f-16c radar - tsd datalink correlated?

[wjmzwx]

The datalink messages are erased as soon as radar captures targets, in another word, datalink symbols dispear and become white or yellow bricks.   I wonder if this is correct.  I know we have 2 phases to make a brick become a green circle or a red triangle : c2 id and nctr.  But, I don't see such behavior on any other US plane models. So, is this an unique character of F-16C? 

Edited December 11, 2023 by wjmzwx

[_SteelFalcon_]

there used to be a bug report linked in here: 

but that has apparently been removed or relocated. it's weird how currently you lose all Link info when your radar picks up a contact that was previously already marked as friend or foe.

[wjmzwx]

33分钟前，_SteelFalcon_说：

there used to be a bug report linked in here: 

but that has apparently been removed or relocated. it's weird how currently you lose all Link info when your radar picks up a contact that was previously already marked as friend or foe.

I am trying to understand the purpose of the design in this way. But it isN't a very efficient way in war zones to be confused about all the targets requaired by radar. After all, we should be able to id friendly units in a distant way(more than 25nm) at least. I know ED team explained that iff had notihing to do with the colors of the datalink symbols. But! I am really confused why in f18 auto iff can make a target with positive mode4 respond green. It appears to me one of the systems has to be wrong. I don't have any experience with real war birds, but I find a lot of vids on Youtube, such as vids about tws muti targets attack, and their correlation functions work just fine. Hopefully,  ED team can explain more than 2steps(c2 id and nctr) and tell us that in the real life the system just works exactly as such a confusing way.  I THANKS ED for make my dream come true, and almost buy every module, I just want a deep learning, don't want to annoy anybody.

Edited December 11, 2023 by wjmzwx

[Moonshine]

 

lots of it in here. Last statement was „working ad intended but still WIP“. 
 

the jet currently doesnt represent whats in the ED manual, but funny enough ED manual represents whats im the real manual.. oh well

[wjmzwx]

16分钟前，Moonshine说：

 

lots of it in here. Last statement was „working ad intended but still WIP“. 
 

the jet currently doesnt represent whats in the ED manual, but funny enough ED manual represents whats im the real manual.. oh well

Thx bro~ I have read that ealier. I notice ED team seems consider it normal in some of the answers. Maybe it's a good idea to put some explanations in the datalink section, such as which correlated symbol shows up in what conditions.  

quote :"  From the Viper Team: As stated, must have two factor to set as correlated hostile. Not only C2. 
Generally, an ROE tree can be customized, but we are not going there. For us, it’s two factor. 

If you want, you can enter a customized ROE tree wishlist item. "

Edited December 11, 2023 by wjmzwx

[Comrade Doge]

in my opinion this is wrong, since you can have a hostile track without 2 factor being needed from your ownship. Real manuals even offer an example of this. You only need 2 factor if you want to change ROE to hostile, from other classifications. But not the opposite, when it's already Hostile on the HSD. Waiting for ED to acknowledge this issue

[Crptalk]

On 12/14/2023 at 10:13 AM, Comrade Doge said:

Waiting for ED to acknowledge this issue

new here?