Armored destroyers
 

Hi
Anyone notice that when you torpedo a destroyer head on that it keeps on going like its not been hit? I actually put 2 torpedoes (one head on the other around the stern section) and it kept on coming.

I am using the T M mod and version 1.3

TJL

Maybe the torpedos are set to a wrong depth,check your torpede panel,and better set the depth to 1~1.5m.Sometimes the torpedo which detonated under the ship's keel will damage them instead of destroying them,especially destroyers.

I usally sink destroyer with one torpedo,if you hit the ammunition depot,it will blow up immediately.

Hope it will help you,good hunting!:D

A couple types are bugged and are armored in excess of a BB (or equal, anyway).

tater

could be they simply missed due to the firing angle. i've destroyed a few with bow shots and others have missed cuz the DD turned at just the right moment:damn:

And if you wait and fire at a point where the DD is almost on top of you, the torp doesn't have time to arm, nor reach crusing depth, thus either swimming under the intended target, or glancing off the keel.

yeash, there's that too, so don't shoot at less than 500yrds:ping:

Do a search for damage bubble. I believe that Werner Sobe has discovered some interesting info on the DD's damage/hit boxes....none in the bow.

Wilcke

Armored destroyers
 

Thanks for the replies. I have been setting the depth at 5 to 8 feet so I will set the torp depth much less next time
TJL

SOME destroyers, not all are bugged.

I know that because i was dealing with their zone layouts in NSM mod. So in example the fubuki and shiratsuyu destroyers are both using zones from battleships and their armorlevel is bugged making them having infinite armor on some parts.

check this link: http://www.subsim.com/radioroom/showpost.php?p=618297&postcount=355


And download this mod: http://www.subsim.com/radioroom/showthread.php?t=120269

These bugs are all fixed there and entire damage system is reworked. Make sure to read the readme.

http://www.geocities.com/aka994555/images/alhena1.jpg

In this case, it's probably the bug though. :up: