Jump to content

Need explanation why the FCR Symbolic is different for the same doing/logic using Datalink or not (yellow or white symbolic).


Recommended Posts

Posted (edited)

Hello,

I assume that what is shown in Chuck's guide is what we can currently expect in DCS for the F16 (possibly even a little more).
The FCR section shows the symbology for the different states of an object detected by our own or another RADAR in our data link group.
I am not able to turn the symbolic of a tracked target into the symbolic of a system target in such a case (shared Data (yellow squares)), at least I have never seen a yellow hollowed-out square for months (could be years ;)). Even if I bug a target (a circle around the target) the yellow square will stay fulfilled.
I only see the symbol of a system target if I am not receiving data from other group members/AWACS (Datalink is disabled).
It seems to be important that the pilot knows which targets are system targets, otherwise the symbol would not be there even in the mode without data link (only white squares).
I therefore strongly assume that recognizing which targets are system targets will also be possible with active data exchange with other members.

In the track-file you can see there is a big difference in symbolic and how good you can track the selected targets. Without the Datalink, I can easily see the differences in the symbolic (search -> track -> system -> bugged). With the Datalink enabled I am unable to see which target is in what current state. I am unable to see if the yellow symbol is a search, a track or a system target. Impossible to see that.

A lot better and more pleasurable situation occurs as soon I am switching the data transfer to off. Now I am able to see in what state one of each target is. The symbolic (white) works like in Chucks guide.

The questions that now arise me are as follows:

1. is Chuck's guide wrong? If so, is there an explanation as to why the symbology and the way I can lock targets is completely different with and without a datalink connection and why it is much more difficult to lock targets with a datalink connection than without an active datalink connection?

2. if Chuck's Guide is correct, when will the error in the symbolic display be corrected and the problem with the more difficult target locking in the datalink mode be resolved?

 

No Mods enabled, all Data cleared, slow repair was done.

 

Edit:

To mention a few more details.
In active datalink mode, it is often not possible to turn all targets that are in FCR (in TWS mode) into system targets with a short TMS right. Typically, only the first detected target is immediately made into a bugged target (the part making a system target will be cut out, because there is no symbology for system targets anymore if you are in the Datalink mode). A new TMS to the right regularly has no effect. It will not switch through all system targets (because in the Datalink mode the FCR is mostly unable to make system targets?).
TMS down only changes the symbolism once, and only if a target was previously bugged.
Since you cannot see from the symbols what status the targets are currently in, you often TMS down until you leave the TWS mode.
Two completely different symbolics for the same subject, and only because you get more/better data. But exactly when you get more and "better" data, you have a harder time selecting targets because the symbology is severely limited. And the target acquisition is significantly more difficult/restricted.
I can't imagine with the best will in the world that this is what the designer intended.

track_f16.trk

image.png

Edited by Nedum
  • Like 7

CPU: AMD Ryzen 7950X3D, System-RAM: 64 GB DDR5, GPU: nVidia 4090, Monitor: LG 38" 3840*1600, VR-HMD: Pimax Crystal, OS: Windows 11 Pro, HD: 2*2TB Samsung M.2 SSD

HOTAS Throttle: TM Warthog Throttle with TM F16 Grip, Orion2 Throttle with F15EX II Grip with Finger Lifts

HOTAS Sticks: Moza FFB A9 Base with TM F16 Stick, FSSB R3 Base with TM F16 Stick

Rudder: WinWing Orion Metal

Posted

Thank you for taking the time to make this post. Track file type handling has been an ongoing issue for a very long time. Although there was not a conclusive response last time, hopefully @BIGNEWY or @NineLine can weigh in on this again. 

  • Recently Browsing   0 members

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