ShuRugal Posted August 21, 2024 Posted August 21, 2024 I have noticed for a while now that the AH64 variometer indicates incorrectly when in forward flight. I have seen an indicated climb rate as high as 500'/min when in level flight. The first couple times i saw it, i thought maybe i had done something wrong with INU alignment, but i am seeing this in every flight, hot or cold start. I will put together a short track file for this later this evening, but i wanted to make the thread before i forgot again.
Specter Posted August 22, 2024 Posted August 22, 2024 I also noticed this tonight. i7-10700K @ 5Ghz | Asus Z490 Tuf Pro Gaming | RTX 3090 | 64 Gb RAM @3.6Ghz | 1TB Samsung 970 EVO+ SSD | 1TB addlink S70 M.2 SSD | 1TB Samsung 850 EVO | 4TB HDD | Reverb G2 | Thrustmaster Warthog HOTAS | Thrustmaster TPR rudder pedals | Thrustmaster Cougar MFDs
ED Team Lord Vader Posted August 23, 2024 ED Team Posted August 23, 2024 Hey @ShuRugal We would really appreciate that track file when you can make it. Thanks. Esquadra 701 - DCS Portugal - Discord
Specter Posted August 27, 2024 Posted August 27, 2024 I noticed the following day this display issue was no longer apparent. I have changed nothing. Very strange! i7-10700K @ 5Ghz | Asus Z490 Tuf Pro Gaming | RTX 3090 | 64 Gb RAM @3.6Ghz | 1TB Samsung 970 EVO+ SSD | 1TB addlink S70 M.2 SSD | 1TB Samsung 850 EVO | 4TB HDD | Reverb G2 | Thrustmaster Warthog HOTAS | Thrustmaster TPR rudder pedals | Thrustmaster Cougar MFDs
Solution Ignition Posted August 29, 2024 Solution Posted August 29, 2024 I had variometer issues when the aircraft couldn't align properly with GPS, for example when being in the red team and didn't have the SATNAV option enabled in the mission editor. But that is expected as far as I know.
ShuRugal Posted September 26, 2024 Author Posted September 26, 2024 On 8/29/2024 at 12:36 PM, Ignition said: I had variometer issues when the aircraft couldn't align properly with GPS, for example when being in the red team and didn't have the SATNAV option enabled in the mission editor. But that is expected as far as I know. This ended up being the problem. Once i made sure satnav was enabled in the mission editor, the problem was resolved. Apologies for not getting back to this for so long. This can be marked as "user error".
Recommended Posts