[SlipBall]

Originally Posted by NaBkin

Hi folks,

I´ve been doing some tests for navigation. Basically I wanted to figure out the time I have to fly for a certain distance.

So I did this test in QMB (no wind, 100 meters hight):

Time: 3 minutes (0.05h)
Speed: 250 Km/h IAS (with this low alt and speed TAS/IAS shouldn´t make a big difference I guess)

So after the math is done (250km/h x 0.05h) the flown distance should be exactely 12.5 Km

I did the test several times with several planes and everytime the actual flown distance is 14,5 Km (that indicates a speed of somewhere around 285 Km/h).

Does anyone know where I did the mistake or is just some of the tools in the game broken (Speed gauge or distance meassure on the map)?

Thanks for help!

Originally Posted by MusseMus

Which aircraft did you use?
The reason I ask is because in a test made in another thread (http://forum.1cpublishing.eu/showthread.php?t=34115) the results shows that the Spitfire in COD is roughly 14% slower than real life.

Since your figures show a 14% speed gauge error, it's tempting to suspect it's accually the speed gauge in the spit thats porked, not necessarily the FM

But it might just be a coincidence

/m

Originally Posted by NaBkin

You're right. This isn't a IAS/TAS issue (if TAS or IAS — neither give the expected values in the calculation and it's only a few % difference in this low altitude on a regular day anyway).

Also it's not an FM issue because even with a completely wrong FM (say if you do the calculation with the "FM" of a juggernaut, you should get the expected values).

So I'm getting the feeling that the speed gauges in CloD are a mess. It seems that they show an incorrect (too slow) speed.
15% too slow for the Spit and 5% too slow for the 109.

If you think further and considering the numbers MusseMus brought up a few posts earlier, the FM of the Spitfire actualy could be 15% faster than the gauge indicates and the Me109 would be arround 5% faster.
Maybe it's "just" an issue of incorrect display of gauges rather than incorrect FM Should be very easy to fix I suppose...

Yes I found gauge is in error too, just wondering if one of you started a bug tracker that I could cast my vote.