CTD for every saved game
 

I've SH3 with GWX Gold. Everything is ok but, when I save a game during a patrol, I can't load that get. More: I can't load any game, unless I am in base. In the middle of a patrol it's impossible.
Can anybody help me?
Thanks
Antonio

There are many reasons for CTD on saved games. Too close to land, saving submerged, visible ship contacts, etc.

I saved my game two days ago when I had a damaged cargo ship despawn outside Hartlepool. It just disappeared. I was quite angry.

I was submerged, within sight of the piers, numerous contacts pierside and 2 ASW trawlers prowling in visual range.

I started up my saved game last night without any problems.

The only thing I did differently than the many CTDs I'd had before?

I removed the Read-only flag from my SHIII game folder and all files within.

Haven't had a CTD since.

It may not save your current game, but try it. I am sure this will minimize such instances in the futuure. It worked for me.

Thank you very much
 

Looks very helpfull. Goona try
Regards,
Antonio

First time I've heard of this 'fix'...watching with interest :hmmm:

I discovered this nugget mining the many past CTD threads. I have no idea which one.

So far, so good. Restarting the above mentioned saved game was the first time I've tested it since I made the change a month or so ago.

Well if it turns out it works, it will indeed be a golden nugget :yep:

Ticking off the read-only attributes has worked for me too. I have not had a single CTD after the change.

Not wishing to come across as being 'negative' but I'd like to see a period of time elapse and a lot more witness experiences....will adjust my files on an additional installation tomorrow :up:

Sounds like good news.:woot: Especially for those dreadfully long patrols with type IX.

Now how is this done?

Right click on your main SH3 game folder and select properties. Down near the bottom of the pop up window there should be a 'Read only' attribute. De-select and apply.

At this point it'll likely ask if you want to apply the changes to all files inside the main folder. Say yes, sit back and watch it work.

Note: This may vary slightly from OS to OS but it should give you the general idea. :sunny:

Thanks Fish, I'll give it a test in evening.

You're welcome! :sunny:

The problem with the save game CTD bug is that you can go months and months, even years without an issue, saving in all kinds of situations, then bam you get a bad save. As Jim says, a long period of time needs to elapse before a potential solution to this problem can be given the thumbs up. Having said that, anjutosi seems to be constantly getting the problem, so if unchecking the read only attributes of the SH3 folder works for him, then it is certainly a step in the right direction.

Nemo

I don't think it sounds "negative" but realistic. We'll have to experiment.

I did this change in mid-May and have made at least one save game since that almost every day, sometimes two saves a day. I haven't played much SH3 in August, but played almost every day in June and July. My estimation is that during that time I have had at least 40 - 60 saves and no problems whatsoever - it doesn't even seem to matter if there are ships in close proximity.

Before the change I had a CTD in perhaps 1 in 5 saves. In fact so many and so regularly that I started avoiding saving when possible.

I have had a save game problem with Windows, PC games and read-only attributes before, as well. The saves I made with Panzer General II didn't work in a new Windows operating system (XP) before I noticed that the files were marked read-only - not by me, probably it was done automatically by the operating system.

Of course, I'm not at all sure if this is a solution to the CTD problem, but it would be nice for people to try it. If many ppl try and many ppl find it helps, we know there's something to it. If many try and there are only a few who find it helpful, then we know it isn't the solution.

So far I tend to think the read-only attribute thing might really be quite helpful, from my own experience. One experience is nothing, though, more feedback is needed.

If this really is about read-only attributes, there would even be a bigger explanation on why nothing has been done to this problem before, Microsoft wanting to make foolproof and secure operating systems and disregarding the needs of the gaming society - there's not much money in old games, compared to all the offices and workplaces everywhere that need operating systems that can't be changed much by the layman user. Even if Microsoft knew about this kind of problem, it would be tempted to keep quiet about it, because if people started to tick off the read-only attributes from the wrong places, that would probably effect the security of the computer. And what comes to Ubisoft, even if they knew about the problem, they would be tempted to keep quiet about it too, they wouldn't want their customers to start ticking off the read-only attributes and perhaps find out their computers security compromised.

problem soved
 

Read only was read only and I couldn't change it.
But I found a solution.
SH3 EXE file, properties, compatibility: check XP compatibility and ckeck "run as administrator". That's it.
Good luck
Antonio