Why Jester can't find targets?

[ebabil]

I am playing on 4ya servers. F10 map is fully open. So I can see where the enemy is instantly. I get the same altitude and head-on. Give the "nearest enemy lock" or "specific target" commands.  There are awacs as weel so I can see them in TID. But almost all of the time, jester can't see it. It sees us and shoots. 

Also, in same server, I mark exact locations of the ground units. And in Q mode, he is unable to find specific target more than 50%

Am I doing something wrong and will this feature improve? 

 

"No can do boss" "Unable".

 

[The_Tau]

Jester is not AI RIO, he is an interface for radar. He doesnt look for targets, he just presses buttons. You have to baby sit him and tell him exactly where to look : Scan at distance 20nm at 0 FT etc. You have to constantly look at TID and check if AWG9 sees tracks. No Tracks, Jester cant lock it. Make sure that its RADAR TRACK and not DATALINK TRACK. These are two different things. Only exception is ONE command, lock specific track, which allows jester to TRY to lock to datalink tracks if its currently outside radar scan range but WITHIN gimbal limit

 

Of course AWG9 limitations still apply, so beaming and cold targets are very hard to lock in PD STT.

[draconus]

On 4/26/2024 at 4:05 PM, ebabil said:

Am I doing something wrong and will this feature improve?

How can we know? Videos, tracks?

Learn Jester and AWG-9 limitations and it'll be much better. Practice in SP missions, use PAL for closer air targets (<20nm). Use PLM or VSL for very close visible targets (<5nm).

"Enemy lock" request will only work for identified (no IFF response) radar tracks.

What Q mode? There are many. Generally if you already have a mark on the F10 map, you should ask Jester to assign it as WP then QWP it and only then start searching for any unit or specific type if it's a group. You can't be too far away obviously and you should fly in a way to have this WP area visible on the LANTIRN.

A few more radar/AWACS related things to have in mind: