Jump to content

Hostile surviliance tracks(empty red triangles) became unknown (solid white bricks) once seen by onboard radar


Recommended Posts

Posted

Hello,

in the attached track file the following issue can be seen:

1. contact appear as enemy DL contact (Hollow red triangle) - as expected

2. Contact appear as DL & radar contact when closing in (Full red triangle) - as expected

3. When locking the target, the target becomes white square  - I Would expect red square with a circle over it

In the HSD it is full red triangle with a circle on it

MK  

FCR Color and lock.trk

Posted

I am sure the devs are at work figuring the symbology out, it can get confusing.

MLU M3 manual page 151 details the symbology for correlated targets between the FCR and Link 16.

Currently it seems that the FCR only shows the unknown symbology once the target is bugged, and not the identity correlated from Link 16. It does however show the correlated identity correctly prior to bugging, and on the HSD.

  • Like 1
Posted
29 minutes ago, Comrade Doge said:

I am sure the devs are at work figuring the symbology out, it can get confusing.

MLU M3 manual page 151 details the symbology for correlated targets between the FCR and Link 16.

Currently it seems that the FCR only shows the unknown symbology once the target is bugged, and not the identity correlated from Link 16. It does however show the correlated identity correctly prior to bugging, and on the HSD.

Green contacts work as expected, I get a full green circle with a thin circle surrounding it once I lock it.

  • 9 months later...
  • ED Team
Posted
On 4/28/2022 at 7:13 PM, desertowl said:

I Would expect red square with a circle over it

we've recently refined the symbology to a more realistic depiction, we'll look into the claims and check, the "red square" is not on the M3 as far as I am aware, but I will run it by the team again

  • Like 1
  • Thanks 1

smallCATPILOT.PNG.04bbece1b27ff1b2c193b174ec410fc0.PNG

Forum rules - DCS Crashing? Try this first - Cleanup and Repair - Discord BIGNEWY#8703 - Youtube - Patch Status

Windows 11, NVIDIA MSI RTX 3090, Intel® i9-10900K 3.70GHz, 5.30GHz Turbo, Corsair Hydro Series H150i Pro, 64GB DDR @3200, ASUS ROG Strix Z490-F Gaming, PIMAX Crystal

Posted (edited)

circle is friendly, square is unknown and triangle is enemy. and to underline this for easier recognition there is the color. green for friendly, white for unknown and red for enemy. so if it is identified, red should always be a triangle. i think it was just worded wrong in OPs post 

Edited by Moonshine
  • Like 1
Posted
2 minutes ago, BIGNEWY said:

confirmed there is no red square,

Just to add IFF has no role in colour or shape, only NCTR and L16

thank you

Indeed, and neither the radar lock should play any role in color or shape (ROE). Yet currently, it does for some reason, changing an ROE of Hostile (decided by Link16), into an ROE of Suspect.

  • Like 2
  • Thanks 2
Posted
6 minutes ago, Comrade Doge said:

Indeed, and neither the radar lock should play any role in color or shape (ROE). Yet currently, it does for some reason, changing an ROE of Hostile (decided by Link16), into an ROE of Suspect.

This.

Posted (edited)

did some test

to start with, Awacs has a contact, identified as bandit -> red on hsd, only outline as my radar does not see him yet.

as soon as my radar has contact, Color changes to white, shape changes to filled square -> weird. DL isnt lost

then i turn my radar completely off to lose the track -> turns red again as bandit on DL

however, turning the radar on and bugging the contact gives me a red triangle even on FCR, yet a white circle outline indicating a bugged contact.. shouldnt the circle that indicates a bugged contact be the same color as the DL? white for unknown, yellow for ambiguous, red for enemy and green for friendly?

upon firing at the contact and cranking, contact turns white again. cant explain that.

 

then trying to lock the friendly AWACS -> HSD shows green circle, FCR shows white square. this symbology thing is reeeeally off, especially since not even friendlies show up as such on the FCR, making this a very dangerous endeavour.

FCR_Color.trk

Edited by Moonshine
  • Like 1
  • ED Team
Posted
2 hours ago, Moonshine said:

we are patient. just for perspective, the OP posted this in april last year...

These things take time, bumping threads does not make them faster. 

thanks

  • Like 1

smallCATPILOT.PNG.04bbece1b27ff1b2c193b174ec410fc0.PNG

Forum rules - DCS Crashing? Try this first - Cleanup and Repair - Discord BIGNEWY#8703 - Youtube - Patch Status

Windows 11, NVIDIA MSI RTX 3090, Intel® i9-10900K 3.70GHz, 5.30GHz Turbo, Corsair Hydro Series H150i Pro, 64GB DDR @3200, ASUS ROG Strix Z490-F Gaming, PIMAX Crystal

  • 3 months later...
Posted

Currently in the viper, if I have the datalink on, when my own radar can see the bandit there’s a yellow square. As the AWACS has identified him as hostile, why is it not a red triangle?

  • 2 weeks later...
Posted

If i IFF my buddy and get a response (green blib), the FCR will not correlate that to the radar contact. Track stays white, HUD target box does not change.

If i IFF a bandit, the track will stay white. I'd have assumed that the track turned yellow (?)...

If i IFF a bandit and do a succesful NCTR ident (Mig21 - obviously hostile), the track stays white. It should turn red... no?

Intended behaviour? User error? A bug? Place your bets!

  • Like 3

My improved* wishlist after a decade with DCS ⭐⭐⭐⭐🌟

*now with 17% more wishes compared to the original

  • 2 weeks later...
Posted

Is it not working as it used to do. System target should be a hollow square, which never appears.

And while in TMS, TMS right short should designate all into system targets which does not, although you can then with another presses on TMS Right,  cycle between "system targets", which are still more like Track targets (full squares).

 

f16-rcr_tws_track_to_sytem.trk

  • Like 10
Posted

Thanks you brought this up. I was trying to use TMS right for multiple targets as I thought it used to work but it did not any more. Thought I was missing something. Following the thread now.

  • Like 3
Guest
This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...