SA page wrong HAFU rankings

The SA page HAFU threat rankings are often wrong and inconsistent with the rankings on the Radar page.

The radar will rank contacts correctly, following the rule: Hostile > Unknown > Friendly (whether Friendly HAFUs should get a rank at all is a different story).

The SA page will not respect that logic and will keep the closest contact as rank 1 if it's not a confirmed Friendly, even if Hostiles are present. The Radar will correctly elevate the threat ranking of Hostiles above the ranking of Unknowns. This can be seen in screenshots 1 and 2.

Also, when a contact is designated as L&S, the radar will remove it from the ranking order and step the other ranks up (so if Rank 1 becomes the L&S, Rank 2 becomes Rank 1, Rank 3 becomes Rank 2 etc). Same for the DT2, it's removed from the ranking order. But the SA page does not do that and that creates situations where you have different rankings for the same contact on the two pages. Additionally, the SA page does not mark the DT2 as such. This can be seen in screenshots 3 and 4.

Finally, as I said above, the Radar will assign threat rankings to Friendly contacts, while the SA page will not. I'm not going to discuss which one is correct, but they should definitely agree on how to display Friendlies. They are not separate sensors, the MC handles the rankings and sends the info to both the Radar and the SA page.

I hope the screenshot quality is enough to see the rankings. I had to downscale them to 1080p from 2160p due to upload size limitations. I still have the originals, if needed.

Tested on 2.5.6.52437 Open Beta, PG map.

Track attached.

FA-18C_RAdar and SA page HAFU ranks inconsistency.trk

Tying into this report of SA/Attack format inconsistency -- no DT2 diamond is displayed on the SA.