Thread: [REL] Depth Charge noise mod
View Single Post
Old 03-09-18, 12:46 PM   #24
schlechter pfennig
Commander
 
Join Date: Mar 2010
Posts: 457
Downloads: 52
Uploads: 7
Default

Quote:
Originally Posted by Rhodes View Post
Is any one using/testing the GWX version of this mod? If so, is there any problems detected when loading a save game?
I had a CTD issue when loading saved games, using this mod.
So, for the sake of the discussion, 2 things:
1. Saving: my saves are done regarding the rules for not having failed loads. Saving away from land, enemy or any unit, at surface, at TC 1x, when in the control room, after some time at maximum TC with out any hicups (normal sign of a enemy unity near the boat).
2. Mods: the mod was loaded, after rolling back SH3 commander and before beginning a new patrol.

The problem:
I enable the mod and run the single mission, all fine. Went to use it in my campaigns. I normally do 3 to 4 saves during a patrol, with the latter being the save and exit. I began to have CTD when loading the save files - CTD occurring after the black screen with the letters (Das U-Boot in my case).
At the beginning I didn't pay much attention, since corruption in saving can occur, do to factors (ex: even regarding all the "safe rules", an airplane could popup and you know). And the only save I could loaded successfully was normally the first one, done after exiting base or at mid patrol route.
After a few times having this problem, I remember that it could be something to do with this mod.
It was the last thing to enable and all the problems of the CTD occured in saves that I done after been engaged and consequentially depth charged by destroyers. The only working saves were the ones that I dind't had experienced any enemy action. So went to test my hypothesis.
Type VII campaign, went on patrol. Saved at mid patrol, no enemy engagement. Convoy detected, attacked and dived to espace. Detected by escorts and depth charged. manage to escape and after all the enemy units had gone, surface and went away. Saved. Rinse and repeat.
When, in next day went to load the game, all the saves after having sink and been engaged by enemy units, give me CTD. The only one that I was able to load, was the first one.
I decided to see if in my type IX campaign, had the same results, could be some incompatibily with the mods that act directly in type VII (aces super turms, the added interiors, etc.).
Same results, any save after the mod was used by the game, after I was depth charged, failed.
So, next step, installing the mod and see. Load the campaign, went on patrol, depth charged, etc. Saved.
Went to load my last save and it loaded fine. Type IX, also.

So, this mod, when the game uses it and at least for me, cause some kind of corruption in the saves. Or, of course, it can also be some incompatibility with my mod soup - when enabling it by jsgme, the only message was that the readme file was already been modified by, but this is a non important file, but do not think so.
Any similar problem for GWX users? Any thoughts of this singular problem?
The reason I stopped using GWX and started using WAC was that I could not load any saved game without getting a CTD once I had engaged, and sunk, a ship. That was before I'd worked on, and started using, my depth charge mod. I believe it was most likely a result of my mod soup that did so; I'm not blaming GWX at all. But I was experiencing the same CTD issue: my first save, made just away from base (and before engagements) would be the only one that would reload; any other save made after that one, if made after an engagement, would CTD. That was happening to me before using my depth charge mod.

What happens when you disable the mod? Can you then reload a saved game after being depth charged?

Also, what was your opinion of the effects of the mod? Did you notice any difference in escort behavior? I'd love to know your opinion, and if you think it needs any tweaking.

Thanks!
schlechter pfennig is offline   Reply With Quote