Saves Will Not Reload..Sometimes

[Seminole]

On occasion after I save a patrol at sea the sim crashes when I attermpt to reload. Not often, but frequent enough to be a hassel.

This means I have to start over back at the base...or it did...until I wised up and started saving patrols in differently named segments as opposed to just saving the patrol over and over under the same name.


Anyway is there anything that can be done to prevent these reload crashes?

I never save while submeged....I've read that can cause problems.

These reload refusals seem to occur when ever a patrol crosses over from one month to another and is then saved...but that could just be my imagination.

Any tips appereciated.

BTW: GWX 1.03/SH Commander/SHCommander dated ship skins/

Maybe I should rollback SHCommander whenever I quit a session?

[melnibonian]

That's really strange behaviour. I have no idea what the issue is but I can speculate a bit (hopefully that might help you or others that know more on the subject)

1. Do you enable/disable mods while you're at sea?
2. Do you enable/disable mods without rolling back SH3Cmd?

These are the most common issues that can mess up your game.

[Seminole]

I religiously observe both of these prohibitions..from experience.

My conviction is becoming stronger that this has something to do with a patrol overlapping different months and the dated ship skins that SHCommander uploads at the start of each session.

I have been rolling back SHCommander at the end of each session and the problem has not occurred for a few days. Fingers crossed.

[VipertheSniper]

I had this too today, still have the save game in the hope I'm able to get it working somehow, I mean it loads fine, I get to the "not so long ago..." on the screen, and then I get the infamous XP "blabla has encountered a problem" screen. I'm lucky tho, my save game before that was made shortly before I went to make a third attack on a convoy, what bugs me tho, is that after that I wanted to finally visit New York for once, and on the way I've encountered a really juicy convoy, and with 7 torps left I wreaked some havoc. Arghhh almost all lost.

[Seminole]

Yes you described it perfectly. Get to the "Not So Long Ago"...and bamo.


Thank goodness it only happens on occassion....but it does seem to like to occur after you do something spectacular doesn't it?


Like I said above, Ive been Rolling Back SHC after each session and it hasn't occured again.... so far...but I will need to play several days before I'm covinced this is the "cure."

[Jimbuna]

A ctd at the "Not so long ago" screen normally means there is a conflict with a mod. But I'm just wondering if either of you are using saved careers from a previous version of the game ? :hmm:

[VipertheSniper]

Originally Posted by jimbuna

A ctd at the "Not so long ago" screen normally means there is a conflict with a mod. But I'm just wondering if either of you are using saved careers from a previous version of the game ? :hmm:

If that would be it, why are previous save games of the same patrol working, I haven't applied any mod in the mean time, that's for sure.

[Jimbuna]

I have known this to happen to me in the past......It can only be one of what melnibonian and I have pointed out......If it persists and you can't rectify the problem I can only suggest you do a reinstall :hmm:

[melnibonian]

Also if you're using an "old" career (created with an older version of GWX) there is a chance the new 1.03 version cannot cope with it. I've noticed that my GWX 1.00 careers were compatible with GWX 1.01 and 1.02 but cannot be loaded in 1.03.

[Seminole]

Nope, the only career I have is the one started after a clean install of SHIII/1.03...and there are no mods other than 1.03's Lite Harbor and Reduced Bouyancy.

Never had the problem with Type IIA boats doing one month North Sea patrols. Only started after I moved to the VIIs and started staying out over 2-3 month time peroids.

The problem isn't sufficient to warrant a "clean install' since the career can be salvaged from judical saves....and especially a clean install isn't warranted when I don't know for certain what is causng the glitch. For all I know ,after doing all that, I would still have the same situation....:hmm:

[melnibonian]

I'm really sorry for that. Unfortunatelly I can't think of anything else, but I will look into it and if I find something that can help you I will let you know.

[Seminole]

Originally Posted by VipertheSniper

If that would be it, why are previous save games of the same patrol working, I haven't applied any mod in the mean time, that's for sure.

Again...you nailed it exactly. Most previous saves load and work fine. It is seemingly a "rogue save" that occasionally craps out....and there just has to be a reason....and so far my guess is a good as any.

[down and out]

Originally Posted by Seminole

BTW: GWX 1.03/SH Commander/SHCommander dated ship skins/

It maybe the SH3Commander skin pack
Try removing that and see

IIRC it was recommended NOT to use that skinpack with GWX

[Seminole]

Where did that reccomendation come from?....


On page 27 of the GWX manual are detailed instructions on installing using the SHCommander skin pack.... ... ....


It has been 3 days now since I had a reload screw up, after I started rolling back SHCommander after each session. I am hoping the problem is fixed....

Thanks for the advice.

[gabeeg]

Seminole,

I have the exact same behavior you and others have described. I too am going to start rolling back SHIII Commander and see if the "rogue" saves go away. They seldom happen as it is...but just enough to be an irritation...last time it happened was when I had just sunk a fat liner..really ticked me to have to go back to a previous save.

I will try and remember to come back to this thread after a couple of weeks of heavy play and post my results.