Reshki Posted December 6, 2010 Share Posted December 6, 2010 Why does ctd on save happen. What causes that to happen. It makes it impossible to move to the area your trying to get to. cause when you get you hit save crash, go in a building crash, wait crash, sleep crash, fast travel crash! WTF How would one go about make'n this... not.. happen? Link to comment Share on other sites More sharing options...
pjz Posted December 6, 2010 Share Posted December 6, 2010 Crashes happen to me a lot also, shrug, just F5 a lot. Link to comment Share on other sites More sharing options...
Deleted1744345User Posted December 6, 2010 Share Posted December 6, 2010 The latest patch should prevent corrupted saves/autosaves. If you don't have that then you really need to get it. Link to comment Share on other sites More sharing options...
Reshki Posted December 6, 2010 Author Share Posted December 6, 2010 The latest patch should prevent corrupted saves/autosaves. If you don't have that then you really need to get it. doesnt matter f5 still is SAVEING so it still crashes. Link to comment Share on other sites More sharing options...
Johssy Posted December 7, 2010 Share Posted December 7, 2010 (edited) Have ya tried blowing yourself up in a way that causes you to go ragdoll? Use a grenade or other explosive forms to blow yourself up, then try to save. Worked for me. Edited December 7, 2010 by Johssy Link to comment Share on other sites More sharing options...
WarKirby3333 Posted December 7, 2010 Share Posted December 7, 2010 Why does ctd on save happen. What causes that to happen. It makes it impossible to move to the area your trying to get to. cause when you get you hit save crash, go in a building crash, wait crash, sleep crash, fast travel crash! WTF How would one go about make'n this... not.. happen? Hiya. I have this problem all the time. And I've gotten past it several times too. The steps to take: 1. restart your computer. Maybe it's just me, but fallout often gets into a state where it crashes on ever save, or even when starting up, restarting often fixes this.2. Move away from the southeast of the map. IE, if you're around Nelson/Camp Searchlight/Cottonwood cove, get away from there. I find that area very problematic for some reason.3. Reload an earlier full save. Quite often I find that with one save, every auto/quicksave will cause a crash, but if I load from an earlier full save (sometimes just 5-10 mins before) I can then auto/quick save just fine. If you don't already, get into the habit of making regular FULL saves. That is, by pressing esc and selecting the save option, then NEW SAVE (not overwriting an existing one). I keep an archive of currently about 500 save files and growing. If you're not playing on a PC, then science help you, you're probably f***ed. Link to comment Share on other sites More sharing options...
pjz Posted December 8, 2010 Share Posted December 8, 2010 I have that problem with requiring a reboot sometimes also, not just with FONV but all Bethesda engine games (Oblivion did it too). Link to comment Share on other sites More sharing options...
wardminator Posted December 14, 2010 Share Posted December 14, 2010 Obsidian/Bethesda is blaming the problem with the auto and quick saves on Steam's Cloud synchronization system and said they have disabled that function in the patch. You can read their comments on the release of the new patch at http://forums.bethsoft.com/index.php?/topic/1125221-please-read-from-the-teams-at-obsidian-and-bethesda/ So how does it explain people that were having the same issue in FO3 that weren't using Steam? Who knows... Link to comment Share on other sites More sharing options...
Recommended Posts