![]() |
Quote:
Cheers Kaleun :up: |
i guess i coud do some sort of basic drawing, taking as a situation, your screenshot:
http://img252.imageshack.us/my.php?image=nomo1kh5.jpg he moved 0.4 km in 3 minutes, right? so: keep in mind that this edited screen was made in seconds, with a broad line for easy recognition. I paid atention to the way the line should cross the nomograph, but i didnt pay too much atention of to the actual values. http://img266.imageshack.us/img266/7...o1kh5ssna1.jpg |
so, based on the line you have drawn, the target ship would be doing.....5 knots?? :yep:
|
in that given case, yes, but i didnt use the exact measures, i just wanted to show how it works i wasnt trying to be 100% acurate with the values.
i guess what i'm trying to say is... when you do it, be carefull :yep: |
DDiplock: You must have had an angel inside of your torpedo's gyro mechanism each time because I can't imagine how you managed to succeed doing it your way. I take my hat off for you.
[edit]Yes I can, as Abd_von_Mumit said, since you happend to use the three minute interval the line length happend to match the target speed (roughly, as 0.4km in 3 minutes is 4.3 knots). But any other interval would have you come up with the wrong speed. Whether you actually miss the target depends on alot of other factors too. As another example of the use of the nomograph take a look at the following link (Paul Wasserman's Manual plotting tutorial; Tip: if you haven't yet allready, read the whole page) The nomograph looks different (horizontal) but works the same way: http://www.paulwasserman.net/SHIII/#... Traveled (NG) |
I guess i'm going to try and stick to firing torps as close as I can, I just did a test fire at two ships in a convoy in my campaign, one of them being at about 1700mtrs away, according to the ruler I used to measure the distance anyway. Torpedos missed on both targets. Naturally I'm going to reload to before firing the torps and "discount" what happend :)
But i'm not 100% convinced on the "multi target" firing explained in the manual. Do you need to relock your periscope onto the 2nd target for the AOB to be auto updated?? Or does it do it automatically when you swing the periscope round? Because after i've input all my data into the TDC manually, I switch it back to "auto" so that it essentially "tracks" the target and updates the solution accordingly. In convoy training mission, I have yet to successfully hit a 2nd target. I always hit the first, but never the 2nd :damn: :damn: |
When TDC is set to auto, then when turning the scope, only the bearing (obviously) and AOB is updated(to maintain same target course). Range is not. Speed should be the same if it is a convoy/taskforce. Unless they spotted the torpedo wake or something, then they might speed-up. Also if you turn your sub you need to match the AOB to new relative bearing again. Don't know if you did turn. More likely is you missed because of a crude speed setting (3m15 rule is too short to measure fractions of a knot) or wrong AOB. These two are the most important factors in aiming torpedo's. Range is secondary. But targets become smaller the further they are so precise speed and AOB become more important for longer shots.
[Edit]Usually in the heat of battle it is easy to forget to open the torpedo doors. That maybe it? |
Quote:
|
Then I can only suggest to plot positions over longer periods of time and see how that improves.
|
Quote:
|
you could use the 3:15 mesurement and back it up with a... lets say, 10 minute nomograph mesurement
|
I do make plots at multiples of 3:15, but only to find out his general course and speed early. When I know roughly which way he's going I turn parallel or maintain distance and speed up to advance on him. As the plots come in I update the speed setting in the TDC and correct my course based on his course ( if it is taking lon I start a new string of plots after 32:24 (propperly 10x 3:15 interval ) and calculate speed from that. But i'm a weird one when it comes to precision. An average over a couple of 3:15 intervals should make good enough improvements.
|
All times are GMT -5. The time now is 11:39 PM. |
Powered by vBulletin® Version 3.8.11
Copyright ©2000 - 2025, Jelsoft Enterprises Ltd.
Copyright © 1995- 2025 Subsim®
"Subsim" is a registered trademark, all rights reserved.