Enabling mod access crashes my game

[hacnsm]

No matter what I do, my game crashes when I edit the inis in a way that enables modding.

 

Adding the proper lines to Fallout4Prefs and Fallout4Custom will crash my game while loading a save or starting a new game.

 

Also, I am not pirating the game. Apparently pirates experience this problem as well, so I don't want there to be any wrong ideas off the bat.

Tried verifying the integrity of the game cache on steam, but it did nothing. Tried reinstalling nexus too.

It doesn't seem to matter what my loadorder is or if I have mods enabled at all.

Please, someone help me.

Vanilla is okay, but I want to be ready before the geck drops.

[VIitS]

What exactly are the lines you added/changed? How are you enabling your mods (are you editing the plugins.txt file directly, or using NMM)?

 

Also, do you have any meshes or textures installed? If it's a replacer, it doesn't get disabled just because all your plugins are disabled.

[hacnsm]

What exactly are the lines you added/changed? How are you enabling your mods (are you editing the plugins.txt file directly, or using NMM)?

 

Also, do you have any meshes or textures installed? If it's a replacer, it doesn't get disabled just because all your plugins are disabled.

 

I added the bEnableFileSelection=1 under [Launcher] in fallout4prefs

 

also

[Archive]

bInvalidateOlderFiles=1

sResourceDataDirsFinal=

in Fallout4Custom

I tested with a fresh install of the game, and it seems if I don't have these lines added, I can start up a new game.

I later reinstalled and tried to add a few mods on top of changing the inis, but the same thing happened.

Even with small mesh replacer mods effecting very few outfits, the game will run fine as long as I don't change the ini. Haven't checked if the changes took effect ingame though.

Just seems like a really strange problem, as I can't find much info on it around the web.

[VIitS]

Doesn't seem to be related to the problem (or at least adding it doesn't cause me a problem), but you don't need bEnableFileSelection=1.

 

I definitely am not getting a crash playing around with everything related to your changes, so I can't understand it either.

 

I did see an interesting group of settings right under the Archive section in Fallout4.ini that might help:

 

[Papyrus]

fPostLoadUpdateTimeMS=500.0

bEnableLogging=0

bEnableTrace=0

bLoadDebugInformation=0

Try setting the three b___ values to 1, making the ini changes, and running the game. It should generate a log in the same folder your saves and ini files are in (inside a new "Logs" folder). Hopefully that will have some information related to the CTD. It's a long shot since it just logs scripts, and I don't see how nothing but those ini edits would be responsible for a script-related crash. Heh, it even has a note in it saying "This is a script log only and does not contain information on any other part of the game, including crashes." Someone at Bethesda was feeling a bit snarky, I'd say.

Woah, looking at my log I am seeing a ton of script errors even though my game is running fine and I closed the game seconds after the save loaded.

Edit: Just thought of something that might somehow be related: when you reinstalled your game, did you clear out your %LOCALAPPDATA%\Fallout4 folder? I've had a few CTD issues that were fixed by deleting everything in that folder and making the game rebuild it by running the launcher (or possibly verifying integrity of game cache again, it's been a while so I'm not sure).