Track Replays Totaly Off.

[ericoh]

Hey, i dunno where to post this other then here, pardon me.

 

I was just flying a pretty perfect hover-taxi-takeoff-landing (for my own skillset ^^) i wanted to review this in a track.

 

Now! As i watched the track replay i noticed that it was totaly off, it didnt fly where i did, and apperently in the replay my Huey crashed. I did not crash. How could this happen? :noexpression:

 

Greetings

[TimeKilla]

Did you fast forward the track any, I noticed a issue if you fast forward to fast in 1.2.3 that the track would mess up.

[ericoh]

Yea i fast forwarded the beginning, then it completly messed up.

[cichlidfan]

That is a long standing, known issue with DCS World not the Belsimtek Huey.

[159th_Viper]

Cannot remember the last time I have had replay issues - non-existent for me with these latest versions. Once you save a track, replay it through once without doing anything to see if it is OK. If so, just make a copy and then use the copy to fast-forward and such things. If you are specifically recording tracks for a purpose, fly the mission without TrackIr as well - can always edit views in later. Not saying that will help alleviate replay issues some experience - might though.

[Fuggzy]

I noticed the same thing in the only replay I've watched. I ran it directly after ending the mission, from the debriefing page. Didn't use any fast forward or anything.

 

I'd just flown the Target Practice instant action, and flew orbit around the Fuel truck convoy that's on the move. Beat them up pretty good with the door gunners, was feeling proud, so I watched the track. Started out pretty good watching from one of the stationary house objects, but I noticed with each firing pass my fire was hitting further and further away. By the time I stopped watching the track, my chopper was laying down heavy fire in empty fields nowhere near the trucks, I'd guess at least 1km away. Weird. Is that because I didn't save the track and call it up from the Replay viewer?

[MaverickF22]

Now i've also found that this unpredictable track recording feature from DCS is more likely to cause a problem on DCS modules instead of to DCS World aircrafts like Su-25's..., which are free from any mishaps of any kind..., or at least the margin of error is quite small.

 

The problem isn't at all if you replay the track fast, slow, change views or let it untouched!:P It simply makes no difference at all!

 

I've tested it too, and only when it's recording a track of let's say HUEY, or P-51 or other DCS module's aircraft, the track shows a whole different story..., and it doesn't even matter how many times would you like to reload the replay and start it over again thinking that the playback speed or changing the views will affect the outcome..., NO! It won't change a damn thing and will replicate the same exact things every time!

 

So the problem is HOW does this feature actually record movements directly as they occur when you are flying, there's the problem..., because if it interprets what you are doing, different than what you actually do..., that's what it is going to show you as well in the replay, no matter what you'll try to do to the replay..., it's done and can't be modified unless you take control:music_whistling:

 

Only, for the SU-25's there seems to be almost no margin of error when replicating the exact same things that happened, but it also tells a different story sometimes, yet not too far from the truth, unlike for other DCS aircrafts, which are like having a different recording feature than that from DCSW alone. No matter how many times i tried to jerk the view around and view modes and go from very slow replay speeds to screen freezing speeds for long seconds, then going back to 1x speed again, it told the same thing every time..., for Su-25's it told with 99% accuracy, but for others with less than 50% let's say!

Edited July 26, 2013 by MaverickF22

[MaverickF22]

I've also found another thing! If you respawn or refly during the same mission..., each time you'll refly/restart, the track recorder will further increase the initial error. I've tested today that, if i was flying a mission with the Su-25, then for whatever reason i've pressed refly and continued the same mission or let's say, stood logged on the same server..., each time i would've got more unreal stories in what the track had to replay.

 

So i've tested that the recorder will actually and accurately replay exactly what you did with no errors at all, but only the first flight of the mission or since you've logged onto a server..., while since the 2nd up to the last respawn/refly which you may take, the errors will pop up and accumulate after each of them.

 

So far, this only applies to the P-51 and SU-25's as a method of saving exactly what you have done, and works perfectly as it should..., but only for the first flight during the same mission/server.

 

I didn't test for the A-10, KA-50 and CA yet, but i will..., yet for Huey..., not a chance..., it will tell different stories than what you actually did even in the first start, no matter how many times have you restarted during the same mission..., so the huey has big trouble being recorded. Don't know why..., but P-51 works perfectly for the first flight, yet huey can't! Another thing that i've found about the huey's recording was that if your pilot dies..., and it will switch you automatically to your copilot (the left seat), the recording will make your huey act like being on autopilot and go straight, although you had control over it within the mission. This might be an issue because the autopilot function was active in the game's options, so the recorder "thought" that the copilot didn't have control, and this might also be from the fact that the sight was on, so normally when the sight is on and you switch to the copilot, the autopilot kicks in (if it's turned on), but not when the pilot is dead and this is what the recorder "forgot" about.

Edited July 26, 2013 by MaverickF22

[MaverickF22]

As a conclusion..., the only aircraft which can't be correctly recorded in the track file and which cannot show exactly what happened and when, no matter if you've just entered a single player mission and spawned only once (didn't press refly again) or on servers and did the same..., is the Belsimtek's DCS Huey!

 

For all other aircrafts (A-10's, FC3's aircrafts, Su-25T, KA-50, P-51) and Combined Arms..., the recorder will track exactly, with 0% errors, of everything that you did..., ONLY your first flight of a single player mission or from a server! The rest of the flights which you have started afterwards will be recorded with an alarmingly increasing error in that the aircraft might blow up in 2..3 seconds after it was re-spawned..., as you watch the track.

 

So this recording feature works only partially!

 

 

Once again..., let's hope that ED will do the job and correct all of these bugs/problems and don't forget about them, because we like to support a good quality simulator..., not any sort of computer game who nobody cares of...!

 

 

A good day to everyone!:thumbup: