Lookiss Posted April 5 Posted April 5 Hello After releasing the bombs in loft mode, Jester just keeps giving speed updates. He just doesn't stop. Even after telling him to switch to the next waypoint, he's stuck there somehow. See attached trackfile Jesterkeepsgoing.trk
Lookiss Posted April 6 Author Posted April 6 And here's a second track. This time using the Pavespike. I failed to drop and Jester just keep giving speed cues. Jesterkeepsgoing2.trk
BomberEW Posted April 12 Posted April 12 I have this issue too. I stopped using LOFT because of this.
Zabuzard Posted April 12 Posted April 12 (edited) On 4/6/2025 at 7:21 PM, Lookiss said: And here's a second track. This time using the Pavespike. I failed to drop and Jester just keep giving speed cues. When you replay the track in DCS (main menu > replay), does it reproduce the issue as well? The main problem with this issue is that so far no one was able to nail it on a track that reproduces it yet, unfortunately. Its a known bug and the team already did some blind investigations and attempts to fix it, but without a working track it probably will remain very hard to find and fix. Edited April 12 by Zabuzard
Stickler Posted April 13 Posted April 13 19 hours ago, Zabuzard said: When you replay the track in DCS (main menu > replay), does it reproduce the issue as well? The main problem with this issue is that so far no one was able to nail it on a track that reproduces it yet, unfortunately. Its a known bug and the team already did some blind investigations and attempts to fix it, but without a working track it probably will remain very hard to find and fix. I literally just downloaded my own .miz from this bug report and was successfully able to reproduce the bug after four months. While the bug does not reproduce in tracks, can you at least confirm you were able to reproduce the bug in live play, e.g. by following the linked instructions?
Zabuzard Posted April 13 Posted April 13 I literally just downloaded my own .miz from this bug report and was successfully able to reproduce the bug after four months. While the bug does not reproduce in tracks, can you at least confirm you were able to reproduce the bug in live play, e.g. by following the linked instructions?The team has repeatedly confirmed the bug and that it happened during test sessions already as well, that is not the problem.For finding the cause and fixing it its necessary for it to be reproducible in debug mode with the debugger attached. Not just once or twice but like 50 times in a row.Hence the need for a tracl that reproduces the issue when replaying the track :) 1
Stickler Posted April 13 Posted April 13 Just now, Zabuzard said: The team has repeatedly confirmed the bug and that it happened during test sessions already as well, that is not the problem. For finding the cause and fixing it its necessary for it to be reproducible in debug mode with the debugger attached. Not just once or twice but like 50 times in a row. Hence the need for a tracl that reproduces the issue when replaying the track Cheers, thanks for the clarification!
Recommended Posts