Jump to content

General Feedback


Recommended Posts

I think there might be a step missing on the "eXcalibr - ammo eXpansion pack" installation, or the instructions are outdated. First it says "Do not select any Overide options." When I installed it, there weren't any options at all, besides whether to extract the bsa or not. Second the instruction of "Double click the mod in the left pane of MO and move CALIBR.esm to Optional ESPs." That leaves xCALIBR.esm active, but CALIBR.esm is listed as a master for xCALIBR.esm so that would result in a missing master CTD on game start. So are we supposed to move both esm files to optional, or does this issue get resolved later in the guide, or is there indeed a missing step?

Link to comment
Share on other sites

If the external fomod installer is used there are two overwrite options; with the current default MO fomod installer these do not appear. CALIBR.esm from FWE is used in the the game, the version from this mod isn't needed.

Link to comment
Share on other sites

Well I stopped using Project Nevada in FNV because I didn't care for most of the features and it required too many compatibility patches, so it just wasn't worth it to me. I am assuming I would have the same experience with FWE. I'm not a fan of making Fallout more "FPS-like", the current options to use VATS or not depending on the situation is just fine in my opinion. The few options from it that I might like to use aren't worth the extra hassle for me. I understand many people prefer using FWE and PN, but I just happen to be one of the people who would rather not bother. If there's a compelling reason to use FWE that has nothing to do with bullet time or grenade hotkeys or other "FPS" conventions, then I might reconsider.

Link to comment
Share on other sites

The main reasons I made FWE Core are for the game parameter management (e.g., for two particularly important settings see the Experience Options and Skill increase options in the "FWE Options" section here.), and the better stat balancing for weapons and armor (which has been adopted by most other mods) that makes it easier to get compatibility across a large set of mods. Most of the rest of FWE (added mods, etc.) can be turned off, but it might not be possible to turn off everything you don't want.

Link to comment
Share on other sites

I understand that and I know I'm in the minority here so it's not something you should concern yourself with. I've never been into FPS games that much so making Fallout more like one doesn't interest me. And I've found that mods that add a lot of new weapons and ammo types tend to cause more headaches then they solve, not to mention it can cause "too many weapons and not enough ammo" situations, where there's so many ammo types that you can only find a small amount of each so you have to carry around a dozen weapons and switch constantly. Updated meshes and textures are cool, no problem at all with them, just in my experience mods that add a lot of new weapon and ammo types don't add much to the game and more often then not either unbalance it by introducing weapons that are too powerful or add so many new ammo types that you can never naturally find enough for the weapons you do have. So in my install, I skip mods like FWE and a lot of the extra weapons, and the mods that add lore-unfriendly new enemies. For now I'm leaving Calibr and xcalibr in the "optional" list unless I run into a mod that I want to use that needs them. I might change my mind later, it's been a long time since I played FO3 and what I found annoying or headache-inducing in FNV might not be so in FO3. 

Link to comment
Share on other sites

That approach seems a bit extreme to me. I've been able to get Fallout 3 and Wind 8.1 64 bit working together, not without some problems of course. I'm not sure how that approach, which in part requires using Windows 8 in a Windows XP compatibility mode, will work with the utilities such as ENBoost, Fallout Stutter Reducer, and New Vegas Anti-Crash that are used in this guide.

Link to comment
Share on other sites

And FOSE which is mandatory. For example, me when I try to run fose_loader.exe under compatibility mode I just get a nice CTD before even making it to the main menu.

 

Not to mention, that changing compatibility mode on installers like the vcredist and dotnetFX exes makes no sense..

Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...

Important Information

By using this site, you agree to our Guidelines, Privacy Policy, and Terms of Use.