TOViper Posted September 13, 2021 Posted September 13, 2021 (edited) The standby altimeter shows totally different altitude (in case of flying in ~11.500m the difference is ~1500m). Both selected for 1013 hPa. Does anyone have official information regarding the tolerances of the standby altimeter in the Viggen? On the other hand the aircraft wasn't always flying at high altitudes ... Edited September 13, 2021 by TOViper Visit https://www.viggen.training ...Viggen... what more can you ask for? my computer: AMD Ryzen 5600G 4.4 GHz | NVIDIA RTX 3080 10GB | 32 GB 3.2 GHz DDR4 DUAL | SSD 980 256 GB SYS + SSD 2TB DCS | TM Warthog Stick + Throttle + TRP | Rift CV1
MYSE1234 Posted September 13, 2021 Posted September 13, 2021 The backup system does not compensate for compressibility, and will therefore show a different altitude compared to the main system. Not sure how accurate the error of 1500m is however, but it should be there. Viggen is love. Viggen is life. 7800X3D | RTX 4070 Ti S | 64GB 6000MHz RAM |
TOViper Posted September 13, 2021 Author Posted September 13, 2021 (edited) If this would be true, the standby altimeter should show less than the main altimeter (higher pressure due to RAM compression leads to higher static pressure > lower altitude indication). No matter of Mach number, the standby altimeter shows the exact same value @M0.3 and @M0.85. Edited September 13, 2021 by TOViper Visit https://www.viggen.training ...Viggen... what more can you ask for? my computer: AMD Ryzen 5600G 4.4 GHz | NVIDIA RTX 3080 10GB | 32 GB 3.2 GHz DDR4 DUAL | SSD 980 256 GB SYS + SSD 2TB DCS | TM Warthog Stick + Throttle + TRP | Rift CV1
MYSE1234 Posted September 13, 2021 Posted September 13, 2021 Just remembered this for earlier this year. So I guess it works differently now, from what it did a few months ago? Viggen is love. Viggen is life. 7800X3D | RTX 4070 Ti S | 64GB 6000MHz RAM |
TOViper Posted September 13, 2021 Author Posted September 13, 2021 13 minutes ago, MYSE1234 said: Just remembered this for earlier this year. So I guess it works differently now, from what it did a few months ago? Hard to say. If I would make a guess, the standby altimeter didn't work correctly back then and still doesn't, and nothing was changed by HB since 4 years. Maybe they had some more information when programming the instrument, but again I doubt that the standby altimeter should show higher values. If the instrument was not compensated for re-compression, then it must show less altitude. So IMHO there is something wrong with it. Visit https://www.viggen.training ...Viggen... what more can you ask for? my computer: AMD Ryzen 5600G 4.4 GHz | NVIDIA RTX 3080 10GB | 32 GB 3.2 GHz DDR4 DUAL | SSD 980 256 GB SYS + SSD 2TB DCS | TM Warthog Stick + Throttle + TRP | Rift CV1
dorianR666 Posted September 16, 2021 Posted September 16, 2021 +1 CPU: AMD Ryzen 5 1600X GPU: AMD RX 580
IronMike Posted September 20, 2021 Posted September 20, 2021 On 9/13/2021 at 9:25 PM, TOViper said: Hard to say. If I would make a guess, the standby altimeter didn't work correctly back then and still doesn't, and nothing was changed by HB since 4 years. Maybe they had some more information when programming the instrument, but again I doubt that the standby altimeter should show higher values. If the instrument was not compensated for re-compression, then it must show less altitude. So IMHO there is something wrong with it. Thank you, we will take a second look. 1 Heatblur Simulations Please feel free to contact me anytime, either via PM here, on the forums, or via email through the contact form on our homepage. http://www.heatblur.com/ https://www.facebook.com/heatblur/
Recommended Posts