Quote:
Originally Posted by frau kaleun
The 'save game bug' is a known issue with the game from stock on up. Sometimes corrupted saves just happen for who knows what reason, but the general consensus seems to be that it is safest to make saves only when you are
1) on the surface, and
2) cannot see or hear any contacts (i.e. no other units within range), and
3) are beyond visual range of any land.
The reason being, I suppose, that any stuff other than you and the empty sea/sky that's around when you save and exit has to be recreated by the game when you reload from that save point. Or at least the game will try to recreate it, in the same location and condition as when you left, and the more stuff there is for it to save and recreate, the higher the likelihood that something will go wrong in the process.
It's also advisable to hit ESC and make saves periodically when nothing is going on... just make the save and then continue playing if you're not ready to end the session. That way if the last one you made won't load, you can work backwards through a series of saves until you find one that's good. At least that way you don't lose an entire patrol.
|
The first thing that happens during the rendering process is that the scripted and random models lose they're waypoints, the equilibrium/everything running as intended is lost by the game engine which attempts to rectify matters but in so doing forces the two aforementioned campaign layers to act out of sync....the CPU is unable to cope with the tens of thousands of SH3 world events (remember, the whole SH3 is scripted upon loading) going on at the same time, thus the resultant CTD.