reported FCR Symbology Yellow instead of Red

[Moonshine]

So i did test the FCR Symbology "fix" as mentioned in todays patch.

Mission Scenario:

Friendly AWACS present

2 Groups of Bandits

 

Now upon locking a clearly as hostile identified aircraft the symbology changes to yellow instead of filled out red with the "Bug" Circle around it.

shouldnt it appear as Hostile with the bug circle around it? 
 

also it does look like the yellow symbology is overlayed over the red one, you can see that as i change the DTT priority target.

 

Track attached

FCR_Symbology..trk

[NineLine]

This is correct as is. The target is ambiguous due to different reporting. 

[Moonshine]

7 minutes ago, NineLine said:

This is correct as is. The target is ambiguous due to different reporting. 

thanks for the quick reply! 

is it normal that the ambiguous symbology is overlayed over the red one as shown towards the end of my track? focus on the altitude numbers for example

[NineLine]

Yes, SURV track from AWACS and ownship ROE-colored track. The SURV is reporting hostile, but the ownship cannot make such a determination. Note that the AIFF is not tied to the ROE tree in the Viper.

[Comrade Doge]

5 hours ago, NineLine said:

Yes, SURV track from AWACS and ownship ROE-colored track. The SURV is reporting hostile, but the ownship cannot make such a determination. Note that the AIFF is not tied to the ROE tree in the Viper.

They should be correlated, as the HSD reports hostile, but the FCR reports ambigous on the same track. Only one track can be displayed, they can't overlay each other...

[llOPPOTATOll]

So to begin with, the symbology is not displayed correctly. For some reason it is shown as a white box with a yellow circle and altitude shown in yellow. Instead it should be a yellow filled box with a white circle to denote its the bugged target and the altitude in yellow. You say yourself that AIFF isnt tied to the ID Tree in the viper, so why is it changing a HOSTILE track into a Suspect track just by bugging it, that doesn't make any sense. An example of something that should show yellow is a track that has met partial hostile ID tree criteria.

[NineLine]

I am relaying this from the Viper team, if you have evidence that shows otherwise I will be happy to take that back to them. You know the drill. Thanks.

[Comrade Doge]

2 minutes ago, NineLine said:

I am relaying this from the Viper team, if you have evidence that shows otherwise I will be happy to take that back to them. You know the drill. Thanks.

Regarding multiple tracks being shown, overlaid on top of each other, check MLU M3 page 156, bottom paragraph regrading Track Correlation. Only one track should be displayed.

 

Regarding the HSD showing Hostile and the FCR showing Suspect on the same bugged target is related to the correlation, it's already been established as hostile on the HSD, it should correlate to the FCR as well (before bugging the FCR shows it correctly as Hostile, the problem only arises after bugging).

[NineLine]

3 minutes ago, Comrade Doge said:

Regarding multiple tracks being shown, overlaid on top of each other, check MLU M3 page 156, bottom paragraph regrading Track Correlation. Only one track should be displayed.

 

Regarding the HSD showing Hostile and the FCR showing Suspect on the same bugged target is related to the correlation, it's already been established as hostile on the HSD, it should correlate to the FCR as well (before bugging the FCR shows it correctly as Hostile, the problem only arises after bugging).

Thanks I will check it out in the morning.

[llOPPOTATOll]

33 minutes ago, NineLine said:

I am relaying this from the Viper team, if you have evidence that shows otherwise I will be happy to take that back to them. You know the drill. Thanks.

Have them talk to your SMEs about it

[NineLine]

7 hours ago, llOPPOTATOll said:

Have them talk to your SMEs about it

We do, but they can only tell us so much, especially when it comes to these types of systems. SME's are still bound by the same laws as everyone else. 

 

[NineLine]

9 hours ago, Comrade Doge said:

Regarding multiple tracks being shown, overlaid on top of each other, check MLU M3 page 156, bottom paragraph regrading Track Correlation. Only one track should be displayed.

 

Regarding the HSD showing Hostile and the FCR showing Suspect on the same bugged target is related to the correlation, it's already been established as hostile on the HSD, it should correlate to the FCR as well (before bugging the FCR shows it correctly as Hostile, the problem only arises after bugging).

I have made a report on this, will see if the team comes back with anything different, but for now consider this reported. Thanks all.