Jump to content

Recommended Posts

Posted

According to the map, the waypoint should be straight ahead but the waypoint indicator on the HUD shows the waypoint to the north. And tbe waypoint indicator should get affected by wind.

Posted

Maybe I'm reading it wrong, but it looks more like the TAD is the one out of whack — HUD and CDU agree, and wind is low enough that it shouldn't be a factor.

❧ ❧ Inside you are two wolves. One cannot land; the other shoots friendlies. You are a Goon. ❧ ❧

Posted (edited)
Maybe I'm reading it wrong, but it looks more like the TAD is the one out of whack — HUD and CDU agree, and wind is low enough that it shouldn't be a factor.

The TAD, HUD heading tape and HUD view all match.

 

The A-10C is flying west (265°M) between Gori and Khashuri.

 

The town to the left in the OP's picture is Khashuri and the TAD shows waypoint 6 ahead, however both the HUD and CDU show it's direction is directly north.

 

Flying around a bit I'm able to reproduce this (in a clean mission) by climbing/descending +/- ~7° pitch and/or flying level towards a similar placed waypoint.

 

DMH and BRG change on the CDU STRINFO page from the correct heading (say 264°M) to 354°M (0°T minus MagVar?).

 

Continuing towards the waypoint in level flight (with small pitch adjustments) - DMH, BRG and the HUD marker eventually return to their correct values/positions.

 

 

Track attached, bug occurs at

and is
by rolling away from WP and then back when the CDU DMH corrects it's self.

 

Tested DCS 2.5.5.35461

A-10C Waypoint HUD marker and DMH bug, 2_5_5_35461.trk

A-10C Waypoint HUD marker and DMH bug, dcs_log.txt

Edited by Ramsay
Add track file and video

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

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...