Quote:
|
Originally Posted by tomoose
RR;
if bearing is the first identifyable data (i.e. you're looking through the periscope to see the target in the first place ergo the bearing is obviously displayed by your scope) why would that be the last piece of info to input? If I understand your point correctly it's because of the PK 'memory' issue but isn't that only a problem if you don't 'reset' the PK?
If the PK isn't 'reset' then yes, the last firing solution is still valid and your torps go off in a relatively bizarre direction (guess how I found that out?LOL  ).
I thought I had this firing stuff figured out (I still miss as much as I hit, LOL) but now I'm confused again (not hard to do at the best of times).  |
Already explained that in the above post. It's because entering in the wrong order doesn't work.
Let's do the same though experiment as before. It's the first time you've used the TDC/PK or you've "reset" it (actually there is no such thing. You can just leave it on all the time if you're going to use it). So the TDC says that the target course is 0º and the speed is zero. Take the bearing/range first. The PK is on. The TDC paints the impact point on top of the target, but because the impact point is moving at zero speed and zero bearing, it sits there and the target takes off and leaves it sitting there while you collect the other information. By the time you develop and input the information you have an impact point moving the same direction and speed as the target but it's a long way off.
So whether the PK is "cleared" or not is irrelevent. There is no way you can input the info in the wrong order and have a good solution. You might still hit if you're close enough and/or the target is moving slowly enough. If you can develop and input the parameters inside of 30 seconds you might have decent luck. If you find yourself missing astern though, I can just about guarantee you that entering in the wrong order is the culprit.
Yes, I know I'm the only one who has ever mentioned this vital detail. Sorry! I am working on a new video that will explain this in full and illustrate the right and wrong way to enter parameters into the TDC using the PK. Once you see it in action you'll wonder why it wasn't perfectly clear before I opened my big mouth.:p