jbiebes

Trying the DTC function for the first time in the Hornet (so I have nothing to compare to prior to today's update). I created a new DTS/CMDS profile and exported it. I only modified Prog 5 from the Hornet's defaults. When loaded in the jet, the program numbers are wrong / shifted by 1: Prog 1 is blank (all zeros). Prog's 2-6 all contain the DTC programming from the program 1 increment less (i.e. Prog 2 contains what I programmed for Prog 1; Prog 6 contains my modified Program 5. Since there is no Program 7, the DTC data for Prog 6 doesn't exist anywhere. Am I doing something wrong, or is this a bug? FA-18C DTC Bug.trk

Worth noting that you’re testing at an airfield close to sea level, so you’re getting a minor deviation of the TPOD (which is looking slightly below ground level), but try this on the Syria map at 3000 ft, you won’t even see the target at all since the magnitude of the error is much greater.

In the latest update (2.9.9.2280), F/A-18 Markpoint function is erroneously saving target elevation in METERS instead of FEET (but is still labeling it as FEET). When the markpoint is recalled, it is no longer pointing at the actual target. Occurs with both ATFLIR and Litening pod (and likely any markpoint generated from any source). e.g. Min-Vody runway actual elevation = 1050 ft. After targeting and hitting MK1, the markpoint elevation is 320 FEET. FA-18 Markpoint Elevation Bug.trk