FinSkyforger Posted January 30, 2019 Share Posted January 30, 2019 Halp, I am at loss. Link to comment Share on other sites More sharing options...
HeyYou Posted January 30, 2019 Share Posted January 30, 2019 Have you started the game at least once? Is the ini file marked as Read Only? (ini file should be in c:\users\yourusername\documents\my games\fallout: new vegas) Link to comment Share on other sites More sharing options...
nge2005 Posted May 1, 2019 Share Posted May 1, 2019 it's a little bit late, but i had the same problem with skyrim se.I solved the problem to open "<mod organizer 2 path>\profiles\<using prifile name>\settings.ini" and set the parameter "LocalSettings=true".It also should help you. I don't know if it was a windows update, but it seems MO2 cann't copy its ini-file to the correct path and this way it use the ini-file of the your own documens. Link to comment Share on other sites More sharing options...
qrysx Posted October 10, 2019 Share Posted October 10, 2019 (edited) So, this happened to me when I "locked" the fallout.ini and falloutprefs.ini files inside an MO profile folder - advice I'd received on a different forum in regards to locking the files in the player folder (which are not where MO looks for them). Evidently MO doesn't like that. Unlocking the ini files allowed MO to start up normally. Edited October 10, 2019 by qrysx Link to comment Share on other sites More sharing options...
Recommended Posts