Stadimeter range is off (Bug?)

[AVGWarhawk]

Originally Posted by Egan

I'm using 1600 by 1200 (4:3) and I hadn't tried using the sonar man to ping distance before so I went to test it. I set up an attack on a stationary 'Old Composite Merchant' and closed in from a long way out. I was getting quite a big discrepancey between the sonar ranging and stadimeter when i measured from the top of the mast. Closer in, I lowered the stad a bit more, checked my distance with the sonar and the two finally started getting close to one another.

So for me, yes, there does appear to be something wrong here. I think Krupp is probably on the right track with mod but i remember someone saying that using the Observation scope gave far more accurate results than either the attack scope or the TBT.

Just to throw a wrench in , at very long distances, what your simulated Stadi and your eye can see will be very much different than a definite sonar ping and time the sound travelled back. As you get closer, the stadi gets more clearer just as the ship get more clear and the mast can be seen quite readly. At this point the stadi should be accurate and close to what the sonarman is telling you. How can any accuracy by eye and a shaking scope/TBT be gotten from 5000 yards off?

Just my thought.

[Egan]

I'm pretty sure I shouldn't be 1500 yards off..

But as I said, even close up there was a very obvious discrepency between sonar and stadimeter. Only when using the stadimeter well down the mast on the particular merchant did the two ranges finally match. At 5000 yards or greater you are right - there shold be a degree of error. At less than half that, though, the error should be much less.

Anyway, I've only started testing this. I'll set another one up with the same type of ship at various ranges that are known to me and see what transpires.