Crash when saving .ntrk saves - why?
#4

well, what i do(and this is after several years of figuring these things out) is to assign a key to 'Record/Stop Rrcording Track'. then, get in the habit of recording from the start of a mission. you will see a hud message 'recording quick000 started/stopped', something like that, as a visual indicator that it is working.
In my experience, i've never had a crash doing it this way. You can try it, and see what happens. You could also just hit the record/stop button to get the parts/clips you want, so your end result would be to have one long mission, but broken up into several smaller ntrk files.
another very common problem with trk files, is that they don't actually record the mission as it happened.
for example, i played a quick mission where i downed 3 Stukas in quick succession (1 long burst) and was so impressed with myself, i decided to save it afterwards. in the replay, i start firing at the first Stuka, and then promptly fly straight into the 2nd one!!! Wtf, you say? it happens. trk recording is not recommended.
this (almost)never happens if you record an ntrk.
yet another reason to record ntrk, and not trk, is that the chances of your mates being able to watch it on their machines is slim to none - the trk files aren't compatible with different versions of the game, etc.
Ntrk does not have this problem. so, ntrk wins hands down in either case.
All i can say is to try what i suggest, and see how that goes for you :wink:
post again if you're still having problems.
Reply


Messages In This Thread

Forum Jump:


Users browsing this thread: 7 Guest(s)