Ini causing crash on start up.

[Hiromatsu1]

Alright so I just re-downloaded FO4 after a long break.  I'm still on the pre Next Gen version and have blocked updates.  Have all Mods disable.  Game starts fine either through Loader or F4SE.  That is until any changes occur in the custom.ini.  As soon as anything none default is in it the game freezes instantly on a black screen.  Delete the ini's and starts fine again.  The instant Archive Invalidation is added eternal black screen.  I have disabled all the mods so it isn't one of them trying to start causing it.  I've removed any kind of UI files.  It's not the video either since it never gets that far.  I'm at a complete loss at this point.  Any ideas?

[dumbkoala]

Hi! Of course, I didn't understand much from your message. What I'm saying is that you haven't provided any specific information to try to understand why the game is behaving this way. Could you show me what exactly is written in the ini files that your game cannot launch with?

At the moment I only have one idea. Namely, prohibit making changes to ini files. That is, set the “read-only” flag for them.

[worm82075]

31 minutes ago, dumbkoala said:

At the moment I only have one idea. Namely, prohibit making changes to ini files. That is, set the “read-only” flag for them.

That is not an option if you want to play with mods. You are not wrong about needing more info though.

 

Where is your game installed?

How did you roll the update back?

Where is the ini you are editing located?

What exactly are the edits you are making?

Does this occur with ZERO mods enabled?

[taylorg4]

Having a very similar problem! 

I'll try to provide as much info as I can.

Just got a new computer. Previous computer had a ton of mods, including weapons, and it all worked fine using the normal procedures. But for the new PC, I'm getting a CTD on loadup.

• Fallout 4, current update.
• Using Vortex and have a handful of mods installed of various size (Sim Settlements 2, America Rising 2, Verdant Wasteland, Vivid Weathers, Pipboy colors, etc)
  • The only thing in my custom.ini is [Pipboy]bPipboyDisableFX=1  
    • Everything works great! 
• I try to install any weapon mod (filtering for Next Gen patch compatible) 
  • Game crashes during initial load screen (before main menu)
• I go into my custom.ini and add in the 
  • [Archive]
    bInvalidateOlderFiles=1
    sResourceDataDirsFinal=
• Game crashes
• Delete Fallout4custom.ini entirely as well as the weapon mod
  • Game loads fine
• Go back into custom.ini and add in the Archive text
  • Game crashes

So it seems that adding in the [Archive] text lines causes a crash during initial load, as do, specifically, weapon mods. I assume there is a connection?

I have even completely deleted the Fallout4 MyDocuments folder so all those get reset, but I keep getting the same results.

Possible the conflict is coming from elsewhere? Maybe the Data folder in the SteamApps folder? Does that get fully deleted when I do a reinstall?

To answer the questions from the previous poster:

Game installed in my C Drive

Current patch

Ini is in My Documents folder in C Drive

My only file adjustments are

Fallout4prefs.ini
[Launcher]
bEnableFileSelection=1

Fallout4Custom.ini
[Archive]
bInvalidateOlderFiles=1
sResourceDataDirsFinal=

[Pipboy]
bPipboyDisableFX=1

Was happening with zero mods after a fresh install. 

 

Thank you for any help. I don't understand why weapon mods in particular are the issue and how the game works without editing the .ini file even with a handful of mods. I even tried downloading weapon mods directly in the in-game system and the game wouldn't load once I exited and returned. I could play without these mods, obviously, but that's one of the biggest appeals to me :(

[RoNin1971]

its not the ini setting, but its "effect".

These settings tell FO4 to load loose files from your data folder (& thus ovveride).

There is something there which makes it CTD.

(and non of it is removed on reinstall.)

so, check your data folder.

[FennecExe]

On 7/2/2024 at 12:56 PM, RoNin1971 said:

its not the ini setting, but its "effect".

These settings tell FO4 to load loose files from your data folder (& thus ovveride).

There is something there which makes it CTD.

(and non of it is removed on reinstall.)

so, check your data folder.

Heya ! I'm having the same problem as the topic creator.

I don't know if I should create a new topic for this or not but I'll share my problem here.

So, same thing for me. I add the Fallout4Custom.ini to make it load loose files and I get a CTD on startup.

Here's what's confusing me. Since I assume this is a mod conflict, I uninstall the most recent mods until it doesn't crash anymore... but the game still crashes on startup. Vortex tells me that my most recently installed mod was installed a week ago and I know I have played the game multiple times since then.

So... I don't know. The game still crashes on startup even though I uninstalled every recent mod I added. I browsed through my Data folder, in case a rogue ESP or ESL was left over but nope...

I really wish Fallout 4 had logs to give info about what when wrong. I know Buffout 4 adds logs but it hasn't been updated to NG yet.

Any idea what I can do to find the file that causes a CTD?

 

Thanks in advance!

Edited July 29 by FennecExe
Grammar.

[fraquar]

You are using Vortex, I must defer to others who understand that mod manager and it's nuances.

I'm just a little confused why you'd create the Custom.ini AFTER you have already installed a bunch of mods - normally that is something you do before ever installing a single mod.

[RoNin1971]

22 hours ago, FennecExe said:

Heya ! I'm having the same problem as the topic creator.

I don't know if I should create a new topic for this or not but I'll share my problem here.

So, same thing for me. I add the Fallout4Custom.ini to make it load loose files and I get a CTD on startup.

Here's what's confusing me. Since I assume this is a mod conflict, I uninstall the most recent mods until it doesn't crash anymore... but the game still crashes on startup. Vortex tells me that my most recently installed mod was installed a week ago and I know I have played the game multiple times since then.

So... I don't know. The game still crashes on startup even though I uninstalled every recent mod I added. I browsed through my Data folder, in case a rogue ESP or ESL was left over but nope...

I really wish Fallout 4 had logs to give info about what when wrong. I know Buffout 4 adds logs but it hasn't been updated to NG yet.

Any idea what I can do to find the file that causes a CTD?

 

Thanks in advance!

 

If enabling "loose files" causes the CTD, no .esm, .esp or .esl is involved.

Its the 'loose files' inside your data folder. (on clean install / without any mods, it should be empty). Could be a bad script, texture, nif, anything realy. (Although bad textures & nifs usually don't cause CTD's on startup)

Those files will always be loaded (last, & thus override anyhing else). Regardless of your mod manager (unless there is a mod with loose files installed using the manager, then it depends, on the manager)

[FennecExe]

8 hours ago, RoNin1971 said:

 

If enabling "loose files" causes the CTD, no .esm, .esp or .esl is involved.

Its the 'loose files' inside your data folder. (on clean install / without any mods, it should be empty). Could be a bad script, texture, nif, anything realy. (Although bad textures & nifs usually don't cause CTD's on startup)

Those files will always be loaded (last, & thus override anyhing else). Regardless of your mod manager (unless there is a mod with loose files installed using the manager, then it depends, on the manager)

Thanks for info. I found the culprits in my Data folder. It was... easier than I thought. Basically, I used Vortex's "purge" feature which temporarily removes mod files from the Data folder and I peeked to see what was left over. A couple of scripts and NIFs were still here. After deleting them and making Vortex redeploy my mod files, everything was A-OK !

Thanks for the help.

 

On 7/30/2024 at 12:13 AM, fraquar said:

You are using Vortex, I must defer to others who understand that mod manager and it's nuances.

I'm just a little confused why you'd create the Custom.ini AFTER you have already installed a bunch of mods - normally that is something you do before ever installing a single mod.

Ah, sorry, I wasn't very clear about that. I did have the custom INI since the beginning. I noticed that by deleting it, the game would start but many of my mods broke (as expected). By using master-hacker skills (Google), I found this topic and thought it was relevant to my problem. Sorry if it was misleading!