TRK files differ vastly from gameplay

[PrimetimeCasual]

I'm aware that there are issues with long replays, fast-forwarding, or complex missions.

But recently I can't even save a trk file of a simple 1v2 engagement lasting 5 minutes without it getting corrupted?

 

It's not small differences, either. It's massive, the AI behaves completely differently in the replay than it did during the flight itself.

 

See attached video: 2024-05-21 23-00-40.mkv

The TacView on the left is from live gameplay, and the TacView on the right is from playing back the TRK file. Back to back, as you can see on the timestamps, so there was not DCS update or anything in between.

In the trk file, the Flankers come in at 35k instead of 27k, they shoot missiles they didn't shoot "in reality", etc... I get that the trk file only saves inputs, but clearly, something else is horribly broken.

 

Is there literally *anything* I can do to mitigate or minimize those corruptions? As it is now, it's not even useful for providing analysis to the Devs, as it's simply not what happened.

 

I'm on Multithreading, VR, singleplayer. This issue has become worse with every update so far.

Edited May 21, 2024 by PrimetimeCasual

[Heater]

This has always been an issue.

[silverdevil]

12 hours ago, PrimetimeCasual said:

I'm aware that there are issues with long replays, fast-forwarding, or complex missions.

But recently I can't even save a trk file of a simple 1v2 engagement lasting 5 minutes without it getting corrupted?

 

It's not small differences, either. It's massive, the AI behaves completely differently in the replay than it did during the flight itself.

 

See attached video: 2024-05-21 23-00-40.mkv

The TacView on the left is from live gameplay, and the TacView on the right is from playing back the TRK file. Back to back, as you can see on the timestamps, so there was not DCS update or anything in between.

In the trk file, the Flankers come in at 35k instead of 27k, they shoot missiles they didn't shoot "in reality", etc... I get that the trk file only saves inputs, but clearly, something else is horribly broken.

 

Is there literally *anything* I can do to mitigate or minimize those corruptions? As it is now, it's not even useful for providing analysis to the Devs, as it's simply not what happened.

 

I'm on Multithreading, VR, singleplayer. This issue has become worse with every update so far.

 

i find a little improvement when i reply the track with all my controllers disconnected.

[PrimetimeCasual]

@silverdevil

That is something I haven't tried yet, thanks!

Tacview-TRK.zip.acmiTacview-LIVE.zip.acmim2.trkKOLA_HVTIntercept_1v4.mizDxDiag.txt

 

I also forgot to attach any proper files.... so here's the TRK, the MIZ, as well as two ACMI for TacView (one from gameplay, one from replay), as well as the DxDiag output.

Please note that this was from just before the DCS Update with the F4, so if that is still any use, I don't know.

[KoN]

Its been broken for ages , was fixed a few months back , but now again broken . DCS . !!!