4.11 - AI debugging

[Whacker]

Well that stinks... What's the difference between a .trk and .ntrk? So you have to decide when a mission starts if you want to record it or not? Seems kinda silly.

[IceFire]

Originally Posted by Whacker

Well that stinks... What's the difference between a .trk and .ntrk? So you have to decide when a mission starts if you want to record it or not? Seems kinda silly.

TRK was setup to record the inputs from the player (and AI) into the flight model. It's an extremely unreliable format as slight or minor changes to the flight model and AI modeling over the years has made saving anything in TRK a near useless endeavor. The NTRK format is a very different beast in that it records more information including the actual positions of aircraft and damage states so that the playback is virtually identical between versions no matter how much has changed.

It's why the BlackDeath.ntrk or the Kamikazi02.ntrk still work many years after they were created.

I know what you mean about deciding to record later... and perhaps there is a solution using NTRK that would be possible but TRK was always problematic. As soon as IL-2 went from version 1.0 to 1.01 things started to go astray.

[Luno13]

Right. And those training tracks? Before, you could actually take control of the aircraft to complete the training. Now, it's just a boring movie that doesn't really teach much at all.

What is nice is that you can make an .ntrk of an .ntrk. So, make a long recording of your flight, and then play back and re-record only the interesting bits. It's useful to add the recording indicator as this shows a timer to tell you how long you've been recording, and at what minute something noteworthy occurred. While pressing the recording hotkey creates file like "00001.ntrk" you can go into the records folder and change it to something more descriptive, like "Il2_pwns_noobs" (no spaces or some symbols allowed).

Add this line to your conf.ini under [Game]:

RecordingIndicator=1