banjo2E Posted December 10, 2011 Share Posted December 10, 2011 (edited) Recently I started getting locked in cinematic mode (in-game, but all controls except looking around are disabled). This initially happened while I was running FOOK2 plus some other mods, while in Operation Anchorage; I'd go to the briefing, and sometimes the general would get all the way to "Dismissed!" before just standing there leaving me waiting forever, and sometimes he'd only get as far as "I'm only gonna go through this once". I decided to uninstall FOOK2 and use an alternate setup. This forced me to delete all my save files because of FOOK's magnitude, and also did not solve anything; I couldn't get as far as choosing my name in character creation (though, I do get to choose my gender) I disabled everything except Bethesda's own content, and still got this. I temporarily renamed my Data folder, made Steam redownload everything, copied the redownloaded .BSAs over, undid the rename, and ran again, to no avail. I am now at the point where I am only running Bethesda's content under what is effectively a clean install, and I still am unable to progress beyond "You're going to need a name, aren't you?" in character creation. I haven't deleted any of my loose files because I'd like to be able to use them again, and I have no idea what could possibly bork up scripts this badly. I am running FOSE, but the only plugin is Stutter Remover, and with all mods but Bethesda's own content disabled this shouldn't be an issue. I have noticed that Darnified UI is somehow still running, but it similarly should not be touching cutscenes at all. Does anyone have any idea what I can do to fix this, without deleting everything and starting over? I'm worried that even if I do that this'll just happen again unless I find out what exactly is causing this Edit: I should probably mention that the more times I try to play before rebooting, the earlier the cinematic glitch happens. The second or third time I run Fallout on a single boot and select New Game, I get stuck before gender selection rather than before name selection. Edited December 10, 2011 by banjo2E Link to comment Share on other sites More sharing options...
banjo2E Posted December 11, 2011 Author Share Posted December 11, 2011 I've discovered that the culprit is something in (or related to) my INI file. I tried running fallout with the default INI file, and everything worked smoothly. I switched back to my normal INI file and everything froze again before Catherine said her first line.Can anyone tell me what to look for in my INI, or look through it for me? I'm a bit out of my depth in INI file edits, but I (or a mod) may have changed something in here that shouldn't be changed. The only things I touched myself were things that tweakguides.com recommended I touch in their Fallout 3 optimization guide. My INI's in the zip file attached. Link to comment Share on other sites More sharing options...
banjo2E Posted December 11, 2011 Author Share Posted December 11, 2011 HUZZAH! It turns out that, when tweakguides says that people said the tweaks in the memory section were often reported to destabilize games, they MEANT it. I think my problems were all due to bBackgroundLoadLipFiles being set to 1. Link to comment Share on other sites More sharing options...
Jeoshua Posted December 11, 2011 Share Posted December 11, 2011 OH! Yeah that TweakGuides thing is a bit suspect in general. There are a few good suggestions there, and some that have absolutely no effect. One, for example, is the Havok threads count. That string does not exist in the Fallout3.exe file. I've checked. What DOES exists is "iNumThreads:HAVOK" (If I remember correctly). Changing that value at all will cause Fallout 3 to crash and burn... Havok is very tempermental when it comes to it's CPU time, and modifying it at all will cause adverse reactions. So take everything on that site with a grain of salt. Link to comment Share on other sites More sharing options...
Recommended Posts