Hey marees62, salut montreal! :up:

Salut CaptGreyWolf...Go HABS GO!!!:rock:

Oh Ya!! Go Canadiens:up:

****, it just happened to me! After spending hours in stormy weather, taking on convoys, tracking lone merchants by sonar, I ended up making a save within 50km of a coast and a boat. I don't know for sure, but I'm pretty confident that's what killed it. The saves after it so far are corrupted, I'm working my way back to a safe save. It just really sucks to lose 4 hours of play and 25K of hard earned tonnage. :down: :damn:

It's a testament to the fun of this game that I don't take it's CD out, cover it with ebola, and mail it to the developers! Even more than that, I actually want to go back and play it some more! :o

If you are using GWX 2.0 that is definitely what happened. I read in the GWX 2.0 manual that you cannot save a game within 50km of a ship or near a location where you just sunk a vessel as I found out from my own experience.

If I'm not mistaken this is not GWX specific. This advice is also applicable to stock SH3. Having said that, I have saved close to ships and the coast, surfaced and submerged without problems, just lucky I suppose.

Nemo

Lucky I have never experienced this bug.

HunterICX

Thanks for the info, I didn't realize it was a stock issue as well as I never had a problem saving when I played stock way back when.

At best it can be called an interrmittent fault, but the risks are clearly there http://img522.imageshack.us/img522/9708/piratebf4.gif

Yes, I've saved close to ships and not lost anything before. I think it's safe to say it's a somewhat random fault that is related to being close to ships and/or the shore. It isn't a perfect correlation, but I'll take it from others' experiences and my own that it is somewhat correlated. What is for certain, is that it's annoying as hell. :-?

Oh well, back to the sinking grounds...

I've had a few save-game crashes. I always save on the surface at TC1. If there were ships nearby I wasn't aware of them. I haven't had any crashes since I cut back on the number of processes I was killing with FS Autostart.

Tony

AMD Sempron 2800+
2x512mb generic pc3200 dual channel
GeForce 6200 128mb
WinXP SP2
D2D version of SHIII loaded on SATA drive; v1.4 with GWX2

I think it's a bloody shame that in 2005 I paid for a game that might not save properly...anyways.

Aye, has happened to me occasionally too. This is what I did the last time:

The .isf and .sav files (in [driveletter]:\Documents and Settings\XXX\My Documents\SH3\data\cfg\Careers\YYY\[patrolnumber]) are the ones that seem to go bad when a save goes belly up. So what one wants to do then is to replace those with files from an earlier save, and then after the patrol edit the .cfg files in the main career directory to get the tonnage and renown correct! Tedious c**p, I know, but this I've found at least lets you continue in a pinch...

Thanks for sharing that work-around. I'm curious what other people do after the crash. Personally, I go back to a previous save that I'm confident about. It means losing the boats that I sank, which is frustrating, but I can always sink more, right? I'll just chalk the other ones that got away to "training" missions that I'm remembering.:-? I'm just disappointed that I'm losing some, IMO, really skilled kills against lone or convoy merchants, made by sonar tracking, then surface attacks, in 3 days of absolutely awful weather. Those are so satisfying that it's hard to let them go. Oh well.

NEVER.........:p

Kiss my ass. ;)