Can't load games saved at sea......

[MRV]

Everytime I try to load a game I saved while at sea SH3 crashes with an error message right after loading and display of the "not so long ago..."-message....


I use GWX and SH3 commander as well as some mods by TDW on Win7 64 bit.

any ideas about this?

[Kaleun Cook]

As far as I know it's a stock bug. Sometimes the saves work, sometimes they don't. I think nearby ships and harbors increase the chance of a crash.

[sharkbit]

The common rules are:
1. Don't save within 25km(maybe more) of ships.
2. Don't save submerged.
3. Don't enable any mods while on patrol. Only enable mods while in port.
4. Don't save near land.

I think there are a few others as well.

Unfortuneately, you have to try a previous save and hope that works, maybe even start the patrol over. :damn:

Myself, I've been very lucky until yesterday. I break all the rules with abandon and have only had one possible save game crash until yesterday.

I believe it was caused by #3 above, but I'm not sure.

:)

[Jimbuna]

Everytime I try to load a game I saved while at sea SH3 crashes with an error message right after loading and display of the "not so long ago..."-message....


I use GWX and SH3 commander as well as some mods by TDW on Win7 64 bit.

any ideas about this?

I could narrow it down to a couple of dozen possibilities.

Disable all mods except those that came with GWX.....start a new career and save....see if that save game loads and if so add the non GWX mods one at a time until you find the offending culprit.

This is presuming the fault is down to a clash of mods of course.

[Fish In The Water]

Myself, I've been very lucky until yesterday. I break all the rules with abandon and have only had one possible save game crash until yesterday.

Same here...

Strange how the bug feasts on some and (for the most part) passes others by. :hmmm:

[chripsch]

Me to was hit by the problem. Started my 1st patrol since some years with an IXB in April 1940, I saved after sinking a ship...

Now I can`t even find the saves in careers...:damn:

Means, I`ve to sart again from zero the carreer.

Christian

[Fish In The Water]

Now I can`t even find the saves in careers...:damn:

You might want to check your - My Documents\SH3\data\cfg\Careers folder and see if they're still listed there.

Also, if you're running Commander, check to see if the automatic rollback option is enabled.

[Jimbuna]

Me to was hit by the problem. Started my 1st patrol since some years with an IXB in April 1940, I saved after sinking a ship...

Now I can`t even find the saves in careers...:damn:

Means, I`ve to sart again from zero the carreer.

Christian

Go into your careers folder, they will be in there.

Add an 'x' to the saved game name and they will appear again when you boot up the game.

[brett25]

This is presuming the fault is down to a clash of mods of course.

I agree. i have found that with GWX and NYGM (perhaps the other big mods) that adding too many heavy mods on top of them,causes this problem. Its likely a memory issue, or perhaps there is a limit on how much data the game engine can work with.In my case FM interior was the culprit. Beautiful mod but heavy on data/memory. I suspect the various harbor mods may be suspect too. One way to check, is to see how large the mod folder is. Some mods merely change a file or two, or several text data files so no big deal, but others are changing large .dat files and adding gemoetry and texture data and are more likeley the culprits:salute:

[Fish In The Water]

i have found that with GWX and NYGM (perhaps the other big mods) that adding too many heavy mods on top of them,causes this problem.

I suspect this to be true...

As I said previously, my saves have been generally trouble free (mostly I think due to careful mod integration and resource management). The first time I did experience the issue was during some 'heavy mod' tests, which seemed to suggest the game save capabilities were likely overtaxed.

As brett said, I would also recommend screening and streamlining additional mods as a test to see if the issue self corrects.

[FIREWALL]

:D :salute::salute: