blunt_waco Posted March 14, 2020 Posted March 14, 2020 The trainer asks that I climb to 325 meters and then maintain altitude but once I get to 300 my altitude jumps to 600 meters. Why is that? Where to check that I’m flying at 325 meters to satisfy the trainer? I looked at the Barometric Altimeter and it wouldn’t go below 500 meters!!!
blunt_waco Posted March 14, 2020 Author Posted March 14, 2020 By the way, the switch is already set to BR.
blunt_waco Posted March 14, 2020 Author Posted March 14, 2020 By the way, the switch is already set to BR. See attached, which panel would show true altitude?
Frederf Posted March 14, 2020 Posted March 14, 2020 None of the gauges show true altitude. The radar altimeter shows radar height above terrain while barometric altimeter shows barometric altitude. The HUD displays radio height with the Cyrillic "rho" letter after it, e.g. 206p for radar height and then switches to barometric reference when radar height isn't available (e.g. too high above surface or radar altimeter is off). If a particular mission asks for you to fly 325 meters it really depends on what this mission is really asking for. Is it 325 meters barometric QNH? Is it 325 meters QFE above the takeoff field? Is it 325 meters true altitude (e.g. the F2 info bar)? Who knows until you talk to the mission designer or take his mission into the editor and check what the scripted trigger is really looking for. A good guess is that he expects you to set QFE altimeter before taking off and reference the barometric altimeter from that. The Ka-50's altimeter can crank super low because it's designed with QFE operations in mind.
blunt_waco Posted March 14, 2020 Author Posted March 14, 2020 None of the gauges show true altitude. The radar altimeter shows radar height above terrain while barometric altimeter shows barometric altitude. The HUD displays radio height with the Cyrillic "rho" letter after it, e.g. 206p for radar height and then switches to barometric reference when radar height isn't available (e.g. too high above surface or radar altimeter is off). If a particular mission asks for you to fly 325 meters it really depends on what this mission is really asking for. Is it 325 meters barometric QNH? Is it 325 meters QFE above the takeoff field? Is it 325 meters true altitude (e.g. the F2 info bar)? Who knows until you talk to the mission designer or take his mission into the editor and check what the scripted trigger is really looking for. A good guess is that he expects you to set QFE altimeter before taking off and reference the barometric altimeter from that. The Ka-50's altimeter can crank super low because it's designed with QFE operations in mind. Hey!! I'm following the instructions from the training mission that was in DCS KA50. Please see attached training instruction.
Ramsay Posted March 14, 2020 Posted March 14, 2020 (edited) Hey!! I'm following the instructions from the training mission that was in DCS KA50. Please see attached training instruction. The Ka-50 behaviour may have changed a little since BigfootMSR created his interactive training mission. In the original 2013 demo/script, the Ka-50 spawned with it's barometric altimeter set to QFE i.e. zero on the runway ... ... now it spawns with the barometric altimeter set to QNH i.e. altitude above sea level. See attached, which panel would show true altitude? You would adjust instrument [5] so it reads 0m before takeoff. I 'guess' BigfootMSR expects players to fly @ 325m QFE, in 1.2.16 the instruction was to fly at your desired height and it was left to the player's discretion i.e. 100-300m AGL The trainer asks that I climb to 325 meters and then maintain altitude but once I get to 300 my altitude jumps to 600 meters. Why is that? Above 300m AGL, the radar altimeter stops displaying on the HUD (i.e. 300p) and the barometric altitude displays i.e. at WP1 300m radar + 335m terrain = 635m MSL Where to check that I’m flying at 325 meters to satisfy the trainer? AFAIK the 325m height is a suggested value (so the player won't collide with the ground) and no mission triggers depend on the 'trainee' following an exact altitude profile. I looked at the Barometric Altimeter and it wouldn’t go below 500 meters!!! Nalchik is at 430m MSL, the briefing page (LAlt+B) shows a QFE setting of 723 mmHg but adjusting the Barometric Altimeter so the thin needle reads 0m is easier. I set the Barometric Altimeter to zero in 2.5.6.44266, so I'm not sure why you couldn't adjust the Nalchik QFE. Edited March 14, 2020 by Ramsay i9 9900K @4.8GHz, 64GB DDR4, RTX4070 12GB, 1+2TB NVMe, 6+4TB HD, 4+1TB SSD, Winwing Orion 2 F-15EX Throttle + F-16EX Stick, TPR Pedals, TIR5, Win 11 Pro x64, Odyssey G93SC 5120X1440
Holton181 Posted March 14, 2020 Posted March 14, 2020 (edited) As Frederf said, you should set the barometric altimeter to QFE, i.e. 0m while on ground before lift-off. Then the barometric altimeter and radar height will follow each other rather closely during your climb to 325m (as long as the ground is rather flat below you during that part of your flight). When you get above 300m radar height the HUD will stop showing radar height and instead show barometric altitude above your starting position (where you turned in QFE). The jump in reading on the HUD won't be that big. The jump to 600m in your start post indicates that you didn't set the barometric altimeter correctly to QFE. Edit: Snipped by Ramsay Edited March 14, 2020 by Holton181 Helicopters and Viggen DCS 1.5.7 and OpenBeta Win7 Pro 64bit i7-3820 3.60GHz P9X79 Pro 32GB GTX 670 2GB VG278H + a Dell PFT Lynx TrackIR 5
blunt_waco Posted March 15, 2020 Author Posted March 15, 2020 You guys truly never disappoint. Many thanks for the details. It seems that I forgot to turn Barometric Altimeter to 0!!
Recommended Posts