It wasn't a save problem- the game crashes when the destroyer explodes! In the end I gave up and re-started the mission. As Cassious has suggested it's presumably some kind of coding issue that manifests itself under particular circumstances, like the car in the movie Class Action :03:



Yes, I am running in compatibility mode- after a lot of trial and error.... I think the 'save game' issues are a bit of a red herring though- I had a working save position made while submerged in the middle of Dover harbour surrounded by stationary ships!

I have a new ctd issue in my latest campaign- I have just successfully wiped out an entire convoy off the east anglian coast, and received a radio message telling me about large numbers of enemy ships near Dunkirk (the evacuation presumably- this is may 1940) but when I get there the game runs very slowly and eventually crashes. I'm guessing the program has so many positions to calculate it can't cope- certainly not a PC issue as mine is still running cool as a cucumber.



I'm guessing this is something I just have to live with- just as well I took the precaution of saving right after I destroyed the convoy- I currently have 3 torpedoes and 7 shells left :03:

Do you have a Large Address Aware utility enacted on your SH3.exe file? Your computer can be a water-cooled behemoth running at 142GHz with 96Gig of RAM, but the game will still plunk along at 30fps and about 1.6gig of RAM, and limited bandwidth, because that's all Windows will give a 32-bit DirectX app...

I wasn't aware there was such a thing, but have now downloaded and enabled one.


My pc is jut a vanilla Lenovo AIO with 8gb ram and AMD A10-7800 combined cpu/gpu running Windows 10. According to the installed Radeon utility the game is averaging 81.2fps but don't tell my wife it also says I have played it for 21 hours so far this week :03:

Those "Large Address Aware Utility" things are garbage software for dummies.
Please un-do that, trash that garbage program, and ignore that info because it truly is false information.

You have win10 so you have a 64bit operating system. It is true that 32bit versions of XP (which you're not using so even me saying this is irrelevant) only read 4gb of RAM no matter what was in the machine. 64bit versions of XP read more, if I remember without looking it up I think it was either 8 or 16gb ram.

You can go to Start > Settings > System > About and read the System Type in the list under Device Specifications. There is where it tells you if you're system is a 32 or 64 bit operating system. It's most likely 64 and 64bit win10 will accept and read up to 2 TB of RAM memory.

You're ok. You don't need to run such thing on 64bit Win10. All that's doing is causing your system to be confused and if you followed such a programs instructions to change your virtual memory change it back to default settings after trashing the garbage.

The proof that my info is correct?:
Hundreds to thousands of people run this game on win10 without it.
You're putting diesel fuel in an unleaded vehicle by running that crap/garbage. Shut it off, get rid of it.

Hmmm


Since I installed the 'garbage software for dummies' I haven't had a single CTD, and FPS has gone from an average 81 to 331.


I am neither a software expert, nor a dummy, but a pragmatist, so if it works, I will continue to use it.


Thanks to both of you for your input though.