Need help analyze an odd saved game

[Pisces]

Originally Posted by BasilY

Actually, GWX3.0 has been good so far. I had three careers without a bad save. (although it's now my practice to try to finish entire patrols without saving/loading) This is the first saved game I had a problem in GWX3.0.

With respect, The situation I am describing is NOT the same situation you have. The game I had did NOT crash WHILE loading (I had that happened in GWX2.1). It crashed after loading successfully and playing for a few minutes. I actually finally AVOID THE CRASH, by running on the surface at flank AWAY from the convoy (over-cast sky, visibility is low). I was able to play on. So I believe this saved game is a great opportunity to finally find out what's causing the crashes. Loading this game and trying to approach the convoy will guarantee a crash.

I am always curious about what exactly cause the crashes. So this saved seem Ideal. I hope someone can finally get to the root of it.

To Jimbuna, The myth that saving while submerged and/or near vessels are not correct. I had perfectly good saved games where I am at p-depth around DDs. But I had bad saves where I am on the surface and with nothing around. Being submerged and/or near other vessel doesn't seem to increase the chances of corrupt saved games.

Originally Posted by Jail

Could it be that the computer gets too much to render/keeping track of in that convoy that makes it crash ?

Yes, just to make sure, clean out the pc case from dust and make sure enough cool air can enter it (and warm air leave). Also clean the fans of your CPU and graphic card. I had it crash on me several times when the game had to show more particle effect like torpedo explosion or bowspray. Mind you, for me that was on hot days, with 2 harddrive connected back to back pretty hot to the touch. Cleaning out the dust and keeping the side lid open I have never had such crashes again. The harddrives appearantly were not the direect cause because I left them back-to-back at the time. However those harddrives started to act up because of the heat they generated a year later. Seperating them and blowing an auxiliary fan at them made the pc alot more stable and able to keep a 'cool head'. Or lower the particle intensity in the options page of the main menu.

[BasilY]

Originally Posted by jimbuna

I've no doubt what you have personally experienced is accurate and correct but I wouldn't dismiss other peoples theories as a 'myth'.

Search the forums for the multitude of posts regarding problems with saves.....in particular look for 'the dive of death'.

I stand corrected. My apologies, Admiral JB.

[Jimbuna]

Originally Posted by BasilY

I stand corrected. My apologies, Admiral JB.

SINK EM ALL!!

[Doolar]

When I save , I :

1. make sure I'm at least 50km from home port
2. make sure I'm at least 35km from another ship . Floating or sunk .
3. gramophone off
4. not in TC for at least 5 minutes
5. on the surface
6. in Control Room View

I really don't know if all this is necessary , but ... 0 CTD's , with GWX , any and all versions

[Paul Riley]

Just thought I would include my latest save problem here.

I experienced the missing save curse yesterday,adding the 'x' sorted that out (thanks to the documentation and jimbuna)

I havent had any corrupt save games (yet),and I always keep the player profile,and just one save,overwriting each time.

I now keep a backup on memory card of my current save point.

[fingers crossed]

[Leandros]

Originally Posted by Jail

Could it be that the computer gets too much to render/keeping track of in that convoy that makes it crash ?

I have often experienced CTD's after a prolonged game (GWX 2.1), possibly in the vicinity of convoys (much information to handle...?) when going from one crew mode to another - usually from torpedo to "neutral". After I began starting from Commander this has not happened. Also, I now always go out of the game after a finished patrol, to start a new one with Commander.

I also suspect it is "safer" to make eventual changes in realism or crew composition before saving and going out of the game - than after start-up from Commander. Not counting changes done in Commander itself.