not a bug Why locking targets is not working?

[skywalker22]

As you can see I am trying to lock two targets for 30 seconds (with TMS UP command), just on the end I succeed.

Why it doesn`t want to lock the targets and put them into System Targets?

 

 

PS: please do not mark at solution, I will do that when I will understand what was going on here!

Edited July 4, 2021 by skywalker22
trying to understand whats going on here!

[Mustang25]

You need to adjust your scan volume to match the datalink contact's altitude. You can see that for both, the empty red symbols mean that you have a datalink track but your own radar cannot see them. You can refer to pg 157 of the official manual for more info on datalink symbology.

[skywalker22]

Lets analyze a bit more:

- 1st target: from 12sec to 27sec of the replay I was inside the limits with my antenna. Its true, enemy aircraft was 100 feet above ground (I was on 15k-20k). Maybe my radar didn`t see it because of the ground cluttering, right?

- 2nd target, which was even higher then me, on the open blue sky, I was trying to get a lock from 40sec to 59sec of the replay, when I finally got the lock. But it needed 20seconds to acquire. Really strange to me, don`t understand that really.

[Furiz]

Those red icons are data link contacts, you can not lock them,

what you want to lock is the little white square that appears, the white square means your radar picked it up,

 

You are in TWS mode, so to lock contacts in TWS mode you have to wait a few sec for the empty red triangles to become filled red triangles, then you press TMS RIGHT to set them as system targets, then you can step through the targets with TMS RIGHT, and fire your missiles at them simultaneously while you are in TWS mode.

 

 

[Frederf]

First target you couldn't see because he was at 1000' or possibly less. I thought it was that 3000' contact behind him but that is probably genuinely another aircraft.

 

Second target you didn't develop a track file fast enough. Several scans are needed to develop a track file which takes time especially with the widest possible search volume. When you see a white contact dot and you know it's your man, select it immediately. Don't wait for track and correlation. Also while the radar can do A6/4B it's not ideal for fast paced acquisition. The narrower your scan volume the happier and snappier your radar performs.

 

I recommend RWS A3/2B unless you feel safe and need to scan maximum volume. This is where having NAV in RWS A6/4B, AA in RWS A3/2B, and MO in TWS A3/2B is helpful. With one UFC button and a throttle switch you have access to three pre-set up radar modes. Unfortunately DCS isn't there yet. There are hands on adjustments for azimuth and to go RWS-TWS which will have to do. RWS A3/2B or 4B for search, TMS right long to go TWS for engagement. TWS should be in A3/2B pretty much always. We're also missing spotlight scan (TMS hold for A1/4B with auto wide acquisition on release) which helps a bunch when you know the guy is there and you just want to lock him already.

 

I noticed you trying to lock up hollow triangles. Don't bother. On the other hand if you see a white contact you do not have to wait for it to become a track and correlate. If there is a contact in white near (or inside) a hollow L16 object track the white thing.

 

There is a particular bug to look out for. I thought I saw it because of the separate L16 and radar contacts but I'm not sure since they were at way different altitudes. But keep an eye out for: L16 and FCR tracks are showing horizontal range and slant range respectively. For example if he's 10,000' away and 10,000' below you he's 14,140' away. The radar display will show the radar contact at 14,140' away while the L16 object is placed 10,000' away. If there's a big angle to target up or down expect the radar contact to appear farther away on the scope than the L16 item.

[skywalker22]

Thank you both. Now the picture of how to handle has become waay clearer and understandable.

@Frederfthank you for exhaustive explanation. Awesome info.Btw, I have all these FCR`s commands on my hotas, so I can adjust them on the fly accordingly.

Edited July 4, 2021 by skywalker22

[Falconeer]

In the first couple of seconds, the bandit you are trying to lock is under the search zone of your radar. He is flying between 500 and 1000 ft above ground and you radar is scanning in the ranges between 17000 and 50000 ft. (the 2 numbers next to your radar cursor) Your radar simply doesn't see it and the reason you can see it, is because its  a datalink target. Later on, the same thing happened with the second target. He was outside of the scan zone of your radar

 

To fix this "problem", you need to lower your radar antenna to match the targets altitude

 

Imagine the radar search cone is like a flashlight in the dark, you need to point the cone over a target to see it

 

After you matched the targets altitude, the radar needs a couple of seconds to build up a track in TWS, then you can lock it (solid square)

Edited July 4, 2021 by Falconeer