![]() |
SUBSIM: The Web's #1 resource for all submarine & naval simulations since 1997 |
|
![]() |
#1 |
Engineer
![]() Join Date: Apr 2005
Posts: 210
Downloads: 141
Uploads: 0
|
![]()
and on the opposite side? Do you take the highest end of a mast or do you take the highest line of the flag of an enemy ship?
greez McM |
![]() |
![]() |
![]() |
#2 |
Watch Officer
![]() Join Date: Dec 2014
Location: Kansas City, Missouri
Posts: 343
Downloads: 24
Uploads: 0
|
![]()
I think that can be variable; OTC, for instance, uses different reference points on the ship for different vessels
__________________
"The sea shall ride over her and she shall live in it like a duck" ~John Ericsson |
![]() |
![]() |
![]() |
#3 | |||
Admiral
![]() |
![]()
With Optical Targeting Correction you follow the Recognition Manual's cues as to where to place the Stadimeter's water line image. Each ship can be different. OTC uses the most visible point, then has the reference point marked in red to indicate the spot. The reference point could be a mast top, funnel, super structure, flag mast, carrier flight deck.
Quote:
All OTC height reference points are fairly accurate. On the contrary, the stock game and other mods have various measurements. Many are off by 30% of what they should be, some by 50% inaccurate. Getting back to jlry's original question.....No the U.S. Stadimeter does not need to have the waterline lined up with the horizontal line of the periscope to take a reading. =============== I realize this thread is nearly a year old, the first linked thread (Hitman's Tutorial for 100% Realism Manual Targeting, of 2007) quickly points out the problems the game has with measurements (least that's what Charos points out in the #8 reply): Quote:
These may be older threads, but the problems with manual targeting are still evident today without OTC.
__________________
The HMS Shannon vs. USS Chesapeake outside Boston Harbor June 1, 1813 USS Chesapeake Captain James Lawrence lay mortally wounded... Quote:
|
|||
![]() |
![]() |
![]() |
#4 |
The Old Man
![]() Join Date: Dec 2005
Location: Philadelphia Shipyard Brig
Posts: 1,386
Downloads: 160
Uploads: 19
|
![]()
"yet if you look closely at it, some flag masts aren't visible at all......the flag is just waving in the breeze"
Biggest problem with using mast height at long ranges on a computer, a distant mast can be one pixel wide or zero pixels (invisible), never half a pixel or 3/4 pixel since computers don't do that. What would be a faint thin line in real life is not there on a computer simulation because of the display limitations. I got interested in OTC after reading this old thread, so I downloaded it and am reading the docs now. My biggest objection to manual targeting has always been "too complicated" since in real life I would have an entire attack team keeping the plot, cranking inputs to the TDC, fiddling with slide rules and the IS/WAS, and of course setting the torpedo depth and opening the outer doors so I wouldn't have to do all that myself. Reading the PDF on the omnimeter hasn't changed that opinion - it goes through calculating the range to the exact yard, then moving stuff on the slide rule to calculate AOB based on actual target length versus the visual apparent length. Assuming I've identified the target correctly, of course, which is difficult to impossible at long ranges. The PDF doesn't mention the time factor, "The computer found range in the Position Keeper is 1468 yards to target. That’s reasonably accurate!" AT THIS MOMENT it's accurate, whoops, the sub is moving and the target is moving, the range is constantly changing, by the time I make the adjustments on the omnimeter and enter the data into the TDC, that 1468 yards range is ancient history. How do you compensate for the time factor? Or do you just accept that the data is no longer accurate but "close enough for government work"? |
![]() |
![]() |
![]() |
#5 |
Weps
![]() Join Date: Dec 2012
Posts: 357
Downloads: 137
Uploads: 0
|
![]()
I guess by trial, error and experience.
It's the same when you plot the target's true course and speed on the Nav.map with radar. By the time you move to the A-scope from the PPI screen, read the distance and look up to the bearing dial, go back to the Nav. Map and select the appropriate tool (triangle thingey ![]() Put it where the sub is 'now' and draw the line at xxx degree bearing will put you +-150yrds off... Not a big deal IF you do it the same way each time, mess up once and you'll be off by a couple of degrees and that will mess up your plot. |
![]() |
![]() |
![]() |
Thread Tools | |
Display Modes | |
|
|