reported overwriting target point with range ring will keep range ring

[FalcoGer]

Only pre planned target points at mission start have range rings attached on the TSD (I believe it should be on any point with an ADU threat ident, no matter where it came from).

However when overwriting a target point because the target file is full, the range ring sticks to that target point number (even if it's a completely different ident or even a target point without range rings at all ("TG" ident in this case))

In the attached track there are 49 SA-8s, which are added as pre planned targets to the DTU Cartridge, creating 49*2 range rings (detection and engagement range, presumably). Adding target 50 does nothing special. But adding yet another overwrites T26 (not sure if that's accurate or if it should be starting with T01?). Despite that target point getting the IDENT "TG" for generic target, it has the SA-8 range ring attached to it that was on the point 26 from the previous point.

Track attached

range_ring_sticks_to_new_target_point.trk

[Scaley]

The overwrite starting at T26 is correct as I understand the documentation. The first 25 points are protected so they can't get accidentally overwritten. 26 onwards are not. Presumably the logic is that important stuff goes in 1-25.

[FalcoGer]

3 hours ago, Scaley said:

The overwrite starting at T26 is correct as I understand the documentation. The first 25 points are protected so they can't get accidentally overwritten. 26 onwards are not. Presumably the logic is that important stuff goes in 1-25.

Ok. Threat ring shouldn't stay though.

[BIGNEWY]

threat rings are not dynamic, they are pre-planned. 

 

I will double check with the team

[BIGNEWY]

The team have a report and are investigating further. 

thanks