Sonar Destroyed Sir!

[Geoff-A]

In my ninth patrol now, but as I started my eighth and as I started this one, the very first message I got was 'Sonar Destroyed Sir' even though once out into the patrol the Sonar worked fine.
No, not air raid damage as I start and finish in a pen and when I get the message I have not even started the engines yet.

I start through SH3 Commander, using GWX2, and yes - I have the sabotage box checked. Could this be a little sabotage taking effect?
Has anybody else had this? Not annoying or anything, does not affect the game-play at all but was curious as to the cause? :salute:

[GoldenRivet]

a few possibilities come to mind. Let me dust off the cob webs

First possibility, i believe that when something gets crossed in the mods, your submarine is accidentally equipped with a type of sonar on a specific date when the game recognizes that the type of sonar you are equipped with within your eqp file is technically not available until a later war year. the game recognizes that it is impossible for you to have a type of sonar in 1940 that didnt exist until 1943... so when your boat spawns, it defaults to the available sonar type that you should have and in an instant the later war type of sonar vanishes and you get the "Sonar Destroyed Sir!" message. If you are running JSGME to enable mods, you might exit the game, roll back SH3 Commander, disable the "Late war sensors" mod if you have it enabled and then run the game. If upon starting a mission the "Sonar Destroyed Sir!" message has gone away... that mod was your problem, and you would be best to utilize that "late war sensors" mod only late in the war. - but this one usually is associated with the "Radar destroyers Sir!" message, not the "Sonar Destroyed Sir!" message :up:

second, there is a possibility that in your JSGME you have the "Type VIIC player sub" mod enabled. this one also wouldnt come along until later in the war and if you have it enabled, it has been known to cause this bug if this sub type is used at a historically inappropriate date. others have reported disabling this mod and the "Sonar Destroyed Sir!" bug has gone away :up:

third possibility, if you have several mods enabled in JSGME, one or more of them might be conflicting with one another and something is getting tangled in the process. exit SH3, Roll Back SH3 Commander and disable all the JSGME enabled mods... then enable one mod... run the game... check for error... exit.. roll back SH3 commander and enable one more mod. repeat the process until you have Identified your offending mod. once identified just disable that particular mod. :up:

fourth possibility, which i dont buy into, some folks have reported this as being "just a bug" which they have experienced with SH3 for ages. however i have never experienced this bug in an unmodified "vanilla" version of the game, so i dont think SH3 was born with this one. this one was brought on by the community. if possibility 1, 2 and 3 produce no desirable results... perhaps its just this explainable fourth possibility here. :06: