I verified everything, this method works for all versions of the game. >>> Fallout 4 1.10.64 And Earlier <<< If you have problems, the source of these problems is located between the keyboard and the chair. >>> How Can You Not Understand A Few Lines Of Instructions <<<
From now on this forum is closed!
If the method described here will cease to work, then I will remove my guide. So if you can still read it, That Means It's Working.
IP, I came here to share my condolences with you. I'm really sorry you have to deal with people who think this is a mod and that it broke their game!! I honestly have NO IDEA how they even manage to add mods if they can't even read... Makes you even wonder how people got by with FO3/FONV/OB/SR without knowing about this, stock-standard in Bethesda games, for years, in many guides, etc. Congrats for making the modding community a better place with this much needed addition, which without the majority of mods made simply will not work! Keep up the great work!
And the ironic part? You're Polish, right IP? Yet you have absolutely no problem generally understanding the community, from what I've seen. So if you can do it, then why can't they?! Too lazy perhaps? Sigh. Anyway, if we all just work together and point them in the right direction it can hopefully save everyone the headache!
i just bought fallout from steam when i do this useing notepad just notepad my game will not load up it'll get to the title screen but it will not load up i tryed disabling my mod but it stil doesnt work
I've been using NMM and Bialgo's for archive invalidation (it automatically tweaks the .ini files as you show here, and yesterday my Steam installed the latest Fallout 4 1.5.x beta patch, and now the game crashes if I try to load or start new game - but if I take archive invalidation off and return to default STRINGS, then it works just fine. Is there any way to do archive invalidation in the latest Fallout 4 patch, or is it just not possible? I've seen modders doing it, so it must be possible. It's just this one .ini tweak that causes my game to crash for some reason, yet it's imperative for all the mods I'm used to using.
Maybe, Beth has changed something in the new Patch. Unfortunately until wednesdays I am away from home and I will not have the opportunity to test this thoroughly. Try Adding Only: [Archive] bInvalidateOlderFiles=1
And see if it still causing CTD.
Other tips that I can give you and others is: - Reset the INI files by verifications of game files through STEAM - Start Fallout4Launcher.exe set up all options. - And only then edit INI using a Text Editor Only.
Simply programs that edit INI are unbelievable to me. Very often they change or add entries that causes instability of the game.
Fallout 4 Configuration Tool -> Last Ipdated 19:26, 9 February 2016 Since then, came a lot of patch for FO4.
I tried that and I tried editing the sResourceDataDirsFinal= line the old-fashioned way, with adding the other directories after STRINGS, and it crashed on both occasions.
After searching Bethesda forums, I did a fresh install of the game and removed Pleasant UI - as it turns out UI overhauls like DEF-UI and Pleasant UI are currently incompatible with the latest 1.5 patch. Now my game is working liked it used to again with no crashes and with ArchiveInvalidation.
"After searching Bethesda forums, I did a fresh install"
Then the next time read what I write to you, (>>> verifications of game files through STEAM <<< it really is not that hard read something and then understand what you have read.
The fresh install would probably not have solved the issue. Most answers are delete the "interface" folder from the data directory . That is where the interface changes are stored from the UI mods
"The fresh install would probably not have solved the issue"
For me "Fresh Install" means the removal and installation of all files and directories of the game Again. It is not obvious, I see.
And all due to the laziness of people. They do not read/learn/find info how Well Modify game! And they think that: It's so simple to modify game. No, it's not, especially when you are using a large amount of modification.
Short answer: Because the sResourceDataDirsFinal is a finite list, it was written in such a way that if it's given no arguments, it's treated as an infinite list. By not removing STRINGS\, you're limiting what loose files the game loads.
Long answer: sResourceDataDirsFinal is a variable that stores all the subdirectories inside the Data directory from which the game will load loose files (files not in a Bethesda-encrypted archive file). Below are a couple examples (with quotes added to clarify the final example) and their results:
"sResourceDataDirsFinal=STRINGS\" -Loads loose files from Data\ and Data\Strings\ "sResourceDataDirsFinal=STRINGS\,TEXTURES\" -Loads loose files from Data\, Data\Strings\, and Data\Textures\. "sResourceDataDirsFinal=" -Loads loose files from every subdirectory of Data\ "" -Loads loose files from Data\ only. (Note that this example, the empty line above this one, means you've removed the sResourceDataDirsFinal variable completely from all ini files. Note also that Beth might've configured the game to automatically re-add sResourceDataDirsFinal to the ini files if it isn't found, and also this serves no purpose, it's merely here for educational purposes)
As a side note, I'm not entirely sure whether or not loose files are loaded with bInvalidateOlderFiles set to 0. My theory is that they are, but that the game gives priority to files inside the bsa's (Beth archives), and setting bInvalidateOlderFiles to 1 changes it to load files by date modified (which, almost by definition, means modded files/loose files are loaded first, because in order to create the mods, the original game's files needed to be released)
My mods weren't loading since the 1.5 update. I found the fix, putting an asterisk in front of each mod listed in plugin.in
Method 1: Adding An Asterisk
1) Open "plugins.txt" that's located at C: > Users > [Your Profile] > App Data > Local > Fallout 4. This can be done using Notepad. 2) In the document there should be .esp or .esm mods listed. (for example BrighterSettlementLights or Advanced Settlement Power.) Simply put an asterisk (*) before every mod in the list and save it. "*Advanced Settlement Power.esp" is just one example.
I've have been testing this method for quite some time now since it was introduced on the Fallout 4 wiki. Load times have been reduced greatly and every mod I have installed works as intended.
Many are unaware of how to properly implement the edits so it is nice to have a clear instruction set for those who need it. Thank you for taking the time to post the instructions.
The only thing that can happen is when using Fallout4Launcher.exe he may reset the settings. I do not use Fallout4Launcher, I erased him from the game directory and run the game using f4se_loader.exe
Why?
Because Fallout4Launcher.exe places in INI variables that are not used by the game itself (iTexMipMapSkip=) or write INI files with errors.(fSunUpdateThreshold:Display=0.5f) More about INI files.
For so many years, Beth apparently has not learned how to properly "write" a simple program that edit a simple text file. Or simply has a PC users in the ***
You can easily check yourself. - Start the game. - In the console, type: getini "iTexMipMapSkip:Display" getini "fSunUpdateThreshold:Display"
Can't understand why it doesn't work for me when everyone else seems fine. I've tried resetting to default .ini files as well, but my mods simply do not function properly unless i keep the multitude of subdirectories listed as per the "old" method. I'm certain to have followed the process correctly, trying to also incorporate the changes in not only the Fallout4.ini, but the Default.ini as well as the Custom.ini....yet I still see no success with this.
Update: After another hour of fiddling, I finally managed to get it to work. My best guess is that it may have been working all along, but as my primary means of assuming it WASN'T was through a lack of Pleasant UI. Turns out that mod refuses to install correctly via NMM, and I have to manually install it for it to function. Having reset all .ini for the Archive Invalidation, I then found that Pleasant UI is indeed working...and as such any other subdirectories should also be correctly referenced now.
70 comments
Comments locked
The author has locked this comment topic for the time beingWant to thank Me, then tell others about it.
I'm sorry but I had to delete some comments.
The whole forum looked like spaghetti.
Here you have the reasons why:
First Example
Second Example
Third Example
Very good S.T.E.P. guide on how to operate the INI files in Beth games
It is written for Skyrim, but the principles are the same.
And I Very Strongly advise you to read this guide, if you have no idea what it is INI files in Beth games.
I verified everything, this method works for all versions of the game.
>>> Fallout 4 1.10.64 And Earlier <<<
If you have problems, the source of these problems is located between the keyboard and the chair.
>>> How Can You Not Understand A Few Lines Of Instructions <<<
From now on this forum is closed!
If the method described here will cease to work, then I will remove my guide.
So if you can still read it, That Means It's Working.
Here you have evidence to support what I wrote.
As you can see in the picture, I use the Lose Files.
Texture for PipBoy, and SWF files for the Interface.
So stop writing Stupidity.
I'm not here to repair what you (or any program that you are using) broke.
Yes I am rude, because I already have enough of this nonsense.
And false accusations/insinuation that this method does not work.
From now on this forum is closed!
If the method described here will cease to work, then I will remove my guide.
So if you can still read it, That Means It's Working.
As you can see, people nowadays have a serious problem with ability to read.
There are plenty of people who do not understand what they just read.
Seriously, I wonder for blocking comments for this guide.
EDIT
I added a warning that guide REQUIRES reading ability with understanding what you have read.
But...
All INI files in Beth games are in English, if someone did not understand English should not change them.
EDIT
I added a link to the guide on INI files.
If you are referring to something, it is good to give some links.
I can not read thoughts from a distance.
My problem is that, with the Steam base game Fallout 4 1.5.157 loaded and zero mods enabled, if I change the lines:
bInvalidateOlderFiles= 0
sResourceDataDirsFinal= STRINGS\
To:
bInvalidateOlderFiles=1
sResourceDataDirsFinal=
The game crashes when I click New or try to load a save game. But if I don't edit those .ini lines, the game runs fine.
By the way, this only happened since Steam installed the latest patch update, because I'd had no problems with it before.
Unfortunately until wednesdays I am away from home and I will not have the opportunity to test this thoroughly.
Try Adding Only:
[Archive]
bInvalidateOlderFiles=1
And see if it still causing CTD.
Other tips that I can give you and others is:
- Reset the INI files by verifications of game files through STEAM
- Start Fallout4Launcher.exe set up all options.
- And only then edit INI using a Text Editor Only.
Simply programs that edit INI are unbelievable to me.
Very often they change or add entries that causes instability of the game.
Fallout 4 Configuration Tool -> Last Ipdated 19:26, 9 February 2016
Since then, came a lot of patch for FO4.
Here you have a credible proven tips for INI.
read something and then understand what you have read.
For me "Fresh Install" means the removal and installation of all files and directories of the game Again.
It is not obvious, I see.
And all due to the laziness of people.
They do not read/learn/find info how Well Modify game!
And they think that: It's so simple to modify game.
No, it's not, especially when you are using a large amount of modification.
I've just added archive invalidation and that was enough for everything to work just fine. String mods included. Am I missing something?
Long answer: sResourceDataDirsFinal is a variable that stores all the subdirectories inside the Data directory from which the game will load loose files (files not in a Bethesda-encrypted archive file). Below are a couple examples (with quotes added to clarify the final example) and their results:
"sResourceDataDirsFinal=STRINGS\"
-Loads loose files from Data\ and Data\Strings\
"sResourceDataDirsFinal=STRINGS\,TEXTURES\"
-Loads loose files from Data\, Data\Strings\, and Data\Textures\.
"sResourceDataDirsFinal="
-Loads loose files from every subdirectory of Data\
""
-Loads loose files from Data\ only. (Note that this example, the empty line above this one, means you've removed the sResourceDataDirsFinal variable completely from all ini files. Note also that Beth might've configured the game to automatically re-add sResourceDataDirsFinal to the ini files if it isn't found, and also this serves no purpose, it's merely here for educational purposes)
As a side note, I'm not entirely sure whether or not loose files are loaded with bInvalidateOlderFiles set to 0. My theory is that they are, but that the game gives priority to files inside the bsa's (Beth archives), and setting bInvalidateOlderFiles to 1 changes it to load files by date modified (which, almost by definition, means modded files/loose files are loaded first, because in order to create the mods, the original game's files needed to be released)
Method 1: Adding An Asterisk
1) Open "plugins.txt" that's located at C: > Users > [Your Profile] > App Data > Local > Fallout 4. This can be done using Notepad.
2) In the document there should be .esp or .esm mods listed. (for example BrighterSettlementLights or Advanced Settlement Power.) Simply put an asterisk (*) before every mod in the list and save it. "*Advanced Settlement Power.esp" is just one example.
http://www.designntrend.com/articles/75204/20160430/fallout-4-pc-mods-not-working-bethesda-1-5-patch-guide-fixes.htm
I've have been testing this method for quite some time now since it was introduced on the Fallout 4 wiki. Load times have been reduced greatly and every mod I have installed works as intended.
Many are unaware of how to properly implement the edits so it is nice to have a clear instruction set for those who need it. Thank you for taking the time to post the instructions.
[Archive]
bInvalidateOlderFiles=1
sResourceDataDirsFinal=
into the Fallout4Custom.ini or does it make no difference?
The only thing that can happen is when using Fallout4Launcher.exe he may reset the settings.
I do not use Fallout4Launcher, I erased him from the game directory and run the game using f4se_loader.exe
Why?
Because Fallout4Launcher.exe places in INI variables that are not used by the game itself (iTexMipMapSkip=) or write INI files with errors.(fSunUpdateThreshold:Display=0.5f)
More about INI files.
For so many years, Beth apparently has not learned how to properly "write" a simple program that edit a simple text file.
Or simply has a PC users in the ***
You can easily check yourself.
- Start the game.
- In the console, type:
getini "iTexMipMapSkip:Display"
getini "fSunUpdateThreshold:Display"
Update: After another hour of fiddling, I finally managed to get it to work. My best guess is that it may have been working all along, but as my primary means of assuming it WASN'T was through a lack of Pleasant UI. Turns out that mod refuses to install correctly via NMM, and I have to manually install it for it to function. Having reset all .ini for the Archive Invalidation, I then found that Pleasant UI is indeed working...and as such any other subdirectories should also be correctly referenced now.