Page 1 of 1
Corrupted Save
Posted: Tue Apr 06, 2010 1:43 am
by Legoman
Okay, I'm a little worried. This is the first time it has ever happened to me, and I didn't lose much game time, only some time in the Kvatch Oblivion World, Ithink I corrupted the save from using the console command in the Kvatch oblivion plane. Anyway, tips on how to avoid it, what causes it? Thanks,
Re: Corrupted Save
Posted: Tue Apr 06, 2010 12:49 pm
by Sawses
What commands did you use?
The most common cause is save game bloating, which I highly doubt was your problem since you were just in Kvatch. It is caused by some mods and the, "placeatme" command. Not too much trouble to avoid.
Another cause is just a random corruption, these happen from time to time, with just the variables being just right. I would recommend that you reload an uncorrupted save, fast travel away from Kvatch and back again, to avoid doing the exact same thing as last time.
To avoid any major save game losses, make separate save files, I use one main file, one I use before I start a quest, and one I use before I plan on doing major damage to a city.
EDIT: Oh, and there is a backup auto save in the Oblivion Saves folder named, "Auto save.bak" Rename this to, "Autosave.ess" and delete the corrupted earlier auto save. This is just a bit of useful info, just in case you get massive corruption on multiple files.
Re: Corrupted Save
Posted: Tue Apr 06, 2010 4:10 pm
by BFG
There are A LOT of possible reasons for save game corruption. Unfortunately it's a fairly common issue with Oblivion, since it's such a complex game; the best defense is to create numerous NEW saves so you don't lose much game time when/if the corruption happens. I save once every 10 minutes or so and always keep at least the last 5 save files, plus the Autosave. I have one character with 430 hours and counting of game time, and by doing the above I've managed to dodge a dozen or more corrupted save games on that character.
Sawses is right--save game bloating and poorly written mods are the most common reasons. But they're not the only ones--I have had a save game on the PS3 (which can only run Vanilla) get corrupted a couple of times, early into the game. Some other tips:
--Don't try to save at the same time that the game is loading an area or Autosaving. I'd also recommend not using Quicksave as this seems to increase instability.
--I'd generally recommend not saving when a lot is going on--such as in the middle of a battle or just after going through a door.
--If you're using the Crash Prevention System and it prevents a crash, I'd often recommend restarting Oblivion anyway. Sometimes Oblivion needs to crash.
--Mods such as Streamline 3.1, Oblivion Optimization, or Kuertee's Cleanup can sometimes cause issues since they make changes to Oblivion's core functionality. Of course, they can also prevent many issues so I usually run them anyway (though I do disable the Autosave feature on Streamline).
--Definitely make sure you're running the latest official patch (1.2.0416) and all of the applicable Unofficial patches. These will help prevent some nasty save game corruption issues, particularly with the Shivering Isles (reference ID glitch). Usually these will only have an effect on longer games however.
--If you're able to at least load your corrupted save game, then disabling some of your mods might help "resurrect" it. I've had several situations where I thought a save game was lost, but after I disabled a couple of conflicting mods I was able to keep going.
--If animations seem to get stuck (doors opening slowly, candles not flickering, etc.), this isn't a crash but a completely separate issue that is easily fixed. Most people experience this after 200-300 hours of gametime; it's inevitable.
Re: Corrupted Save
Posted: Sat Aug 21, 2010 7:40 pm
by Sjeng
BFG wrote:--If animations seem to get stuck (doors opening slowly, candles not flickering, etc.), this isn't a crash but a completely separate issue that is easily fixed. Most people experience this after 200-300 hours of gametime; it's inevitable.
Mind sharing with us how that's fixed?

thanks!