Jester not locking, only focusing

[Rhinozherous]

Hello!

I have setup a training mission with MIG21 drones flying straight and not reacting to train radar handling

- I am 10 to 5  NM behind the mig in about 20.000ft (over water - not much clutter) and have the mig on the radar. 

- Master Arm on - CW for the AIM7M is on for some minutes - interlock on - HUD in A/A.

- Jester is focusing on the mig. When I now hold Jester Context LONG he keeps focusing and saying something like "Focusing on your target".

But he never is actually locking the target - I mean Jester is not saying something like "Locked" and I dont get any symbology for the AIM7 range and stuff.

What do I wrong?

Thank you!

Edited May 25, 2024 by Rhinozherous

[Zabuzard]

Ssounds odd, that's the voice line for target switching. Could you send a track file? Then I can check what commands Jester received :)

[Grundar]

If there are multiple targets I believe you have to first do a short press followed by a longer press for the Jester context option.

If they are visual try using Auto Acquisition mode - mapped to the nose steering button on your joystick (or assign it if not assigned).  Also if you are trying use CAGE you need to have your nose on the target to affect a lock - 5 degrees I believe is the area you have.

 

Edit: I should add double quick of the Jester Context button resets targets.

Edited May 25, 2024 by Grundar

[Nuggetz]

I have been having the same type of issues leading to very inconsistent launches of Fox1. No real issues with Fox 2. 

[Rhinozherous]

52 minutes ago, Zabuzard said:

Ssounds odd, that's the voice line for target switching. Could you send a track file? Then I can check what commands Jester received

I will provide a Track asap. I have to add that there was no problem locking a target when I start in Air.

[Rhinozherous]

@Zabuzard In this video from casmo you can see him not locking - only talking phrases like "Roger" and "I got that" at timestamp 07:33.

https://youtu.be/uCc29oPhlfk?si=WzqsjhEKGAlqUIu7

[Zabuzard]

Quite odd. Never seen that happen. Gonna investigate.

[Nihu]

hey, I am experiencing the same thing as described above - jester is just focusing but not locking any targets on long press of the context action button. He will, however lock it via the round menu. I think this has something to do with a cold start because when I spawn in the air, same as the other user above said, this is not occurring at all. Thanks for investigating this!

[PhantomHans]

I've had this same issue as well but I'm also just getting poor radar performance out of Jester.

 

Flying at 13,000ft looking for targets at 15,000 to 20,000 he can't seem to find them until WVR.

[jojo]

7 hours ago, Zabuzard said:

Quite odd. Never seen that happen. Gonna investigate.

It's hapening at time 07:45

Edited May 25, 2024 by jojo

[ShinyMikey]

Had this same issue today. Didn't seem to be a problem yesterday, today's flight was from a cold start...not sure  if that had any affect on it.

[bomkata]

I am having this issue just as described as op. sat behind a mig 2 min no lock.

Edited May 27, 2024 by bomkata

[LizardKingYB]

Sometimes its happening (

[SkYwAlK3R-_]

Same issue here, tried it multiple times now but no success in locking targets Consitently. Same Voicelines and same thing like in Casmos Video!

[Aphelion079]

Any updates? Still seems to be happening.

He works fine if you're in ACM and CAGE/Borseight but he wont lock from a scan. Tap focus, then hold and "yup" "I got him" etc. but he never turns into a STT.

[Zabuzard]

Can someone replicate it on a short SP track?

I havent yet been able to reproduce it and my only guess so far would be that he is for some reason getting the short-context command (switch target) instead of the long (lock target).
Sometimes user error because they thought short-click is whats needed, but perhaps also a DCS issue (perhaps performance or hardware related) where the command is interrupted momentarily.

In some other cases I saw, the WSO pit was setup incorrectly, for example in TV instead of RDR mode - also sometimes due to user error (TGT FIND on the weapon knob for example), but also due to a bug that has been fixed in the latest patch (switching the knob too fast).

[thodre]

Happened to me only once on a MP-Server - never had it again, but heard of it. Not a consistent bug for everyone i talked to.

[Rhinozherous]

 

On 6/9/2024 at 11:10 AM, Zabuzard said:

Can someone replicate it on a short SP track?

I havent yet been able to reproduce it and my only guess so far would be that he is for some reason getting the short-context command (switch target) instead of the long (lock target).
Sometimes user error because they thought short-click is whats needed, but perhaps also a DCS issue (perhaps performance or hardware related) where the command is interrupted momentarily.

In some other cases I saw, the WSO pit was setup incorrectly, for example in TV instead of RDR mode - also sometimes due to user error (TGT FIND on the weapon knob for example), but also due to a bug that has been fixed in the latest patch (switching the knob too fast).


 

Still happening to me, alltough not always. Hardware is not the reason, checked on VIRPIL software if button is flickering when hold, but it is not. Something has to get thru as jester is calling his phrases. When I trie to provide a track it does not happen  Last time on MP flying with friends. 

[unclesneep]

Also having this issue.  Jester slews over ti the target.. I long press to lock, and he says Roger, or focusing on your target.  Will not actually lock, and I don't get the dot and circle indicating a lock.

 

I'm also having issues where jester will get stuck at either 10 miles or 5 miles.. double hitting context he says back to regular scan.. but nothing happens...still stuck at 5 or 10 miles.. will check to see if it's only on cold start 

 

 

[Mike_CK]

Unless someone who is having the issue posts a track file as requested, the answer will continue to be “please post a track file”. I haven’t been able to get on to play around with it this week or I would 

[Zabuzard]

We are trying to do some blind fixes and continue to investigate in the meantime. But yeah, capturing it in a working (short, SP) track would be extremely helpful.

[Zabuzard]

It appears that you are sending the command multiple times.

Cause after commanding a lock, clicking it again would command to unlock the target (which gives the focusing phrase).

Not sure if people are impatient and click the button multiple times or if there is perhaps a hardware issue or DCS shenanigans interrupting the command and sending it again.

I am still hoping to get hands on a working short SP track showing the issue.

Edited June 19, 2024 by Zabuzard