[OK INTERNALLY] track replay unusable

[bbrz]

That's too bad. I did land on the runway but in the replay the Yak crashed onto the runway in a vertical dive :(

But at least the Yak handles very nicely apart from the really dangerous habit to pitch up with extended flaps when slowing down at low speed.

Edited August 3, 2018 by bbrz

[NineLine]

That's too bad. I did land on the runway but in the replay the Yak crashed onto the runway in a vertical dive :(

But at least the Yak handles very nicely apart from the really dangerous habit to pitch up with extended flaps when slowing down at low speed.

 

I just viewed on our internal version and its working, it may be that the fix for that isnt in the public version yet, also I know that not touching anything for a couple minutes on the start of the replay can help, don't change views or anything. After a couple of minutes you should be ok, but again, its possible its not fixed in the release version.

[bbrz]

Thanx for the HU :)

[bozflyer]

Yak-52 and Replays

 

Hi to all Airmen

 

I have some issue with the replay..

After aerobatics in any map, i watch the track immediately after the flight but it takes some strange behavior executing completely different thing and always crash down to ground.

This same behavior was present in early version of Spitfire too but now solved.

 

Any ideas to avoid all of this ? or i only must wait the beta release/final ?

 

Thank you very much

 

Paolo

[bbrz]

https://forums.eagle.ru/showthread.php?t=217322

[Nealius]

It's a shame really. With an aerobatic plane like this working track files would be a major part of making a virtual airshow.

[bbrz]

It's a shame really. With an aerobatic plane like this working track files would be a major part of making a virtual airshow.

?Have you read NineLine's post that this issue has been fixed internally already?

[Nealius]

?Have you read NineLine's post that this issue has been fixed internally already?

 

It's also possible that the tracks only work on their internal computers and not everyone else's computers, like the Spitfire or Viggen, which have had broken tracks since release.

[NineLine]

Tracks are always tricky, if you start changing views or fast forward too much you can get strange results. They aren't like a video recording, but a recording of the actions that took place, so things can change slightly even without doing anything like changing views.

[Nealius]

I understand that, however certain modules are more robust than others regardless of switching views or fastforwarding. I've been able to fastforward x4 and switch views countless times in the Hornet and a couple of other modules with no ill effects, for example.

[NineLine]

And I get that, I can view tracks no issue in most everything, then I will get a batch that dont view at all. Its pretty hit and miss. Its one of those things you almost report without even needing to check when a new module hits testing.

[bbrz]

It's also possible that the tracks only work on their internal computers and not everyone else's computers, like the Spitfire or Viggen, which have had broken tracks since release.

Since the last 2 betas I didn't have a single Viggen trk that didn't replay correctly :)

[Spinner3]

I have just tried you suggestions, but it didn't seem to help. Both the Spitfire and Yak are not relaying correctly for me and never make it back to the airfield in one peace.

[Nealius]

I can't even get the Yak to replay a taxi after startup :lol:

 

It just goes off into the grass.

[NineLine]

I was able to do both the Yak-52 and Spitfire, the Spitfire was a start up, take off, engine break and landing with no power, and it played back fine. Perhaps its partly based on specs too. I have a 1070, 32GB of ram and an i7-4790k, maybe that makes a difference.

Edited August 9, 2018 by NineLine

[Nealius]

I've always been curious how it may be effected by systems. DCS has never maxed out my RAM, ever, so I wonder if CPU affects replay tracks.