Fallout 4 1.10.50 won't start after editing Fallout4Custom.ini

[gooboo]

Hi everyone. After updating my game to 1.10.50 from 1.9.4 I seem to have run into a problem and I don't know what to do. Whenever I edit the Fallout4Custom.ini file to enable modding by adding these lines-

 

[Archive] bInvalidateOlderFiles=1 sResourceDataDirsFinal=

 

the game just doesn't want to work anymore. I can get the game to start fine without editing the Custom.ini file, but then that means none of my mods are showing up in-game. I've tried deactivating all of my mods (except for official DLC) in the mod manager, and that doesn't change anything. If I edit the file by adding those lines it just crashes before it ever gets to the main menu screen, whether I'm playing with my mods or none at all. I've successfully started the game both from Steam and from f4se, so I don't think that's the problem either.

 

What's going on here? I have absolutely no interest in Fallout 4 without mods, so I really would like to be able to fix this problem. Never ran into this issue when I was playing 1.9.4, so I'm not sure what the update screwed up.

[Gookins]

Hey there, you might wanna take a look over there https://www.loverslab.com/topic/90049-fallout-4-11050-wont-start-after-editing-fallout4customini/ . The last post specifically. I actually had a very old interface mod active, after removing it started working again. Maybe it'll work for you too.

 

Good luck!

[Moksha8088]

Are they listed on two separate lines?

 

bInvalidateOlderFiles=1
sResourceDataDirsFinal=

[lepushomicidae]

I have the same problem , but seem to lack the file that was deleted in the post from Gookins.

[Aoikani]

They way you list it in your op, it's wrong. It should be 3 separate lines. This is how it is in my .ini

 

[Archive]

bInvalidateOlderFiles=1

sResourceDataDirsFinal=