reported NCTR keeps previous prints forever

[Ahmed]

Hi,

1. Set up a mission with me and a single group hostile

2. within 25nm head on, NCTR prints single group hostile as Su-27, trackfile gets a hostile HAFU, as expected.

3. Lost lock, separated North for a while to ensure that there are no trackfiles left

4. Turned South. As soon as I locked the previous group, it gets unexpectedly ID'd as hostile with print Su-27 while outside of the 25nm "NCTR range"

 

Expected outcome: previous NCTR data is lost given that the trackfile has been dropped. The new trackfile needs to be within NCTR range/aspect to get a new print.

Observed outcome: as per step 4 above, the new trackfile is still IDd

I originally noticed this when reacquiring targets from a side aspect. The procedure above and the track are just a way of consistently reproducing it.

nctr.trk

Edited September 7, 2024 by Ahmed

[Ahmed]

Bumping this issue to see if it can get acknowledged

[Lord Vader]

Hello @Ahmed

We've sent this to internal analysis. 

Thanks for bringing this to us.