Wolfmod Posted December 16, 2015 Share Posted December 16, 2015 When I began modding my game I was told to extend the "sResourceDataDirsFinal=" entry in my fallout4.ini file to "sResourceDataDirsFinal=STRINGS\, TEXTURES\, INTERFACE\, SOUND\, MUSIC\, VIDEO\, MESHES\, PROGRAMS\, MATERIALS\, LODSETTINGS\, VIS\, MISC\, SCRIPTS\, SHADERSFX\" and this I did. Modders still tell players that the reason why this mod or another is not working is because they haven't done this. Now, when I load NMM I am informed that I should return this entry to its default and even some mod authors have been advising players that the .ini file modification is no longer necessary. However, I was also told that using Fallout4.exe to launch my game instead of Fallout4Launcher.exe would stop Bethesda from emptying my plugins.txt file and it didn't. So, what is the story here? Link to comment Share on other sites More sharing options...
RavenerTBC Posted December 17, 2015 Share Posted December 17, 2015 Seconded. I archived and rebuilt my ini files yesterday from the launcher, and no texture mods would load until I re-added those subdirectories to Fallout4.ini and Fallout4Custom.ini. Link to comment Share on other sites More sharing options...
SkunkMonkey Posted December 17, 2015 Share Posted December 17, 2015 You also need bInvalidateOlderFiles=1 if you aren't using the sResourceDataDirsFinal method. The paths method loads only the paths specified so you can selectively load some paths and not all. The invalidate older files method tells the game to just load all the folders. Use one or the other. Link to comment Share on other sites More sharing options...
Recommended Posts