need track replay Ground Radar Designtion Cross snaps back to Waypoint.

[rurounijones]

This behaviour was observed in our MP session today on both the F-16 and the F-18. The replication instructions below are for the F-18.

Start with an F-18 with a TGP (I was using the Lightning).

1. Create a waypoint, hereafter referenced as WP1.
2. Take-off. Turn on Radar and TGP and wait for warm-up.
3. Enter A/G mode. Have the TGP on one MFD and the Radar on another.
4. Waypoint Designate WP1

The status as this point is that WP1 is designated and both the TGP and Ground Radar are slaved to it.

5. Select the Radar and move the Designation Cross to a new point 500 meters west of WP1. I am calling this poing AP1 (Aim Point 1).

At this point the TGP will now be pointing at AP1. However the radar's Designation Cross does not move and is still pointing at WP1. These two sensors are now desynced by 500 meters.

5. Select the Radar and move the Designation Cross (Which is still on WP1) to a new point 500 meters west of WP1. I am calling this poing AP2 (Aim Point 2). AP1 and AP2 should be the same offset from WP1, given the wierd current logic, and the TGP and Radar should both be looking at this location if they were synced.

However in reality At this point is:
* The Radar Designation Cross has snapped back on WP1.
* The TGP is now looking at a point 500 meters west of AP1/2 because when we slew the radar based on an offset of WP1 the TGP will slew the same amount but from AP1 instead of WP1.

If we drop a bomb at this point it will hit WP1.

So there are two bugs here.

A. The Ground Radar Designation Cross snaps back to the Waypoint and targetting systems will use this as the drop point for things like bombs in CCRP.
B. The TGP does not stay slaved to the Desicnation Cross.

Things not tested:
* What happens if you switch to the TGP, does the Radar Designation Cross start following the TGP? Properly or using the wrong base offset?

Edited January 14, 2023 by rurounijones