Torpedo Attacks
 

I have a question for you torpedo shoot'n gurus:

I have been playing SH4 for awhile now and I've run into an interesting behavior. I just started using the sub's TDC. I was using Gutted's Solution Solver and Sub Buddy and have had great results. All torpedo's hit where I calculated. There is the occasional ship that decides it doesn't want to sink on that particular day :D. Using the sub's TDC I keep hitting aft of where I calculate. Most of time, I get mortal hits.

As a general rule, I use the nav map to get the targets course then use the tools mentioned to get the rest of the data.

I'm wondering what I need to tweak to have better control. :hmmm:

Torpedo Mods:
Webster's Improved US Torpedo v2
Perfect Torpedos v1

Thanks!!! :salute:

Couple of observations.

1. The stadimeter pretty much sucks - you'll get better range estimates from your OOD.
2. AOB can be easily determined if you have map contacts on. Without it on, AOB and course are dependent upon accuracy of your range and bearing measurements.
3. Speed measurements can be done from the map and plugged into the TDC.
4. Sonar will give you a range/bearing as will radar also.

A "proper" way to get TDC to generate a solution purely using the scope:

1. Stadimeter to get range. Send range/bearing by hitting the send button twice.
2. After three minutes, do it again. This will give you course. Turn on the PK
3. Dial in AOB based on targets true course and hit send twice.
4. Get another range and bearing.
5. Have crew estimate speed based on this and send twice.
6. Get another range and bearing.

The key is to always hit send button twice for all measurements.

the torpedo mods are focused mainly on malfunction percentages and hitting power....and not firing solutions.
you may still want to think about using one.:D

good luck!
:Kaleun_Salute:

After reading the feedback, I ran through some attack scenarios using the 'proper' scope method and then my own. Here are my conclusions:

1. The scope method depends on the type of ship you're targeting. This is really problematic when it's very dark or the ship is at an acute AoB.

2. The stadimeter is inaccurate. Strangely enough, this might be an unintentional piece of realism. With the advent of optical range finders, either stadia or coincidence, depends on a know length or height. Every navy had a ship's identification book with the data. Navy's would change or camouflage mast height or ship length to create errors in ranging.

3. I'm not totally convinced that a correct speed is obtainable with taking range measurements within 10 seconds.

So, I think I'm going to stick to my method of doing most of my metrics on the nav map and using Solution Solver. I did sink a destroyer at 2100 yds.! I think the crew had too much Sake the night before. Or it could have been Habu Sake.......:haha:

Thanks for all the input :Kaleun_Salute:

No idea if this applies to manual targeting in stock, but using automatic targeting and experiencing hits aft of the expected impact point, the culprit was my failure to open the doors manually, resulting in a lag.

good observation....because that is exactly the result of not opening your tube doors before giving the order to fire.:Kaleun_Salute:

I'm running FOTRS with manual targeting. My torpedos are set up and doors open long before i'm in a firing position.