Replay system doesnt work properly

[Eugel]

I know that the replay system always was a bit glitchy, but since 2.7, 100% of my replays are useless.

All replays I recorded with 2.5 now show something completely different. I´d understand if the weather in those missions would do weird stuff. But in one replay, my aircraft didn´t even take off. It taxied in a weird 90° angle to the runway and speeded off into some building and exploded.

 

Or in a recent mission I recorded with 2.7 I did 4 Maverick attacks against enemy tanks and some other stuff. After that, I got one engine shot and limped back to base and barely managed to land. When I watched the replay, my plane was shot down after the 2nd maverick and crashed.

 

Just now I played a mission in the Huey where I took off from a FARP, flew north into a city, picked up some infantry, landed back at the FARP, took off again toward the city, engaged some enemy infantry and flew back again. 

In the replay, the Huey didn´t land on the FARP, but 100 meters off to the side, and just took off to the west instead of heading back north to the city.

 

This is really a bit annoying, as I am still learning and like to look at my replays to see what I did wrong. But this is really pointless if the replay just shows some random stuff happening.

Edited May 5, 2021 by Eugel

[Sarabi]

yep, in my case got crashed or get shot down by enemy when on Tackview shows the mission/s I was playing.

[dorianR666]

11 hours ago, Eugel said:

All replays I recorded with 2.5 now show something completely different

trackfiles are not compatible across dcs versions. you have to replay in the same dcs version as the version used for the recording.

 

if it works otherwise, thats merely accidental.

 

11 hours ago, Eugel said:

But this is really pointless if the replay just shows some random stuff happening.

i dont know if you know it, but the trackfile only records your input. its all resimulated. error accumulates over time which means things like a missile you dodged resulting in missile hitting when replayed, or you landing a bit off.

 

not really a bug, just limitation of this technology.

Edited May 5, 2021 by dorianR666

[Eugel]

Well I still consider this a bug when the replay function does not "re-play" what actually happened during the mission.

And for me it got worse with 2.7

I´m not talking about long or heavy missions, even with just a single aircraft, all replays longer than ~10 minutes are pointless.

Edited May 18, 2021 by Eugel

[peachmonkey]

yes, in my experience after 5 minutes in to replay the action doesn't represent anything I did when I was flying.

 

However, I did use fast forward to move the replay to the action points.

 

If fast forwarding corrupts the re-simulation I'll give it a try with realtime only. Pretty weird bug but oh well...

[Nealius]

The "fast-forward breaking tracks" is an old trope by now. That is not the case. Any track that would work at regular speed, will still work at x10 speed. Any track that would not work at regular speed, would also not work at x10 speed. 

 

The mechanism that breakes the tracks is not known because it is wildly inconsistent across modules, with different triggers for each module. In 2.5.6 Spitfire replays used to work flawlessly, for example. After 2.7, they consistently break when exceeding a certain speed in a descending turn. A-10C-II tracks will replay flawlessly in simple training missions, but will have position desync when missions are more complex or lua scripting is involved. Then you have modules like the Tomcat that never work, period. A while back in 2.5.6 I had a really wild one where the F-5E tracks would break with shadows set to Medium or higher, but would replay flawlessly when shadows were set to Low. 

Edited May 18, 2021 by Nealius

[Eugel]

On 5/18/2021 at 4:54 PM, Nealius said:

A-10C-II tracks will replay flawlessly in simple training missions, but will have position desync when missions are more complex or lua scripting is involved. 

 

I just repeated my A-10C II target practice mission. No scripts involved, only one unit in the air (me) and mostly static ground targets. The mission duration was 47 minutes. 
When I watched the replay, the startup was fine, and the first two bombing runs with mk82´s were correct. After that in the actual mission, I made an attack run where I fired 4 Mavericks then turned to the next waypoint and landed safely. 
In the replay however, I fired only one Maverick, flew over the enemy base and rammed my A-10 into the ground.

It´s not just position desync and the replay isn´t resimulating my inputs. My inputs fired 4 Mavericks. It is really like the first 10 minutes are fine and after that it looks like the pilot just died.

[Nealius]

2 hours ago, Eugel said:

I just repeated my A-10C II target practice mission. No scripts involved, only one unit in the air (me) and mostly static ground targets. The mission duration was 47 minutes. 
When I watched the replay, the startup was fine, and the first two bombing runs with mk82´s were correct. After that in the actual mission, I made an attack run where I fired 4 Mavericks then turned to the next waypoint and landed safely. 
In the replay however, I fired only one Maverick, flew over the enemy base and rammed my A-10 into the ground.

It´s not just position desync and the replay isn´t resimulating my inputs. My inputs fired 4 Mavericks. It is really like the first 10 minutes are fine and after that it looks like the pilot just died.

 

That's strange. Last I did an A-10 training mission, roughly the same length, replay was flawless from engine start to engine shutdown.