Thread: [REL] Depth Charge noise mod
View Single Post
Old 03-30-18, 10:16 PM   #39
schlechter pfennig
Commander
 
Join Date: Mar 2010
Posts: 457
Downloads: 52
Uploads: 7
Default I have discovered the source of the CTD problem

I have discovered the source of the CTDs when Depth Charge Noise mod is enabled. However, I have no idea how to find the root cause or how to fix it (assuming it is fixable).

Reports of CTDs when loading a saved game that has Depth Charge Noise mod enabled has been extraordinarily vexing. Since the CTD doesn’t happen unless depth charges have previously been deployed and exploded before saving the game, testing variables is time consuming, since it involves first being attacked and depth charged, and then successfully evading the attacking escorts. This can take up an hour, or more, to resolve to a point where the sub can surface away from units in order to make a clean game save. As well, loading missions can take upwards of 6-10 minutes, due to the loading times of some of the supermods.

The cycle of tests for this mod have, for the most part, followed this pattern: 1) run a mission without the Depth Charge Noise mod enabled, avoid attacks, save then reload; 2) run a mission with the Depth Charge Noise mod enabled, avoid attacks, save then reload; 3) run a mission with the Depth Charge Noise mod enabled, be attacked then evade and escape, save then reload; 4) run a mission with the Depth Charge Noise mod enabled, be attacked then evade and escape, save then reload.

This testing cycle is repeated for each of the following: Stock Silent Hunter III, GWX Gold, GWX Gold heavily modded, NYGM (unmodded), WAC 5.0, and WAC 5.0 modded.

In order to expedite testing, a final mod was enabled, this one consisting of three blank campaign files, so that the test missions would rapidly load.

At the time of my releasing Revision A of the Depth Charge Noise mod, I had tested that revision multiple times with all six game versions and experienced no CTDs when loading a saved game, so I was quite surprised when reports of CTDs surfaced. I went back and reran the test missions, and was stunned when loading a newly saved game it CTD.

After several hours of digging through files, checking IDs for duplicates, errors in file structure, etc., I realized that, after having run the pre-release tests, I’d disabled the blank campaign files mod. I re-enabled that, then ran another cycle of tests.

No CTD.

I disabled it, and ran another round of tests.

CTD.

I then created three different blank campaign files, isolating the _LND, _RND, and _SCR files, then ran cycles of tests against all six game versions, and got the same result each time:

The _RND campaign file somehow causes the CTD when loading a saved game if the Depth Charge Noise mod is enabled and depth charges have been deployed and exploded.

Guys, I’m at a loss here. I’ve absolutely no idea why the _RND campaign file causes a CTD, especially a CTD on loading a game modified by the Depth Charge Noise mod, and only after a depth charge explodes. It just doesn’t make sense.

I’ve no familiarity at all with campaign files. Here’s hoping someone with more experience there than I have can help me figure out just what is going on.
schlechter pfennig is offline   Reply With Quote