View Single Post
Old 12-13-07, 08:08 AM   #43
Fincuan
Admiral
 
Join Date: Aug 2007
Location: Suomi, sauna, puukko, perkele
Posts: 2,346
Downloads: 39
Uploads: 0
Default

Quote:
Originally Posted by Rockin Robbins
If for some reason one of the ranges is wrong, or if both ranges are wrong the estimate speed button will be wrong. Because of that I always estimate speed from my plot and forget all about that.
That's very much true, and is also the primary reason why I never use the function in campaign. One small mistake and bam, your solution is screwed. The Dick O'Kane method is a nice tool to have in the toolbox, but for me it's not the primary one. Now that my current career is well into 1944, I mostly find myself in night surface attacks against enemy convoys, something where the O'Kane method just doesn't suit well. If you are to engage three merchants travelling in a line 800 meters apart from each other while keeping your bow pointed at the closest escort, you pretty much have to use the TDC. Developing the solution over time and gathering the basic data with the radar, while using the stadimeter only as a confirmation, guarantees that by the time the target is within torpedo range, the solution is nearly flawless.

If it's not a multiple target situation, or it's just two targets very close to each other, then the Dick O'Kane method is indeed much easier and more straightforward. A few other situations where I find myself using it are sonar-only attacks against escorted targets, when you can't ping to get the range, and radar-guided surface attacks in extremely bad visibility(<500 meters). Especially in the latter situation the TDC is almost useless, because you can plot everything on the map but there's no easy and precise way to feed the data into the TDC. With the O'Kane method you don't obviously have to input anything but the speed.
Fincuan is offline   Reply With Quote