Now I remember why I gave up on SHIII after it first came out

[Syxx_Killer]

This is the first time I heard of this crush depth save bug. I have literally saved hundreds of times both above and below and have never run into this bug.

[sh3rules]

I had to reinstall once because I couldn’t load any saved game. After reinstalling it never did it again. But I never experienced this bug.

[Tuddley3]

You may have to start that career over, sounds like something happened to your mid patrol file.

Did you add any mods while you were not in port, this makes weird things happen ?

[stabiz]

Strange stuff, tuddley. :hmm: I have never - yes never - experienced any of the save bugs myself.

[Samwolf]

Originally Posted by Tuddley3

You may have to start that career over, sounds like something happened to your mid patrol file.

Did you add any mods while you were not in port, this makes weird things happen ?

No, that's what makes it so frustrating. It seems that not all users experience this. Makes me wonder if it is system related somehow.

[shegeek72]

Originally Posted by Samwolf

No, that's what makes it so frustrating. It seems that not all users experience this. Makes me wonder if it is system related somehow.

I experienced something similar when I first got SH3, though not the sub crashing, just saved games not loading. I found when I didn't overwrite, but created a new save each time helped. But it went away completely when I installed GW.
--

[THE_MASK]

What are you saving the games as . For example i use the grid coordinates such as AD18 , AM21 etc . I never get the problems with the saves . If however i use say , words like CON(short for convoy) or convoy it will eventually break the game . If i have to save again in the same grid , say AM21 then i just overwrite with AM21 again . Never had a problem .

[Faamecanic]

This is one bug I have NEVER had. And I save with no TC, no grammaphone on, and never around other ships. I DO save with grid names (AK38) and also AK38conv and such....

This game is very finiky with systems it seems. I have a strange graphics bug where if I use my attack or obs P-scope it turns off my Anti Aliasing (get jaggies BAD) on any external views, and also only HALF of my crew screen. If I use the UZO after any P-scope it turns my Anti Aliasing back on. See this if your curious as to what Im talking about... http://forums.ubi.com/eve/forums/a/t...223#2711043223

Wish I could help ya SAM...I know this has got to be frustrating

[Samwolf]

Originally Posted by sober

What are you saving the games as . For example i use the grid coordinates such as AD18 , AM21 etc . I never get the problems with the saves . If however i use say , words like CON(short for convoy) or convoy it will eventually break the game . If i have to save again in the same grid , say AM21 then i just overwrite with AM21 again . Never had a problem .

I use 3 "save game" names but never overwrite.

Format is:
P#Intel
P#Save#
P#Sunk#

Where the first # is Patrol number and the second is the next sequential number within "sunk" or "save". I use save if nothing happened since the last save and sun to keep track of ships sunk.


So my save career looks like this

P1Intel
P1Save1
P1Sunk1
P1Sunk2
P1Save2
etc

What is really frustrating is that it doesn't always save corrupted So you never know when a file is bad. Like I said I played for a few months with no problem and then it shows up.

I'm testing a few things to see if I can track this down, so for now I've given up trying to play a career.