reported [MULTICREW] CAQ point and BAM Zone misplacement

[LorenLuke]

While in a multicrew apache, BAM Zones and CAQ points may be inaccurately placed or represented to the crew, and may jump around upon activation or switching of the BAM page.

 

Apache_BAM_Test-CPG.trkApache BAM Test-Pilot.trk

[N8AHbl4]

From what i remember, main issue is that it ignores PAN shift when creating a zone in multicrew. 
PAN -> move far from the ownship symbol -> BAM -> create zone -> created zone jums to the ownship just if it was created with no PAN.

Even if you just select BAM and try to create zone, it will automatically go to freeze and mess up with the zone position if aircraft changed course while creating. 
Makes PFZ/NFZ totally unusable in multicrew.

Edited May 13 by N8AHbl4

[Opesher]

22 hours ago, N8AHbl4 said:

Even if you just select BAM and try to create zone, it will automatically go to freeze and mess up with the zone position if aircraft changed course while creating. 
Makes PFZ/NFZ totally unusable in multicrew.

This is not entirely true. The bug OP mentioned has to do with the TSD desync (or a lack of sync) after using CURSOR PAN or adjusting map heading with arrows in PAN.

There's little known workaround to create PFZ and NFZs as CPG:
1) Don't PAN map with the cursor - it will cause a desync
2) Don't adjust map heading with arrows - it will cause a desync
Instead,
3) PAN on POINT and not with the cursor (enter point you want to PAN to via keyboard).
4) Enter desired heading manually to sync it between stations (you can adjust it with arrows to get desired angle first and then re-enter the same heading with keyboard to sync).

This way you will be able to create accurate PFZ/NFZ zones as CPG.

We'll write a detailed report on this issue soon, for now it's possible to use the method presented above.

P.S. This only persists for BAM and PILOT/CPG cursor show on TSD, points created on TSD using CURSOR PAN are accurate despite the desync.

Edited May 13 by Opesher

[LorenLuke]

1 hour ago, Opesher said:

This is not entirely true. The bug OP mentioned has to do with the TSD desync (or a lack of sync) after using CURSOR PAN or adjusting map heading with arrows in PAN.

There's little known workaround to create PFZ and NFZs as CPG:
1) Don't PAN map with the cursor - it will cause a desync
2) Don't adjust map heading with arrows - it will cause a desync
Instead,
3) PAN on POINT and not with the cursor (enter point you want to PAN to via keyboard).
4) Enter desired heading manually to sync it between stations (you can adjust it with arrows to get desired angle first and then re-enter the same heading with keyboard to sync).

This way you will be able to create accurate PFZ/NFZ zones as CPG.

We'll write a detailed report on this issue soon, for now it's possible to use the method presented above.

P.S. This only persists for BAM and PILOT/CPG cursor show on TSD, points created on TSD using CURSOR PAN are accurate despite the desync.

To clarify, can I drop a waypoint after using the pan mode, and then use the pan-to-point functionality to cancel out the desync of the previous pan-mode usage? 
i.e. pan to the target area, drop a waypoint, pan-to-point onto it, and then drop the CAQ point/BAM zone from there?

[Opesher]

1 hour ago, LorenLuke said:

To clarify, can I drop a waypoint after using the pan mode, and then use the pan-to-point functionality to cancel out the desync of the previous pan-mode usage? 
i.e. pan to the target area, drop a waypoint, pan-to-point onto it, and then drop the CAQ point/BAM zone from there?

CAQ point is fine, it's not affected. Only PFZ and NFZs are.

You can drop any point, unfreeze TSD, then PAN to point you created.

[flanker0ne]

The bug has been internally reported for some time now, and is under investigation.

Thank you