diegoepoimaria01 Posted February 14, 2018 Posted February 14, 2018 The "clock" altimeter on the SU-27 can't be lowered enough to reach zero when on the ground. It seems that the lower pressure ( QNH? ) that the altimeter can accept isn't low enough ( the lower end is something near 70, while the ground is at 65 , if i remeber correctly ). Is it a bug or am I misisng something ( like a limitation )? In the SU-25 the altimeter can be set that low, but I don't know on other planes.
DaveRindner Posted February 16, 2018 Posted February 16, 2018 Western NATO aircraft use QNH. Russians use QFE. So I was told.
diegoepoimaria01 Posted February 18, 2018 Author Posted February 18, 2018 Hmmmm, ok. I'll have to learn about QNH and QFE then. But my problem is that, while on the ground, I can't lower the altimeter enough for it to reach the zero. so, while standing on the runway, my altimeter still indicates about 200 meters. Radar altimeters and HUD altimeters works fine though. Is it a minor bug or the Flanker has a limitation in altimeter setting?
Art-J Posted February 18, 2018 Posted February 18, 2018 It's a airplane design limitation which originates from what Dave wrote above. Works both ways, for example folks flying F-5 have similar problems with adjustment of its altimeter on Caucasus map. Unfortunately, the DCS ATC in its current, simplified (and pretty much useless) form is unable to give QFE or QNH pressures depending on what map and airplane you use. i7 9700K @ stock speed, single GTX1070, 32 gigs of RAM, TH Warthog, MFG Crosswind, Win10.
diegoepoimaria01 Posted February 20, 2018 Author Posted February 20, 2018 It's a airplane design limitation which originates from what Dave wrote above. Works both ways, for example folks flying F-5 have similar problems with adjustment of its altimeter on Caucasus map. Unfortunately, the DCS ATC in its current, simplified (and pretty much useless) form is unable to give QFE or QNH pressures depending on what map and airplane you use. Sorry, i tought I've repied to you, but something didn't work correctly. I'm not sure I had correctly understood the answer. You said that , sice the ATC gives you the airfield elevation in a different format, then your altimeter can't be adjusted correctly. But then a simple conversion chart should be enough, no? I mean, the ATc says : 1234 4 scenarios: 1) I'm in Caucasus with a russian airplane => ok, it's QFE 2) I'm in Caucasus with an allied airplane => conversion form QFE to QNH 3) I'm in Nevada with an allied airplane => ok, it's QNH 4) I'm in Nevada with a russian airplane => conversion form QNH to QFE For me, the issue is that on the ground in Nevada the SU-27 altimenter can't be lowered enough to reach zero, while Su-25 altimenter can. So, even if i know the QFE/QNH, I can't use it. I can't even set my altimeter on the ground to zero without looking at the QFE/QNH.
discwalker Posted March 5, 2018 Posted March 5, 2018 (Su-33 use hectoPascal not mmHg as other russian planes.) GTX 1070 8GB, 16GB DDR3, W8.1 on SSD, DCS on another SSD
Nealius Posted March 6, 2018 Posted March 6, 2018 I believe it may be related to the issue of pressure changes at altitude in DCS. If I create a mission flying from Nellis with QNH 30.15, the actual QNH when I get in the cockpit is 30.28. It appears the QNH/QFE reported in the Mission Editor/Briefing is the QNH/QFE at sea level, and not QNH/QFE at the actual airbase that you are spawned at. Unless you set Mission Editor QNH to an unrealistic setting, it's probably impossible to zero out the altimeter in Nevada.
Recommended Posts