escaner Posted January 29, 2017 Posted January 29, 2017 Eg. for Beslan it says 1772 m elevation and 9914 m runway length, but both figures are actually in ft. [sIGPIC][/sIGPIC]
imacken Posted April 12, 2017 Posted April 12, 2017 I have the same issue. I reported it on the Spitfire section, but the issue is not restricted to it. All airfields have the wrong values for elevation for me. They show the correct value for feet, but state metres. I have been in conversation with Art-J on this, and he doesn't have the problem. Neither does dannyq8 from another thread on this topic. See attached 2 screen grabs - one is mine showing the problem and the other is from Art-J which shows the correct info. My settings are Imperial. This also happens in 2.0.5, so I will post to that bug section as well. Intel i7 12700K · MSI Gaming X Trio RTX 4090 · ASUS ROG STRIX Z690-A Wi-Fi · MSI 32" MPG321UR QD · Samsung 970 500Gb M.2 NVMe · 2 x Samsung 850 Evo 1Tb · 2Tb HDD · 32Gb Corsair Vengance 3000MHz DDR4 · Windows 11 · Thrustmaster TPR Pedals · Tobii Eye Tracker 5 · Thrustmaster F/A-18 Hornet Grip · Virpil MongoosT-50CM3 Base · Virpil Throttle MT-50 CM3 · Virpil Alpha Prime Grip · Virpil Control Panel 2 · Thrustmaster F-16 MFDs · HTC Vive Pro 2 · Total Controls Multifunction Button Box
=Pedro= Posted April 12, 2017 Posted April 12, 2017 Eg. for Beslan it says 1772 m elevation and 9914 m runway length, but both figures are actually in ft. That's the hell of the RWY :megalol: Gigabyte Z390 Gaming X | i7 9700K@5.0GHz | Asus TUF OC RTX 4090 | 32GB DDR4@3200MHz | HP Reverb G2 | TrackIR 5 | TM Warthog HOTAS | MFG Croswinds
the_soupdragon Posted April 12, 2017 Posted April 12, 2017 LOL yeah a 6 mile long runway. :D SD [sIGPIC][/sIGPIC]
escaner Posted April 12, 2017 Author Posted April 12, 2017 I have the same issue. I reported it on the Spitfire section, but the issue is not restricted to it. All airfields have the wrong values for elevation for me. They show the correct value for feet, but state metres. I have been in conversation with Art-J on this, and he doesn't have the problem. Neither does dannyq8 from another thread on this topic. See attached 2 screen grabs - one is mine showing the problem and the other is from Art-J which shows the correct info. My settings are Imperial. This also happens in 2.0.5, so I will post to that bug section as well. Good catch, the problem only arises with imperial units. The conversions are correctly calculated, but still displays metric units. [sIGPIC][/sIGPIC]
imacken Posted April 13, 2017 Posted April 13, 2017 I have the same issue. I reported it on the Spitfire section, but the issue is not restricted to it. All airfields have the wrong values for elevation for me. They show the correct value for feet, but state metres. I have been in conversation with Art-J on this, and he doesn't have the problem. Neither does dannyq8 from another thread on this topic. See attached 2 screen grabs - one is mine showing the problem and the other is from Art-J which shows the correct info. My settings are Imperial. This also happens in 2.0.5, so I will post to that bug section as well. My post was a little misleading! I shouldn't have mentioned Art's situation. If I set my units to Metric, then I have the same result as him. The issue appears to be quite simple, as escaner says, it is just that the (correct) feet values are shown as metres and not feet on the map. Intel i7 12700K · MSI Gaming X Trio RTX 4090 · ASUS ROG STRIX Z690-A Wi-Fi · MSI 32" MPG321UR QD · Samsung 970 500Gb M.2 NVMe · 2 x Samsung 850 Evo 1Tb · 2Tb HDD · 32Gb Corsair Vengance 3000MHz DDR4 · Windows 11 · Thrustmaster TPR Pedals · Tobii Eye Tracker 5 · Thrustmaster F/A-18 Hornet Grip · Virpil MongoosT-50CM3 Base · Virpil Throttle MT-50 CM3 · Virpil Alpha Prime Grip · Virpil Control Panel 2 · Thrustmaster F-16 MFDs · HTC Vive Pro 2 · Total Controls Multifunction Button Box
Recommended Posts