saizai Posted October 8, 2009 Share Posted October 8, 2009 Are you installing to the c:\Program Files default installation? No. c:\games\Fallout3. (I always do this 'cause I don't like having program files over cluttered.) After lots of uninstalling an reinstalling and testing out other patches, I figured out the problem: when uninstalling the old version and preserving saves, it preserved fallout.ini... which was then used by the "fresh" install. And crashed it even before installing patch. Deleted that and everything else I could find, and now the 1.7 patch works. My suspicion is that FOMM et al modified the fallout.ini in a way that the 1.7 patch was unable to deal with. So current status: vanilla FO3 + 1.7 loads the menu at least (which is past the previous crash point, so presuming all else is OK). I'm about to reinstall FOMM etc; if I don't post again it's 'cause those worked. :) Link to comment Share on other sites More sharing options...
gsmanners Posted October 8, 2009 Share Posted October 8, 2009 It goes without saying that you move the Fallout.ini file (to avoid the stupid auto-start after install). That said, I'm still using the same Fallout.ini file I was using back in March. Link to comment Share on other sites More sharing options...
csb Posted October 8, 2009 Share Posted October 8, 2009 I hate to get somewhat off-topic, but if moving the .ini file and using ArchiveInvalidated Invalidate! cause a problem of that nature? I know the utility changes a few settings the bArchieve...whatever setting for one, and establishing the reference for its BSA file. Would that lead to the behavior that was reported if the BSA were no longer there? :) Thanks for considering the question in advance, I'm just trying to resolve that potential thorny issue in my mind. Link to comment Share on other sites More sharing options...
saizai Posted October 8, 2009 Share Posted October 8, 2009 FWIW: I'm confirmed working post mod. Well, mostly... still have some other CTD issues. But hey, at least I can play. :P Link to comment Share on other sites More sharing options...
SirFrank114 Posted October 8, 2009 Share Posted October 8, 2009 Are you installing to the c:\Program Files default installation? No. c:\games\Fallout3. (I always do this 'cause I don't like having program files over cluttered.) After lots of uninstalling an reinstalling and testing out other patches, I figured out the problem: when uninstalling the old version and preserving saves, it preserved fallout.ini... which was then used by the "fresh" install. And crashed it even before installing patch. Deleted that and everything else I could find, and now the 1.7 patch works. My suspicion is that FOMM et al modified the fallout.ini in a way that the 1.7 patch was unable to deal with. So current status: vanilla FO3 + 1.7 loads the menu at least (which is past the previous crash point, so presuming all else is OK). I'm about to reinstall FOMM etc; if I don't post again it's 'cause those worked. :) Can you give a somewhat computer illiderate, like myself, futher info on how to delete the fallout.ini...? Where does that file reside? Is it more than one? What else do I need to do? BTW, What does FOMM mean? Link to comment Share on other sites More sharing options...
csb Posted October 8, 2009 Share Posted October 8, 2009 SirFrank: the fallout .ini file is in your My Documents\My Games\Fallout3 folder (XP) or in (UserName)\Documents\My Games\Fallout3 (Vista). A default .ini is created when you install Fallout (to whatever directory). Some utilities (ArchiveInvalidation Invalided! is one) make changes to this file, so deleting it probably isn't a good idea (though, Fallout3 itself might recreate a default one(?) if it isn't there ... not sure about that, since I've never intentionally deleted it.) There are tweak guides that tell you about the settings and how to optimize them available on the 'net. Link to comment Share on other sites More sharing options...
Recommended Posts