Custom.ini (Screwing up my game)?

[WardenHero]

So, this may be a known issue by now, or possibly a very unfortunate isolated incident for myself, either way, I deleted my ini's, and uninstalled/reinstalled my game, after deleting it's folder, including all of the mods, for the single reason that my game would not launch, Steam would stop responding, and there would be an opened window for Fallout 4, it wouldn't launch though, if I waited a minute I would get an error saying that there was a problem syncing with the cloud. So, I tried turning off the cloud, it did nothing. Either way, back to the point, when I reinstalled the game, to my surprise, there was no custom ini, which I'm sure most of you know NMM will nag you, if you don't have it.
So, I verified the integrity of the cache, and it did not revive my custom ini, so I brought it back from my recycling bin, which is how I found out it was the culprit to all of my problems, without it in my documents, I can launch Fallout 4... With it the error persists... So is it the simple fact that I need to delete it, and just edit my base Fallout 4 ini? Or is there a way to fix this?

[wax2k]

First of all, make sure to look in the right location, which is \%userdata%\Documents\My Games\Fallout4\, not in the installation folder. Sounds like you already did that, just to make sure since I've seen others doing that :wink:

 

Secondly, the Fallout4Custom.ini should be created when launching the game for the first time. So start the game at least until the main menu appears and quit it. The ini should be there.

 

If that doesn't help, you can also create it manually. Just create a new textfile and rename it accordingly. And while you're at it, you can already put in the default lines and the archive invalidation part for using custom assets from mods:

[Display]
iLocation X=0
iLocation Y=0

[Archive]
bInvalidateOlderFiles=1
sResourceDataDirsFinal=

Make sure to make it read-only afterwards to avoid unwanted changes to it. You want this file to be edited manually only. Edited February 20, 2016 by wax2k

[WardenHero]

First of all, make sure to look in the right location, which is \%userdata%\Documents\My Games\Fallout4\, not in the installation folder. Sounds like you already did that, just to make sure since I've seen others doing that :wink:

 

Secondly, the Fallout4Custom.ini should be created when launching the game for the first time. So start the game at least until the main menu appears and quit it. The ini should be there.

 

If that doesn't help, you can also create it manually. Just create a new textfile and rename it accordingly. And while you're at it, you can already put in the default lines and the archive invalidation part for using custom assets from mods:

[Display]
iLocation X=0
iLocation Y=0

[Archive]
bInvalidateOlderFiles=1
sResourceDataDirsFinal=

Make sure to make it read-only afterwards to avoid unwanted changes to it. You want this file to be edited manually only.

 

Thank you very much for your response.

Yes, I am already aware as to the location of my ini files, however I appreciate the thorough help!

 

That being said, I have tried all of these things, which furthers my problem more; I am not new to modding, and have been keeping up to date with Fallout 4's ini edits...

Just in case, I did just load up my Fallout 4 again, I have the Fallout4.ini, the prefs.ini, however, it will not create the custom ini, and creating it just causes the response error all over again.

 

Again, thank you for your response, I really want to figure this out :tongue:

 

(Update: I don't know what was different, however, I just remade the custom ini again, out of desperation, if anything XD and my game is fine again).

Edited February 24, 2016 by AshkaariAdaar