SHIII HAS STOPPED WORKING

[fastfed]

WTF!!

I think I remember why I was always frustrated with this game.. It wasn't the escorts!

3 different PC builds and my latest one

I5 2500k OC'd 5GHZ
8gigs of ram
running it on a 120GB SSD
6870 vid card

and I still have these issues..

Every so often the game will just lock up and I get the message SHIII has stopped working..

I'm running the Living SHIII mod, I ran the 4gb patch.

Was there ever a solution to this problem? or is just something we have to deal with :(

[flag4]

...i doubt its your rig.
maybe some combination of in-game mod set up. saved game issue - ive had that before.
what mods are you running, have you noticed conflicts whilst installing?

[Kapt Z]

I get those every once in a awhile. Not too often, maybe 1 incident every 5-10 patrols. It's usually just as a save is almost loaded, but has happened during game play as well. Figured it was just a corrupted save. They 'seem' to also occur right after my pc has run updates or if some new software has been updated. May be coincidence though.

No idea what to do about it. I just reload the previous save and it works fine.

[Raptor]

CPU: AMD Phenom II 4x 970 Black Edition 3.5 GHz
RAM: 8 GB DDR3 PC3-10600 unbuffered
VIDEO: Sapphire (ATI) Radeon 5770 (! GB)

It is not a hardware issue. SH3 barely challenges my system. I can get 4096X TC with frame rates of 100 or better.


I've had the same issue with SH3 stopping on occasion (I'm running GWX Gold). It is almost always while trying to load a prior save........the loading bar just about finishes when the black screen of death appears, or the loading bar finishes, the usual "Not so long ago" message appears, and I wait forever for the control room to light up. CTRL-ALT-DEL reveals that SH3 has stopped working...etc.:hmmm:

I have learned to save several times enroute to and upon reaching my patrol area, after every ship sunk, and at least every other game day if nothing is happening. Then if the most recent save ultimately crashes during reloading, I have something to go back to.


On occasion, that first refusal to load corrupts that entire mission, no matter how many saves. I once had it take out the entire game - not even a new career would load. Had to rip out SH3/GWX and reinstall everything. :damn:


Ideally, I don't save and exit mid-patrol. If time allows, I just pause the game and let it run in the background while I attend to whatever interupted me. THat seems the wiser and safer way to go

[VONHARRIS]

Ideally, I don't save and exit mid-patrol. If time allows, I just pause the game and let it run in the background while I attend to whatever interupted me. THat seems the wiser and safer way to go

I am doing the same thing.
It helps a lot. :DL

[Harald_Lange]

Not sure if its definitely true but I find its safer to save when there's no 3D stuff happening. Ie you're not in periscope view, your not being hunted, no planes etc. I always save o n a static screen like crew management or radio log. I've greatly reduced the number of CTD occurrences that way.

[RConch]

I too have lost missions and tonnage due to a corrupted save. I have never lost a whole career, thankfully.
Just had to go back to "in base" before mission and try again or if I feel uncomfortable-just pull out of harbor and then end patrol and try my luck at the next assigned grid.
My biggest headache is forgetting the, for me, cardinal rule to never load or change anything in mission. I only alter mods when I start a new career. After that-no changes till the next new career.
As Raptor implied-save,save,save.