CTD when entering required [ARCHIVE] lines into Fallout4Custom.ini

[TheTokenGeek]

Hi all,

 

This is a little embarrassing, but I was hoping someone here could spread some light onto why FO4 crashes to desktop when I load or start a game after adding the following lines into my Fallout4Custom.ini file:

[Archive]
bInvalidateOlderFiles=1
sResourceDataDirsFinal=

I have tried to find the problem by running through the following steps:

• Placing only

  bEnableFileSelection=1

  into Fallout4Prefs.ini
  
  The game will start, load and run. But as the above [Archive] code is not entered, mods cannot load.
  
• A totally fresh install of FO4 with no mods and only 1 save (next to vault door, fresh game). Works fine without the [Archive] code, the moment I enter the [Archive] code into Fallout4Custom.ini the game crashes upon trying to start or load a game.
  
• Have tried removing the Interface folder following some ideas I found online.
  
• Tried reverting back to the old fashioned method of entering the following into Fallout4.ini:
  

  sResourceDataDirsFinal=STRINGS\, TEXTURES\, MUSIC\, SOUND\, INTERFACE\, MESHES\, PROGRAMS\, MATERIALS\, LODSETTINGS\, VIS\, MISC\, SCRIPTS\, SHADERSFX\

  and it crashes even trying to open the game.

 

In short, the game will crash to desktop when trying to begin a new game or load a game when

[Archive]
bInvalidateOlderFiles=1
sResourceDataDirsFinal=

is entered into Fallout4Custom.ini. This is even from a fresh vanilla install, I do not have the DLC.

 

My system is as follows:

Operating System

Windows 10 Pro 64-bit

CPU

Intel Core i7 3930K

RAM

32.0GB DDR3

Motherboard

RAMPAGE IV GENE (LGA2011)

Graphics

NVIDIA GeForce GTX 980 Ti

Storage

C:\ = Windows and My Documents Drive (Samsung SSD 840 EVO 1TB (SSD))
D:\ = Steam Drive (SanDisk 960GB (SSD))
E:\ = Origin Drive (OCZ-VERTEX4 476GB (SSD))
F:\ = UPlay and Battle.net Drive (OCZ-VERTEX4 476GB (SSD))
G:\ = Media Drive (Hitachi 4TB (SATA))
H:\ = Scrath Disk (SAMSUNG 2TB (SATA))

ANY help would be so appreciated!

[bill8872]

I have had to recreate the .ini once before, a while ago and this is what I ended up doing.

 

Delete your .ini, and perf files, and start the game through the FO4.exe and let Steam make both the .ini and perf files. The last time I did this Steam did not create a custom.ini file, as the game does not require it to run, but Nexus requires it to add mods.

 

Edit the .ini file, then make a custom.ini file, and copy the .ini file into it. I have both files exactly the same, and have never had an issue with them.

 

 

You will have to add the two archive lines to add mods, and I can not recall if Steam added everything after the

line sResourceDataDirsFinal= I do have everything after it, so I left it there, and have been fine.

 

I do have many other entries in my .ini files due to mods requiring them, or suggestions of lines to add for various reasons, and have had no issues with having the custom.ini exactly the same as the .ini files.

[TheTokenGeek]

I would truly love to say that this worked for me, but alas, it was not meant to be.

 

Thank you very much for trying though. :)

[archtrtd1]

Here are a few things that came to my mind after reading your post:

 

I don't know what Mod Manager (if any) you may be using - you may be missing some random .net files. I have had this happen after a fresh install of Windows 7. I don't know if Windows 10 is any better with updating . . .

 

I've found that setting every single .exe associated with the modded game to "Run as Administrator" has helped me with launching issues. This includes: Fallout4.exe, Fallout4Launcher.exe, f4se_loader.exe, ModOrganizer.exe, Steam.exe, etc. I even had to set it on Skyrim's enbhost.exe (I actually cannot launch Skyrim without this set to run as administrator).

 

You also may need to set your .ini files to read only after making the desired changes.

[9thCleric]

I am having the exact same problem. Stepped away from the game for a few months due to a particularly hard summer course, came back to updates and new DLC. Now I get CTD with a save load unless I delete the added lines in the .ini files. I've tried re-installing the game, starting from the beginning, and the steps outlined below with no success. Will gladly take any suggestions anyone has.

[Toad1337]

Also having this issue. A friend told me it had something to do with the 1.5 and later updates since those support the in-game modding client and that a new version of F4SE needed to be released. Still having the issue even with the new F4SE though.

[9thCleric]

Yeah, just downloaded the latest F4SE after reading some other posts. Going to give it a shot later and see if it fixes the issue.

[Dman883]

I'm having this same problem now. Can't run the game with bInvalidateOlderFiles=1 Unable to find a solution