Angardia Posted March 3, 2018 Share Posted March 3, 2018 (edited) im getting this msg while trying to install mods.i have the file, i see it fine. but i keep getting this notice.after i click ok, the msg is gone and i install mods and they work as they should.BUT this msg is annoying as hell.any ideas what to do?i already deleted this ini , made a new one few times... its not on "read only". https://ibb.co/gQTQSn Edited March 3, 2018 by Angardia Link to comment Share on other sites More sharing options...
AGreatWeight Posted March 3, 2018 Share Posted March 3, 2018 Are you sure that in your Fallout4.ini, under the [Archive] tab you have the following lines?bInvalidateOlderFiles=1sResourceDataDirsFinal=(if the last one has anything after "=" you can remove it, those old entries "strings/etc" are no longer needed) Link to comment Share on other sites More sharing options...
Angardia Posted March 4, 2018 Author Share Posted March 4, 2018 Are you sure that in your Fallout4.ini, under the [Archive] tab you have the following lines?bInvalidateOlderFiles=1sResourceDataDirsFinal=(if the last one has anything after "=" you can remove it, those old entries "strings/etc" are no longer needed)https://ibb.co/dNUSsn u talk about this ini or Fallout4.ini?> Link to comment Share on other sites More sharing options...
AGreatWeight Posted March 5, 2018 Share Posted March 5, 2018 I was referring to your Fallout4.ini, not your Fallout4Custom.ini (although from the screenshot you've provided, everything is fine with the custom.ini, so unsure as to why exactly you're getting this problem, seeing as the warning message directly mentions the custom.ini being incorrectly configured)Your three .ini files are in Documents/My Games/Fallout4? Check the Fallout4.ini and make sure it has those same two entries in [Archive]Barring that, I'm not sure what's causing it. Link to comment Share on other sites More sharing options...
Moksha8088 Posted March 5, 2018 Share Posted March 5, 2018 (edited) My custom ini file looks like this: [Archive]bInvalidateOlderFiles=1sResourceDataDirsFinal=[Display]iLocation X=0iLocation Y=0bAllowScreenShot=1[Pipboy]bPipboyDisablefx=1[Display]fPipboyScreenEmitIntensityPA=1.25fPipboyScreenDiffuseIntensityPA=0.15[saveGame]iAutoSaveCount=10 -------------Most likely those mod-specific entries below Display would not apply to you, but you might try to place the Archive entries above the Display entries and see if that helps. Edited March 5, 2018 by Moksha8088 Link to comment Share on other sites More sharing options...
ColonelC61 Posted May 8, 2018 Share Posted May 8, 2018 Are you sure that in your Fallout4.ini, under the [Archive] tab you have the following lines?bInvalidateOlderFiles=1sResourceDataDirsFinal=(if the last one has anything after "=" you can remove it, those old entries "strings/etc" are no longer needed)https://ibb.co/dNUSsn u talk about this ini or Fallout4.ini?> this comment saved my ass thank you so much Link to comment Share on other sites More sharing options...
Carnage2K4 Posted June 2, 2018 Share Posted June 2, 2018 Are you sure that in your Fallout4.ini, under the [Archive] tab you have the following lines?bInvalidateOlderFiles=1sResourceDataDirsFinal=(if the last one has anything after "=" you can remove it, those old entries "strings/etc" are no longer needed)Well, this is stupid, the message (which I'm also getting) AND the documentation both say to add the lines to Fallout4Custom.ini... not Fallout4.ini... Link to comment Share on other sites More sharing options...
JackTheInsaneSeal1 Posted June 25, 2018 Share Posted June 25, 2018 My custom ini file looks like this: [Archive]bInvalidateOlderFiles=1sResourceDataDirsFinal=[Display]iLocation X=0iLocation Y=0bAllowScreenShot=1[Pipboy]bPipboyDisablefx=1[Display]fPipboyScreenEmitIntensityPA=1.25fPipboyScreenDiffuseIntensityPA=0.15[saveGame]iAutoSaveCount=10 -------------Most likely those mod-specific entries below Display would not apply to you, but you might try to place the Archive entries above the Display entries and see if that helps.I did a bunch of random stuff so I'm not sure exactly but placing Archive above Display seems to have fixed the issue I was having. Thanks Link to comment Share on other sites More sharing options...
bld504 Posted November 2, 2018 Share Posted November 2, 2018 I placed Archive above the Display and it fixed the problem. Link to comment Share on other sites More sharing options...
darthaurelius Posted November 22, 2018 Share Posted November 22, 2018 pudiste arreglar el problema?, yo ahora tengo el mismo error :( Link to comment Share on other sites More sharing options...
Recommended Posts