Corrupted saves again

[1Patriotofmany]

Not trying ti jinx myself, but it appears I have much better luck hitting save waiting a few minutes, then resume the game for about 20 seconds and flat out quit. I was even able to recover a bad one after a corrupt save using that method, by starting a good one and then loading the bad one. Seems when i go through the 4-5 menus even taking two minutes to three minutes per click to save and end the game, I have the most failures. Think I'll stick to saving and waiting a few minutes then resuming. Wait a minute after resume and just quit the game. Anybody else find this more stable?

[KaleunMarco]

Originally Posted by 1Patriotofmany

Not trying ti jinx myself, but it appears I have much better luck hitting save waiting a few minutes, then resume the game for about 20 seconds and flat out quit. I was even able to recover a bad one after a corrupt save using that method, by starting a good one and then loading the bad one. Seems when i go through the 4-5 menus even taking two minutes to three minutes per click to save and end the game, I have the most failures. Think I'll stick to saving and waiting a few minutes then resuming. Wait a minute after resume and just quit the game. Anybody else find this more stable?

i save when there are no other ships detected, when i am not near a coastline with an airfield or battery, when i have moved off from the are where i have sunk ships.
i never save and then reload...any saved game. i always exit and return to play the saved game.
there are probably a couple more do's/don't's that i follow and i just cannot remember them at this time.

i used to have save/reload issues, especially with OpM, and over time i have developed the best practices i have outlined above and now i have less issues.

[propbeanie]

Originally Posted by 1Patriotofmany

Not trying ti jinx myself, but it appears I have much better luck hitting save waiting a few minutes, then resume the game for about 20 seconds and flat out quit. I was even able to recover a bad one after a corrupt save using that method, by starting a good one and then loading the bad one. Seems when i go through the 4-5 menus even taking two minutes to three minutes per click to save and end the game, I have the most failures. Think I'll stick to saving and waiting a few minutes then resuming. Wait a minute after resume and just quit the game. Anybody else find this more stable?

Yes. That does seem to be "proper technique"... though as KM mentions, somewhat mod-dependent also.




My guess is that the game has a read AND a write buffer for the hard drive, the write buffer being the "slow poke", and therein lies the trouble when you don't "pause", but who knows?

[Mad Mardigan]

I follow the methodology, NEVER saving while submerged, near any ship... (still alive or sunk) of being in either nav map or in command room... making sure there are no ships or aircraft about... not near land by at minimum of 50 nm, in deep waters area... never shallow waters... & have been out of using high TC, by at minimum of... 3 minutes (I feel 5 is better, but... that's just Me *shrugs*) before doing a save... & then waiting at least 3-5 minutes after, before I exit.



Following that methodology... to date (knock on wood) I have not ran into any issues, with save corruptions... thus far.



Hope this helps...








M. M.

[1Patriotofmany]

I've been saving a game, wait 3 minutes, then RESUME the game for about 10 seconds or more. Then Quit to windows, taking 10 seconds or more to click on the two quit screens. I've been saving while a giant convoy is near, saving underwater during attacks and hurt, saving everywhere you're not supposed to. Knock on wood every save has turned out good since I complained at the beginning of this post!!!!! Playing Darkwaters. Haven't tried the same method on other mods yet. I am happy again! Had a few weird saves where the crew was repeating something over and over when I started it, but diving or doing something else stops the repeating.