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

[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

[flyingdane]

I have played this game since it came out!..And all i can say is that i have never had this happen, (This is why) When I save" I just save game,
.. with name or number and..or overwrite".. then push "return to base, then main menu then...exit.

When i do it this way i don't get the save game bug!

[P_Funk]

I never had these save issues. Though it has been finicky for no reason sometimes.

Its possible that this game has certain code errors that cause it to act funny in all kinds of random ways based on subtle system based characteristics, ones that aren't always realted to Mobo or CPU or particular hardware. Basically though whenever I've had issues with SH3 that cause this much grief I've reinstalled it.

You know maybe theres a corrupt file or two in the installer that buggers the install sometimes.

I don't know enough about computer coding to know if my conjecture is anywhere near realistic but certainly this isn't a simple issue.

I'd suggest a clean reinstall.

[Venatore]

mate, never heard of this one before. I hope you find what the problem is soon. Hang in.

[Samwolf]

Originally Posted by P_Funk

I never had these save issues. Though it has been finicky for no reason sometimes.

Its possible that this game has certain code errors that cause it to act funny in all kinds of random ways based on subtle system based characteristics, ones that aren't always realted to Mobo or CPU or particular hardware. Basically though whenever I've had issues with SH3 that cause this much grief I've reinstalled it.

You know maybe theres a corrupt file or two in the installer that buggers the install sometimes.

I don't know enough about computer coding to know if my conjecture is anywhere near realistic but certainly this isn't a simple issue.

I'd suggest a clean reinstall.

I've done clean reinstalls and sooner or later this problem pops up again, sometimes it takes a while but it's always shown up.

[Samwolf]

Originally Posted by 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

Except for the "yellow crew" last mission and the invisible wacth crew with binocs, I haven't really run into graphics problems with this game, I have with other games, and I know that's frustrating too. Did you ever get it resolved?

[Faamecanic]

Originally Posted by Samwolf

Except for the "yellow crew" last mission and the invisible wacth crew with binocs, I haven't really run into graphics problems with this game, I have with other games, and I know that's frustrating too. Did you ever get it resolved?

Nope it never got fixed. And that was about 10 Nvidia driver realeases ago... (I was using the 71.xx detontator drivers back then...up in the 91.xx now)

That is also after at least 3 reinstalls, the last of which I did Fresh and did NOT bring over my SHIII game folder from the previous install.

[Samwolf]

Originally Posted by Faamecanic

Nope it never got fixed. And that was about 10 Nvidia driver realeases ago... (I was using the 71.xx detontator drivers back then...up in the 91.xx now)

That is also after at least 3 reinstalls, the last of which I did Fresh and did NOT bring over my SHIII game folder from the previous install.

I'm running a GeForce FX 5200, hoping to be able to upgrade for Christmas.

[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.