I know i'm kinda reviving a dead thread, but eh.... I just started having this problem. Funny thing is that it didnt happen untill i added my first mods (Natural Sinking Mechanichs and Pacific enviroments) I was in office when i enabled them, but was halfway threw my carrer. maybe this had someithng to do with it? I'm just gonna try starting a new carrer and see what happens, after deleting all saves and a disk cleanup.

Welcome aboard :up:

When you added the mods did you start off in port? If not, return to port first before adding mods. That is the safest way and it doesn't matter if you are halfway in your career.

I am not going to read all the above so if this is duplicate info, sorry.

Here's the deal on corrupted saves, at least in part--corrupted saves happens to a lot of us, modded and unmodded, for apparently a lot of different reasons. I don't know of a single all-encompasing fix. So--here is what you do to protect yourself. First of all, name your saves somthing--tmo1, tmo2, tmo3. Like that. Only keep three saves and just overwrite the oldest one each time you save. Second, and this is important, do not delete your most recent 'When_leavingPort' save. That's not exactly the right spelling but you get the idea. By always keeping that save if you get a corrupted career that won't reload all you can do is reload the "When_leavingPort' save. That way you do not lose your whole career, just the last patrol. Each time you start a patrol delete the previous ones but not the one for the patrol you are now in. Hope this is clear.

@ Fearless: Yeah, i was in port when i enabled the mods. I was following a tutorial and thats what it said to do.

I already save my games under different names, a habit i have had after i lost a save file from a different game thati had put countless hours into. I guess we are all just gonna have to grit our teeth and bear it and hope for a patch.


LtAirForce

I had this problem so bad that I did a clean install, destroying a career in which I already had two CMOH and it was only the end of '42.
I have subsequently tried to stay within the guidelines above altho I don't think it's that necessary.
What I have seen work best is that you have to let the program run until it's happy to stop. What I mean is if something big is happening, like you're taking damage/sinking, and you just want to abort and re-load, don't do it. Let it run out and then re-load. Also don't try to switch screens fast if something complex is happening. It seems to stay more stable under these conditions. No need to reinstall either. When the problem does occur, it appears to clear at the end of that patrol.
I just completed a patrol in which I torpedoed eleven ships and saved the approaches to same multiple times with no problems holding to the above guidelines.

Just got done reading the last 4 pages as it is happening to me now on patch 1.4, the crash after the please wait screen. As a few posts back have stated, you can reload usually from the leaving port save, you bet. That is back at the beginning as none of the saves during the patrol will load. Going to try different versions of the above mentioned ideas, but man, you would think somehow, somewhere, someone (Ubisoft or a modder) that has the amazing ability to read these games files and makes adjustments would find a way to make save work. Even if I had to run a program in the background to save and load from it would be better then loosing an entire morning of work.
Yet, Here I go back into the game to do the patrol over again..... I swear we are sheep lol:damn:

the main problem is the "random" part of the AI, the fact that it is random means the game doesnt have the ability to regenerate a random AI event like a ship traveling at the same spot, speed, and direction. if this were changed then every single event would have to be planned and scripted which would ruin the whole feeling of the game. to save the kind of data to recreate everything would fill your hard drive.

Strangely I havent had any of these issues and I have alot of saved games.

I use this scheme... I have the usual autosave on entering / leaving base.

Then I have a series of 'named' saves x1, x2, x3, x4 I step through and over wright those saves 'in order' as I go. I save every half hour or so. When I reach x4 I start overwrighting x1 etc.

I did notice that when I first loaded RFB it took a looooooong time to save, in the order of 5 minutes or so. I dont know if this is actually related to the mod or not but the first time I passed it off as froze up and rebooted. The second time I went to the bathroom, got something to eat etc. basically 'waited it out' and the save would finish and return to the game. But after two or three of those looooong save times its back to 'normal' and only takes a few seconds.

Now... I sure hope I havent cursed myself.... at least I have a 'recent' save game to go back to :up:

I think the reason these issues haven't been fixed yet is because the cause hasn't been pinpointed. Some peolpe have issues, others don't. I, for one, never have these issues. I save whenever, wherever and it's all good. Others stick to specific rules (no saving underwater or near contacts, for example) with mixed results.

To me, it is the most illogical and puzzling issue with SH4. :-?

Hold on... :hmm: yes, once. RFB was generating insanely large save files. Figured out it was because of the replay data always getting saved. Ran out of discspace, so I opened up the folders with the save-games and deleted the replay data. All save-games got corrupted, even the ones I didn't mess with. (deleted the temporary replay data as well, in an effort to make it impossible for the game to save it) :shifty:

I loaded a war patrol, let it finish loading till I was standing in the control room, facing my XO. Then I tried loading a save-game I hadn't messed with (but wouldn't load before) and it worked!

Maybe it can be of some use to someone in the future. :hmm: