Jester Speed Call Out on loop

[WinOrLose]

In my last two flights Jester has been stuck in a speed call out loop than never ends. I had to silence Jester but meant the other call outs I needed, VIP etc were lost as well.

It happened at low level and above 500 KTAS.

[Zabuzard]

Thanks, this is happening occasionally since release but no one was able to pin it on a working (short SP) track.

[BJ55]

On 11/1/2024 at 7:22 PM, Zabuzard said:

no one was able to pin it on a working (short SP) track

That's because tracks are bugged. The one attatched was made from a MK-82SE Laydown test and had the speed call bug (+ the L late delivery bug), but when I replayed the track there where no speed calls at all (and bombs are released at button press, above the IP).

F-4_ag_train_cauc_82SE.miz F-4_ag_train_cauc_82SE_L_wIP1.trk

[Zabuzard]

Likely because you used the Jester Wheel or Bombing Table at some point during the recording, which is not captured in tracks. You would have to reproduce the issue without the UI (or only using keybinds instead of mouse/head movement).

[BJ55]

I've did as you suggested: in the track replay bombs are released in the same point as in mission, but there's only one speed call, while in mission I've had four sequential speed calls. Edit: sometimes there are 4-5 speed calls, other times it's endless like OP said. (I have half refresh rate HBUI)

F-4_ag_train_cauc_82SE_L_wIP9.trk

Edited November 4, 2024 by BJ55
added text

[Zabuzard]

I've did as you suggested: in the track replay bombs are released in the same point as in mission, but there's only one speed call, while in mission I've had four sequential speed calls.
F-4_ag_train_cauc_82SE_L_wIP9.trk

Thanks for the replay. We will see if it can provide insights. Nasty issue :)

[Volator]

Came across this bug during my last two attempts at loft bombing, plus when I approached Nellis with Jester activated frames suddenly became extremely bad. Once I deactived Jester frames were back to normal. Felt like Jester was "clogging the system", if I may call it like that.

Track would be available but due to the problems above (+it is a very long track) uploading it wouldn't help I guess.

[WinOrLose]

On 11/18/2024 at 8:58 PM, Volator said:

Came across this bug during my last two attempts at loft bombing, plus when I approached Nellis with Jester activated frames suddenly became extremely bad. Once I deactived Jester frames were back to normal. Felt like Jester was "clogging the system", if I may call it like that.

Track would be available but due to the problems above (+it is a very long track) uploading it wouldn't help I guess.

I’ve had the same on the Syria map. 

[Volator]

I thought this issue had been solved by the latest update, but yesterday I experienced the same bug again in a custom loft training mission. The first flight was OK, but rerunning the mission two times the speed call bug was there again...

[Zabuzard]

I thought this issue had been solved by the latest update, but yesterday I experienced the same bug again in a custom loft training mission. The first flight was OK, but rerunning the mission two times the speed call bug was there again...

This is happening occasionally since release but no one was able to pin it on a working (short SP) track.

Our blind investigations and attempts on it didnt do the trick, sadly.

[WinOrLose]

We had a multiplayer flight of 3 last night and it happened in all 3 aircraft. Only solution was to stop Jester talking.
 

In addition 2 of us suffered massive FPS loss which was only resolved by disabling Jester. 

[Zabuzard]

We had a multiplayer flight of 3 last night and it happened in all 3 aircraft. Only solution was to stop Jester talking.
 
In addition 2 of us suffered massive FPS loss which was only resolved by disabling Jester. 

Right, we are aware. It happens to us occasionally as well. The issue is not knowing that it happens or what it does.

The issue is that in order to find the source of the problem and to then fix it, we need a working track file (short and SP) that reproduces the problem when replayed within DCS.

Since then we can attach a debugger to the game while it replays the issue and inspect the system in order to spot what is going wrong in the code.

So far neither we nor the community was able to capture it on a proper track yet, sadly. And our ~3 blind attempts at fixing "something that looks odd in the relevant code" apparently did not fix it. At that point the only way forward is to work with a track.

[Volator]

@ZabuzardHere are five tracks that hopefully help in some way.

To me the problem occurs when I predesignate waypoints as IP and TGT in the ME. Without that predesignation, the speed callout loop bug does not appear. Please find three tracks witout designation and no bug, and two tracks with designation and bug appearing attached.

 (In one flight that I did not record it appeared to me as if when dropping bombs in pairs only and not in ripple the bug would also NOT show up, but I have to check this further.)

---Edit--- tracks removed, invalid

Edited December 15, 2024 by Volator

[Zabuzard]

@ZabuzardHere are five tracks that hopefully help in some way.
To me the problem occurs when I predesignate waypoints as IP and TGT in the ME. Without that predesignation, the speed callout loop bug does not appear. Please find three tracks witout designation and no bug, and two tracks with designation and bug appearing attached.
 (In one flight that I did not record it appeared to me as if when dropping bombs in pairs only and not in ripple the bug would also NOT show up, but I have to check this further.) Test_F-4_speed_callout_no_IP_no_TGT_001.trk 
Test_F-4_speed_callout_no_IP_no_TGT_002.trk Test_F-4_speed_callout_no_IP_no_TGT_003.trk Test_F-4_speed_callout_yes_IP_yes_TGT_001.trk Test_F-4_speed_callout_yes_IP_yes_TGT_002.trk

Thanks for the tracks. Can you replay them locally in DCS to see if they work and replicate the issue?
That's how you can verify yourself if the track will help us or not. Thanks :)

[Volator]

7 minutes ago, Zabuzard said:

Thanks for the tracks. Can you replay them locally in DCS to see if they work and replicate the issue?
That's how you can verify yourself if the track will help us or not. Thanks

Rgr, will try later...

[Volator]

3 hours ago, Zabuzard said:

Can you replay them locally in DCS to see if they work and replicate the issue?

Lol, I checked the two tracks that were supposed to show the issue... and of course the tracks do not work. I did a loft attack and pressed the bomb release button overhead the IP. In the replay though the bombs release immediately, and the speed bug does not appear of course... sigh.

But at least I can confirm how to circumnavigate the bug: Do not designate the waypoints (at least not the target, further testing might be needed), and you should be fine.

Edited December 15, 2024 by Volator

[Stickler]

I was finally able to consistently reproduce the bug five times following the below steps. The problem is, as Volator already reported, that the issue does NOT occur in the associated track(s).

1. Put the Caucasus.lua into the C:\Users\XXX\Saved Games\DCS.openbeta\Config\RouteToolPresets\ folder, overwriting the old file, if present.
2. Load the attached .miz in the ME.
3. "Launch Multiplayer Server" from the "Flight" menu.
4. Take the F-4E slot on the Blue side and load the "Jester_Repeat" preset.
5. Spawn
6. Go to the back seat and set the pull-up and release timers to 300 (30.0) seconds.
7. Return to the front seat, select A/G sight, stations 2 and 8, "BOMBS", Master Arm HOT, and TL mode.
8. Steer straight ahead to the railroad bridge (VIP) at 500 KTAS.
9. When directly over the bridge, hold the bomb release button to start the pullup timer. Do not wait for Jester to report the fix.
10. Once Jester is done with his "INS updated" call, the speed callout loop starts.

Caucasus.lua server-20241215-204029.trk jesterrepeat.miz

Edited December 15, 2024 by Stickler

[Zabuzard]

I was finally able to consistently reproduce the bug five times following the below steps. The problem is, as Volator already reported, that the issue does NOT occur in the associated track(s).

1. Put the Caucasus.lua into the C:\Users\XXX\Saved Games\DCS.openbeta\Config\RouteToolPresets\ folder, overwriting the old file, if present.
2. Load the attached .miz in the ME.
3. "Launch Multiplayer Server" from the "Flight" menu.
4. Take the F-4E slot on the Blue side and load the "Jester_Repeat" preset.
5. Spawn
6. Go to the back seat and set the pull-up and release timers to 300 (30.0) seconds.
7. Return to the front seat, select A/G sight, stations 2 and 8, "BOMBS", Master Arm HOT, and TL mode.
8. Steer straight ahead to the railroad bridge (VIP) at 500 KTAS.
9. When directly over the bridge, hold the bomb release button to start the pullup timer. Do not wait for Jester to report the fix.
10. Once Jester is done with his "INS updated" call, the speed callout loop starts.

Caucasus.lua server-20241215-204029.trk jesterrepeat.miz

Thanks for investigating and the instructions. Fingers crossed we can repro it with that as well