I have upgraded from SH3 commander 2.4 to 2.5 and am now also getting this gremlin in the works. So far only my stb desil is 'destroyed'. I have been running SH3 via Sub Cmdr 2.4 successful with no glitches at all. Until the upgrade.

My Mods are as follows:

GW ver 1.0
Tonnage War Mod ver 1.03
extended unified campaign [GW/NYGM]
original rudder guage
1500 bearing overlay
alternative dial faces
aces high res uniform mod
imrpoved insignia mod
enhanced nav map plotting tools
atomsphere mod v2 16km light
SHIII NYGM crew managment
GW-IOU update
JCW uboat faces

I installed 2.5 as per the instructions. I have now gone back to 2.4 but the problem still occurs.

I have been running several careers at different time periods and with different boats, all my careers and boat types are so effected.

hope this bit of info on mods being used might help.

hope the gremlins can be erradicated.

have always loved SH3 commnander, so hope the issues can be resolved. :D

Let's go back a step - is anything actually destroyed? Or is it just a message that appears?

Does it just happen when loading save games, or also when starting "in base"? Does it happen with new, freshly started careers? Have you installed *any* of your mods, including SH3Cmdr whilst mid-patrol?

Sorry, but if you guys want whatever it is fixed, you really need to do some thorough testing. Circumstantial evidence may sometimes be nothing more than a red herring...

Anyway, some suggestions...

FULLY remove SH3Cmdr (ie delete ALL files and folders EXCEPT SH3Cmdr.ini), then reinstall SH3Cmdr R2.5.

WITH SH3 v1.4b ONLY installed (ie NO mods or changes):
1. Start a new career *without* SH3Cmdr. Save mid-patrol. Exit SH3. Reload SH3 direct and reload the save game. Note any messages.
2. Start a new career *without* SH3Cmdr. Save mid-patrol. Exit SH3. Reload career via SH3Cmdr and reload the save game. Note any messages.
3. Start a new career *with* SH3Cmdr. Save mid-patrol. Exit SH3. Reload career via SH3Cmdr and reload the save game. Note any messages.
4. Start a new career *with* SH3Cmdr. Save mid-patrol. Exit SH3. Reload SH3 direct and reload the save game. Note any messages.
5. If any of teh above results in the message, delete \SH3 Commander\Cfg\Miscellaneous.cfg and \SH3 Commander\Cfg\Randomised Events.cfg. Repeat tests 2 to 4.

**Don't recycle careers - start fresh ones for each test iteration. For consistency, start all careers with the same settings, including flotilla, start date and sub type - notate these settings.**

REPEAT the full test cycle WITH GW installed and note the results. If the results are still inconclusive, START a NEW career WITH ONLY SH3 v1.4b installed, start and finish a patrol. INSTALL GW, load the career, start and save mid-patrol. Exit SH3. Reload SH3 direct and reload the save game and note any messages.

Keep testing different years, flotillas and subs until you identify problems. Then note what's different and continue to hone in on the problem.

In the absence of a magic wand, this is prolly the only way to get to the bottom of the problem. Post back your results.

Kpt Lehmann: Perhaps unrelated, but I was just searching through the archives and found a similar message way back last year about repeating "rudder destroyed" messages. Anyhoo, the problem was traced back to zones.cfg. I just had a look at zones.cfg in relation to this issue, and noticed that the [DieselEngine1] HitPoints is 180 yet the [DieselEngine2] HitPoints is 130. I am *assuming* that 1 is port and 2 is starboard. Why the difference? Could it have any bearing here?

Anyway, I see the problem (or one similar) has also existed prior to R2.5... http://www.subsim.com/phpBB/viewtopi...ight=destroyed I've searched the forum archive and excluding the known sonar destroyed message for the IXD2, there's a number of posts from people since around mid-last year (before SH3Cmdr) with similar "x destroyed" messages on patrol startup. No solutions though.

Does IUB and GW share any files/settings? It may be coincidence, but the problems are shared by users of both mods.

@ JScones - How to email the file to you? (sorry the noob question) :oops:

I'd probably load it into my by weby and give you a link to it...


Now regarding your question.

Let's go back a step - is anything actually destroyed? Or is it just a message that appears?

In my case, it appears not to affect the equipment at all.

This glitch is just that missleading message (which also shows on "F7" that item X is destroyed - in red). However everything seem to work fine, stb diesel engine, radar (and now with IXD2) the sonar... like I said in one of my previous posts... its just anoyance than a problem.

BTW is there a way to clear the sub from upgrades (while in the base)?

So to start a new mission without any upgrade... then reload and try the same but reassigning new upgrades? to see if this issue continue to appear? Thanks

Cheers

That's fine.

The sonar destroyed message on the IXD2 is a well known SH3 bug. It is NOT SH3Cmdr or mod related. The radar error has also come up before - apparently it's to do with the placement of the radar on the boat, but it still works. It's the second most common example I found when I just did my forum search. The stb diesel message, well that seems like the new one.

The other common thread I found through my search was that the problem more likely occurs with upgrades (for example the Nibelung sonar on the VIIB and schnorkel fitted radar on the type XXI). Have you upgraded your equipment, especially the diesel engines or radar? If so, perhaps downgrading in SH3 may help. Anyway, here's some earlier analysis... http://www.subsim.com/phpBB/viewtopi...destroyed+ixd2

I have yet to experience anything except the usual rudder damaged repeat so am at a loss.

I popped the hp of rudders up to 1000 cos I did not want to hear it as much. I still think it comes though so I suspect hardcode issue.

I will look at the sub.zon files as I remember Jungman reporting weird issues when we played with them but I think this was only hp and armour levels.

Maybe it is time to re-visit the sub model but I would hate it if this was not related to the faults reported. Mind you I am currently re visisting everything so will try and set a new one up based on new knowledge.

The sub zones may need checking over and comparing to the original.

I have tried to warn about setting things to destructable or playing with this and that as I had problems when I did this. I will check the ships, planes and subs to see if any obvious mishaps have happened.

There have been some adjustments to the zones.cfg that have not been done by myself. It is time for a proof reading session

Personally I would be suprised if it had anything to do with the damage model as modded cos I am not getting the issues.

Have patience,

I will check my side but I am away for 3 days so this may take some time.

@ JScones - email(s) sent :)

Now, regarding your last post, about sonar issue.

What am about to write would probably backup what you mention.

After I've read your post, I removed SH3C2.5 from my system again, after rolling back SH3 files (using SH3C option)

I wanted to replicate my previous sucesseful test (that I post its results this morning), which were:

Starting SH3, loading the game (while in the base) and not getting the "sonar destroyed" error message on my IXD2.


Now the results are:

1st attempt (without SH3C installed) got "sonar destroyed" :hmm:

2nd attempt (also without SH3C installed) nothing was destroyed :doh:

Oh! well I'm now confused and tired of this. :damn:

ve started a career in gw with a XIc/40 from bordeaux. everytime the game starts off im getting a strabord engine destroyed message, and its actualy marked as destroyed in the damage control screen. it dosnt seem to have influence on my boats perforamance tho. is it me or is this a bug?
is this a known issue? i have to say that i never played with a XIc/40 before.

im using gw + unified camp + latest sh3 cmd. i had 2.4 sh3cmd before, and deinstalled it before i put up 2.5 in it.

So are people getting these messages in vanilla games with no mods at all?

This is something definately with SH3 Commander 2.5. Before, never got this message: now, only when I play a scenario with type IX. Does not happen all the time, but I get the message, and in crew management/DC window, the stbd diesel is marked destroyed. But is not really destroyed.

I have RuB 1.45z, Btty mod, NYGM crew management mod, and IXD2 torp fix. I was running 2.4 and all was OK.

Maybe something with random files :hmm: I did go back and change the crush depths of all boats and the upper/lower limits. Also changed the time DDs search after losing contact......

:damn: :damn: :damn: Have you actually read any of this thread??

The link I included in one of my posts above suggest that "x destroyed" messages are prevalent in stock SH3. I found others too that suggest the same.

As I said, the sonar destroyed message for the IXD2 is a well known SH3 bug - been there since day 1. Not related to SH3Cmdr and not fixable by SH3Cmdr. More here http://www.subsim.com/phpBB/viewtopi...onar+destroyed (last few posts on page 1) although a forum search will find *many* discussions on the matter dating back to March last year. You'll also see it mentioned on the known SH3 bugs list.

The radar destroyed message is also not SH3Cmdr - it occurs because of poor placement of the radar. Again, not SH3Cmdr related, not fixable by SH3Cmdr and discussed many times on this forum. Such topic are here http://www.subsim.com/phpBB/viewtopi...onar+destroyed and http://www.subsim.com/phpBB/viewtopi...adar+destroyed

You'll also get various equipment destroyed messages if you start an IXD2 or XXI in a subpen - the equipment is too big for the pen and gets destroyed. Another known bug.

I am not interested in these already identified SH3 bugs.

You must understand that as these bugs are in the core SH3 they will also be apparent via SH3Cmdr. As you have already determined, they occur randomly. Anyway, if you are still convinced that they are related to SH3Cmdr, search the forum archives: "sonar destroyed"- all terms. FYI, SH3Cmdr did not exist at all until July last year, and even then was quite crude compared to now.

Anyway, that only leaves the stb engine destroyed message. That's all I'm interested in. On this topic, the last few posts seem to relate it to the IX. Are we talking IXB, IXC, or IXC/40? What upgrades do users have? Does anyone get the stb engine destroyed message with any other sub type? If it is just IXC related, I may have a tweak that you can try.

Yes... :-? You said in one response that vanilla version was getting message... I NEVER got the destroyed message before loading SH Commander 2.5 :stare:

Just trying to help.....

Just two wild shot in the dark ideas:

a) What if there is a corrupted zones.cfg with the starboard engine having zero hit points.
b) What if changes in the basic.cfg by GW in availability of engine upgrades either before they are supposed to exist or forced as default engines to the boat.

BTW the sonar destroyed in the IX boats and the radar destroyed in the XXIs are stock game bugs.

Best,

VonHelsching