reported O/S Waypoint elevation value incorrect on data page

[Phantom711]

Just found an error with O/S waypoints.

In the track I have waypoint 1 set at Tonopah. I set my elevation to "feet" on the UFC. I create an O/S waypoint just 10m south of wypt1 at the same elevation.

I select my ATFLIR. I select wypt 1 and then O/S as TGT designate. I switch from the HSI to the Data page.

Both Data page and pod show the correct elevation for the O/S waypoint.

But as soon as I start to manipulate the O/S waypoint with the pod, the elevation value for the O/S waypoint on the data page shows a completely different value which in fact equals the correct value in meters, even though it still says "FT". The value shown in the pod is still correctly showing feet.

O-S wypt elev error.trk

[Harker]

Thanks, I also reported it now, alongside other issues with Offsets. What I can see is that after the FLIR (and only the FLIR) becomes the designating sensor, it will actually slew the Offset coordinates, alongside the weird FEET -> METERS switch that you mention here.

Generally, I would only used Offsets as fixed points and avoid slewing the designation with any sensor, for now.

Edited May 30, 2024 by Harker

[Phantom711]

But by slewing it and thereby changing the offset and it´s coordinates one can nicely determine the distance to friendlies as a FAC(A). So in fact I like that aspect of it, but I don´t know if this is rather a bug or a feature.

 

 

Edited May 31, 2024 by Phantom711