bendking Posted June 18, 2015 Share Posted June 18, 2015 (edited) As stated in the title, I'm having problems with Fallout Script Extender.To run most of my mods I need both archiveinvalidation Invalidated! and FOSE.Problem is, that after activating archiveinvalidation Invalidated!, running Fallout 3 skse Loader either through the launcher or FOMM returns fallout.ini to it's original settings.When starting Fallout 3 through the the Fallout 3 Launcher this problem doesn't persist, which is what makes me think that it's skse loader which reverts the changes that archiveinvalidation Invalidated! inflicts onto the fallout3.iniThis is highly troublesome as I can't run most mods without having missing textures popping out everywhere as well as wierd-ass albino faced motherf*#@ers creeping up on me. Please help. Edited June 18, 2015 by bendking Link to comment Share on other sites More sharing options...
M48A5 Posted June 18, 2015 Share Posted June 18, 2015 You don't need the stand alone ArchiveInvalidation Invalidated!, since there is an Archive invalidation built into FOMM. I have been using both FOSE and FOMM for years and it has never made any changes to the Fallout.ini. You must being doing something wrong. If you use the FalloutLauncher.exe, a new .ini will be created based on the Fallout_default.ini. In order for the game to use FOSE, you must use the "Launch FOSE" button in FOMM. Link to comment Share on other sites More sharing options...
bendking Posted June 18, 2015 Author Share Posted June 18, 2015 I did launch through the Launch FOSE button.Didn't work.Solution found, though!After using the ArchiveInvalidation Invalidated! I simply changed fallout.ini to read-only, that way FOSE didn't revert it back to default. Link to comment Share on other sites More sharing options...
Recommended Posts