PrimetimeCasual

Just noticed the same - rather annoying, as I wanted to create a mission where waves spawn while the older ones might still be active. Definitely recently introduced, and hopefully fixed soon...

@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.

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.

That explains so much, actually. I'll RTFM and see if I can get this sorted. Once again, you helped me out a lot!

Will check - but it does sound like that might be the issue indeed. I figured I wouldn't need to with a fresh install / reset profile, but then again, I'm not sure how the VAICOM profile is generated from the keyword database.

I did a fresh install with the community edition, but I noticed that I can't control the VAICOM kneeboard. I checked and the diagnostic returns over 500 missing voice commands, including those for the kneeboard (and presumably realistic ATC). I did a reset of the profile, but those commands are still missing. I also tried resetting license data (I had a purchased pro license before). Do I need to set them manually?

I actually didn't know that, thank you. I thought comms menu was comms menu, no matter where, for "easy communications". Guess I'll do the switch properly then and disable easy mode.

General -> Open Communications Menu

It's entirely possible that I'm doing something wrong here, but nevertheless. This happens in created fast missions, or missions I throw together in the ME. I'm in the Hornet, easy communications are ON, the airport is set to BLUE, but all the ATC options are dark grey, i.e. unavailable as if they are not in range, and don't respond to any calls. Both when I'm on the ground at the airport, and in the air. AWACS - works. Flight - works. Ground crew - works. JTAC - works. The radio also selects the correct channels (easy comms), it's just as if ATC (and ONLY ATC) is on strike...

I just registered to say THANK YOU, both to the original creator (even if I bought it only a few weeks ago, I'm not reversing the charges, since they did the original work), and of course the community team that is now maintaining the tool!