reported Offset Aimpoint (OA) is displayed on the wrong position (HUD)

[Vigo68]

OA is displayed in the wrong position on HUD,  depending on the active wpt altitude when entering OA data instead of the altitude of the target WPT. popcaus.miz wpt1 alt 43ft,  wpt2(tgt) alt 43ft.   popcaus1.miz wpt1 alt 5000ft, wpt2(tgt) alt 43ft. WPT coordinates in both missions are the same.  Load mission, pause it and enter the data from picture. Select CCRPVRP AG mode, target wpt 2. You will see a different (wrong) position OA on HUD in popcaus1 mission.  If you choose wpt2 (tgt) as active wpt before entering data, OA is displayed in the right position in both missions.

PoPCaus1.miz PoPCaus.miz

Edited October 25, 2023 by Vigo68

[karpiyon]

I also duplicated this error.

I believe the problem is that when you enter popup data for a specific wp, say wp10, adn your current wp elevation is different, OA data shown on the HUD will be wrong.

The only sure way to enter correct OA data is if you first select the current wp (STPT page) and only then enter the OA data to the same wp using DEST page.

 

Edited October 25, 2023 by karpiyon

[Lord Vader]

Hi @Vigo68

We thank you for your description as well as the miz files. However, next time try to create a short track with your description to help us, not only observe the bug, but also see what you are doing as well, just in case something goes overlooked. 

I was still able to reproduced this and I have reported it internally. 

 

[xanstin]

On 10/25/2023 at 3:38 PM, Vigo68 said:

Which planner program is this that will automatically input to DED?

 

[karpiyon]

On 10/29/2023 at 1:59 AM, xanstin said:

 

It's a special plugin I created for VoiceAttack.
You can download it here and also see the Forum page

[Shrike88]

Nice find on the bug.