working as intended Radar lock symbology

[Bjarned]

I locked a friendly and he showed as yellow square. Is this a bug?

[Moonshine]

Been discussed and raised here:

sadly the post everyone is referring to in that thread is „no longer available“… 

[Q3ark]

I always assumed that the two factors thing had to come from different donors.

[Moonshine]

even if thats true, it would explain why it wont work if you are alone and have no AWACS.

but doesnt explain why its not working when an AWACS is present. he is a different donor. and if the AWACS already classifies something as hostile (which would mean that multiple factors identifying something as hostile is already true), i dont think your own aircraft should overwrite that information. yet currently we lose all classification as soon as our radar paints something. even worse, on top of that, the classification also disappears on the HSD. which it shouldnt

[Comrade Doge]

The key here is that there are 2 different topics, one is the track correlation (what this topic is about), and the other is ROE Tree. ED thinks we are talking about ROE Tree, but in reality the problem is with the correlation only (which is irrespective of the 2 factor argument).

Maybe one day this will be revisited.

[BIGNEWY]

Hi all,

for now this is working as intended, but we may revisit the target classification in the future. 

thank you 

[Nedum]

Do I understand that correctly? The FCR will never display anything other than a neutral target in terms of color?
For my own understanding: The HSD shows me a target (hostile (red) or friendly (green)) with the help of the AWACS. But the FCR will only ever show me a neutral target, regardless of this and also completely independently of two-factor authentication (IFF+AWACS)?
Can someone explain to me logically why the FCR has been given a color mode at all if it is completely useless for identifying targets?

 

Edited February 22, 2024 by Nedum

[BIGNEWY]

The F-16's IFF is not linked to the FCR or datalink symbols in any way, in that doing an interrogation and receiving a friendly IFF response (as shown in the OP's image) will not contribute to how the FCR or HSD classifies the contact.
The F-16 requires two factors to classify a target as hostile, which would mean a hostile NCTR print along with a target ID transmitted across the datalink. If only one factor comes back as hostile, it will be shown as a yellow unknown square. Alternatively, it only needs one factor for friendly ID.

[Comrade Doge]

2 hours ago, Nedum said:

Do I understand that correctly? The FCR will never display anything other than a neutral target in terms of color?
For my own understanding: The HSD shows me a target (hostile (red) or friendly (green)) with the help of the AWACS. But the FCR will only ever show me a neutral target, regardless of this and also completely independently of two-factor authentication (IFF+AWACS)?
Can someone explain to me logically why the FCR has been given a color mode at all if it is completely useless for identifying targets?

 

 

There is no logic really, the system is not complete, hopefully it will be solved.

 

1 hour ago, BIGNEWY said:

The F-16's IFF is not linked to the FCR or datalink symbols in any way, in that doing an interrogation and receiving a friendly IFF response (as shown in the OP's image) will not contribute to how the FCR or HSD classifies the contact.
The F-16 requires two factors to classify a target as hostile, which would mean a hostile NCTR print along with a target ID transmitted across the datalink. If only one factor comes back as hostile, it will be shown as a yellow unknown square. Alternatively, it only needs one factor for friendly ID.

This is the issue, we are not talking about IFF here, there is no issue about the ROE System (changing classification), the issue is with track correlation (filling the hollow Link16 symbols).

It is possible to have a correlated Hostile track without NCTR print, because that track has already been established as Hostile (ROE has already been applied by whomever has donated that symbol over Link 16), now all that's left is to do correlation when FCR sees it (fill up the symbol).

I will gladly provide more details in DMs if desired.

[BIGNEWY]

10 minutes ago, Comrade Doge said:

There is no logic really, the system is not complete, hopefully it will be solved.

 

This is the issue, we are not talking about IFF here, there is no issue about the ROE System (changing classification), the issue is with track correlation (filling the hollow Link16 symbols).

It is possible to have a correlated Hostile track without NCTR print, because that track has already been established as Hostile (ROE has already been applied by whomever has donated that symbol over Link 16), now all that's left is to do correlation when FCR sees it (fill up the symbol).

I will gladly provide more details in DMs if desired.

We understand the issue, for now it is working as intended. In the future we may revisit the target classification tree. 

thank you 

[Comrade Doge]

26 minutes ago, BIGNEWY said:

We understand the issue, for now it is working as intended. In the future we may revisit the target classification tree. 

thank you 

You may revisit the classification tree as well, but that's not what this topic is about

[BIGNEWY]

the topic is known, for now it is working how we intended it to. In the future we will revisit this. 

thank you