Tracks not showing what really happened?

[darklyt750]

That's strange. Also shortly after I posted this I watched the same .trk without manual time comp. and made it so it was the original camera views and it showed everything correctly. Thanks everyone

[Stig1207]

but it's is more or less related. Playing back a TRK file and you go into 'no cockpit view'(ctrl + 1) there are 'guages' that show TAS, altitude and g-forces. If you do the same with a Ntrak file the 'g-force guage' doesn't work.
Anyone no why?

/Stig

[JtD]

trk files aren't a recording of the flight, they are a recording of the input. So you replay the input, everything else gets recalculated. Including g forces. But the downside is if something is just a millisecond off early on in the track, the whole track goes wild. Reasons for a millisecond difference can be a change of views or some caching when the missions starts. Usually, when I fire up il-2 and go watching tracks first thing, the track plays differently playing it first time then it does playing it the second or third time.

ntrk files are an actual recording, essentially they record everything that's also sent via network in multiplayer games. Apparently, the g load is not transmitted and also not recorded. The format is more stable in the long run, but not quite as smooth as trk. You may occasionally see aircraft warping, which never happens with trks.

[Spinnetti]

Another point is that if you use time compression anywhere, in flight or in replay, its often enough to drop sync between inputs and action on screen... If you avoid time compression, it should be fine. Another thing is, that anytime you change any mods due to the above (it records inputs, not the whole thing), it will throw off timing more times than not. With that understanding, tracks work fine for me.