Jester “o’clock” positions wholly inaccurate.

[TEMPEST.114]

Hi

 

so I adore the F14 and I fly it everyday. It’s my favourite module, but I’m really struggling in dogfights with how utterly useless Jester is calling out the target’s position. 
 

It’s a trivial bit of maths to use the ownship’s plane datum and get an angle from the hostile, so I’m assuminG it’s an over enthusiastic nerf or a bug, but several times tonight jester said 10 o’clock, then instantly 2 o’clock and back to 10 o’clock but neither i nor the bandit changed aspect, we were in a vertical loop. Similarly I could see the hostile at 12 o’clock high and the dummy in the back said 3 o’clock. 
 

Please can you let me know if fixes are going to be coming for this? Considering I fly with a human Rio most of the time, when I have to rely on jester it’s just too frustrating. 
 

I just watched this video, and even then the calls are utterly wrong and unhelpful,; 

 

Edited September 10, 2021 by Elphaba
Added video link

[captain_dalan]

Though sometimes lagging, Jester's callouts are IMO pretty much correct. It's just that they don't translate well to most head mounted face trackers. I noticed this for the first time when i experimented with a VR about a year ago. Suddenly he got them all right. It's then that i noticed the 2D representation in DCS (on a flat screen) skewers your spatial orientation. Especially when bandits are very high or medium low. A tiny offset can result in shifts from 2 to 10 or from 3 to 9, despite looking to us as if the bandit is still in its original aspect. 

[Kula66]

I asked a couple of years ago and the response I got was that it was caused by a delay resulting from having to fetch and play the appropriate audio file, ie. the call was correct a few seconds ago

[draconus]

Yep, in a merge both aircraft maneuver and that can change relative position even by a few hours on the clock in 1 second.

1. DCS checks bandit relative position when Jester is about to call

2. The proper audio starts playing

3. When you hear "...12 o'clock" it can be already on your six at that moment even if it was only 2-3 seconds since point 1.

[TEMPEST.114]

8 hours ago, Kula66 said:

I asked a couple of years ago and the response I got was that it was caused by a delay resulting from having to fetch and play the appropriate audio file, ie. the call was correct a few seconds ago

 

Then surely the problem is not having all 15 o'clock calls inc level, cached and ready to play? Instead of pulling from the drive each time and having IO lag. This just means it can be fixed. 

[Kula66]

Not sure how much lag I get on a fast M2 and 32GBs of RAM, but it's enough!

[Airhunter]

Yeah in a dynamic environment said calls will always be delayed. 

[draconus]

It's not a performance lag. The files are tiny and cost no CPU time. It's a case when you say something that's no longer true when you finish the sentence.

[Kula66]

Well, here is the official response: