She-wolf, I have found that there are two save-related actions which consistently result in in-game problems, and if I avoid these two, I get consistent uncorrupted saves with absolutely no in-game problems (that weren't coded by UberSoft!). One is: NEVER over-write a saved game. The save process is much more elaborate than just writing out a single file, and there is apparently a bug somewhere. Always use a different name for the saved game than any currently existing save. If you want to use the same name, delete the existing file first. Do not try to save to an existing save.
The second action: NEVER change the mod load between saves, unless the save was an automatic in-port save between patrols. Any change to the mod load can produce inpredictable in-game performance. There are probably some mods that won't cause a problem - sound mods, for instance - but, if you value the career you're working on, avoid any and all changes just out of prudence.
Since I began following these two rules I have had ZERO problems with the game. I run RFB with RSRDC and a boat-load of other mods. I can save in the middle of combat, dived, surfaced, with or without my lucky rabbit's foot, etc, etc, and the game restores perfectly. YMMV, but I'd urge you give these two restrictions a try.
|