Such a change in fortune!!!!

ddiplock · 03-12-08, 11:43 AM

Quote:

Originally Posted by Keelbuster

Savegame bug. Feel the pain. I'd rather pause it and let my computer run all day while i'm at work that deal with the load/save BS - especially if something important happens. Try the previous save. I find that corruption often happens in bulk, so you might have to go back two or three saves. If that's yer only save, then yea, it's blown. If you do have a previous save, at least you know when and where that TF will be right? Maybe you can do some real target data acquisition now. I figure that save crashes allow a bit of cheating this way

That was my only save. The only choice now is to restart the patrol, and try and hang around the area's where I had recieved task force reports the previous patrol. What rotten luck!!!! Whenever i'm in position to sink a battleship, fate steps in and moved the goal posts!!!

3Jane · 03-12-08, 12:39 PM

These days I always create two save points before exiting the game.

Keelbuster · 03-12-08, 01:17 PM

Arg. What a burn. Unfortunately, I sort of doubt that the TF will be in the same spot if you restart the patrol. But it will be _somewhere_. The trick is to have a highly trained radio room so you get all the contact reports. Blindly stumbling into a TF is very unlikely, but if you know their rough course and speed it's easier to get in the way of a BB.

Graf Paper · 03-12-08, 05:03 PM

I feel for you, kaleun! Losing a shot at that BB from a stupid game bug is a miserable way to end a patrol.

Don't give up! It could be looked at in the game world as your electrics shorting out due to saltwater seepage.

Another thing to remember is to avoid saving your patrol while submerged. It's been documented for a long time now that particular bug is likely to corrupt your saved patrol.

jas39 · 03-12-08, 06:39 PM

I can confirm this. If you are saving your game anywhere near either A-a burning ship, with pretty explosions lots of graphics-hungry processing going on or B-a convoy or taskforce, it usually means that the savegame will fail. This is because the game engine (which is already slow when loading a mission or campaign) somehow cant load so much info when you start the save.

I run SH3+GWX+SH3 CMDR using athlon xp 1.67ghz, 1gb ddr266 ram, geforce fx 5500 agp, 128mb. I usually get 7-13 fps on highest graphic settings, which is playable for me. However, a mission or patrol takes 9?! minutes to load, starting from the main menu, and the whole thing from desktop takes 12?!!? minutes to load from desktop.

So I always save on the surface, without any ships in sight.

bookworm_020 · 03-12-08, 08:39 PM

Ouch! I feel for your loss. Lesson to learn from this is never to save a game when you are submerged!

03-12-08, 12:39 PM	#2
3Jane Ace of the Deep Join Date: Sep 2006 Location: York. Northern England. Posts: 1,004 Downloads: 0 Uploads: 0	These days I always create two save points before exiting the game. __________________ Fate opposes me in vitality and morality, forced ever onward, burdened, always in shackles. So this very moment, without tarrying, pluck the quivering strings. Because fate punishes the one who plays, all lament with me. (http://hosted.filefront.com/KatherineRowan)

03-12-08, 01:17 PM	#3
Keelbuster Ace of the Deep Join Date: Oct 2005 Location: BA 72 Posts: 1,092 Downloads: 43 Uploads: 0	Arg. What a burn. Unfortunately, I sort of doubt that the TF will be in the same spot if you restart the patrol. But it will be _somewhere_. The trick is to have a highly trained radio room so you get all the contact reports. Blindly stumbling into a TF is very unlikely, but if you know their rough course and speed it's easier to get in the way of a BB. __________________

03-12-08, 05:03 PM	#4
Graf Paper Ace of the Deep Join Date: Jan 2008 Location: Pacific Northwest United States Posts: 1,146 Downloads: 41 Uploads: 2	I feel for you, kaleun! Losing a shot at that BB from a stupid game bug is a miserable way to end a patrol. Don't give up! It could be looked at in the game world as your electrics shorting out due to saltwater seepage. Another thing to remember is to avoid saving your patrol while submerged. It's been documented for a long time now that particular bug is likely to corrupt your saved patrol. __________________ Still sailing the high seas, hunting convoys with those who join me.

03-12-08, 08:39 PM	#6
bookworm_020 Navy Seal Join Date: Aug 2005 Location: Sinking ships off the Australian coast Posts: 5,966 Downloads: 1 Uploads: 0	Ouch! I feel for your loss. Lesson to learn from this is never to save a game when you are submerged! __________________ "There is always one person in any organization who knows whats going on, That person must be fired"

Thread Tools
Show Printable Version Email this Page
Display Modes
Switch to Linear Mode Hybrid Mode Switch to Threaded Mode

03-12-08, 06:39 PM	#5
jas39 A-ganger Join Date: Aug 2006 Posts: 77 Downloads: 25 Uploads: 0	I can confirm this. If you are saving your game anywhere near either A-a burning ship, with pretty explosions lots of graphics-hungry processing going on or B-a convoy or taskforce, it usually means that the savegame will fail. This is because the game engine (which is already slow when loading a mission or campaign) somehow cant load so much info when you start the save. I run SH3+GWX+SH3 CMDR using athlon xp 1.67ghz, 1gb ddr266 ram, geforce fx 5500 agp, 128mb. I usually get 7-13 fps on highest graphic settings, which is playable for me. However, a mission or patrol takes 9?! minutes to load, starting from the main menu, and the whole thing from desktop takes 12?!!? minutes to load from desktop. So I always save on the surface, without any ships in sight.