This is my take on the whole thing. It appears crashes will always occur right after a save after a ship has sunk.
If this is so, I think there is a flaw in the game programming here, as I think the program is confused as to whether the ship is afloat or is sunk.
I think the error occurs in the .sav files in the SH3 folder in Documents.
These files are save specific and tell the program what is happening at the time of the save, instead of just reloading the campaign layers and assuming everything is vanilla and no ships are sunk.
What I think happens here is that the sunk or sinking ship is not written correctly in the .sav file. Thus the ctd. I think in the code it is written as being in pergatory, not sunken not still afloat. Thus the confusion between the engine and the save.
Of course ctd will happen for many reasons, like little ram, but I think the sunken ship issue is a problem with how the engine outputs the .sav files. Because it reads the .sav file, which contradicts with the campaign layer saying there is a ship there and its still afloat. But if its in the process of sinking or just after sunk, perhaps the engine can't understand that.
Can we find the mentioning of the sinking ship with hex editor in the .sav files?
However, as a control, I'd suggest everyone to remove all the mods for testing. Because if this specific ctd occurs during vanilla, then we need to be sure of that and attack the issue from there knowing no other mods create this ctd.
|