Reolay lost.

[zero]

Replay worked fine during my first flights.

Fresh from the box - with no adjustments.

 

Now it is heavily bugged.

 

Tried to reset my joystick axis back original (No curve)

Renamed and build new config files.

 

But replay is still bugged.

Where is the culprit hidden?

:helpsmilie:

Edited December 26, 2017 by zero

[razo+r]

Tracks are inaccurate.

 

If you want to improve their reliability, Try to not fully extend the joystick to the maximum but always leave a bit space. But this won't fix the problem.

[zero]

Thanks.

Guess my first flights was hot from runway.

Now I start cold at ramp.

Probably taxing generates errors.

[razo+r]

It's not just taxiing that generates error.

 

It just records the stick input. And since they can't get 100% accurate recorded, it will create a small error, which will grow over time...

[zero]

Why just Viggen?

Other planes such as F-5 and Mirage is OK.

[razo+r]

Since it is a bug in DCS, all planes are affected.

[MBot]

Since it is a bug in DCS, all planes are affected.

 

That is not correct, this is a problem specifically about the Viggen. Tracks for other aircraft play back correctly.

[QuiGon]

That is not correct, this is a problem specifically about the Viggen. Tracks for other aircraft play back correctly.

That's not true. It is indeed a general (and known) DCS wide problem that can occur in every replay. The longer the replay is and the faster you play it, the more likely are inaccuracies. That is because DCS just records the control inputs and when the replay is played it will just start a new flight and automatically applies the recorded inputs the player made during recording. That can lead to inaccuraccies and can result in totally different outcomes.

 

Just do a quick forum search about bugged replays and you will find quite a lot about this issue ;)

Known issue, track replays are unreliable especially for long MP tracks

[razo+r]

That is not correct, this is a problem specifically about the Viggen. Tracks for other aircraft play back correctly.

 

Nope. F-5, Fw-190 and Bf-109 are also affected on my side. Don't know about others as I don't fly other planes.

[MBot]

Nope. F-5, Fw-190 and Bf-109 are also affected on my side. Don't know about others as I don't fly other planes.

 

I can't comment on the Fw-190 and Bf-109, but have recently played tracks flying the F-5E, the Su-33, the Gazelle and the AV-8B and they all worked flawless.

[QuiGon]

I can't comment on the Fw-190 and Bf-109, but have recently played tracks flying the F-5E, the Su-33, the Gazelle and the AV-8B and they all worked flawless.

Like I said, the chance that replays get corrupted increases with length of play time and speed of playing (fast forwarding). The amount of active units might also affect it, but I'm not sure about that one.

[MBot]

That's not true. It is indeed a general (and known) DCS wide problem that can occur in every replay. The longer the replay is and the faster you play it, the more likely are inaccuracies. That is because DCS just records the control inputs and when the replay is played it will just start a new flight and automatically applies the recorded inputs the player made during recording. That can lead to inaccuraccies and can result in totally different outcomes.

 

Just do a quick forum search about bugged replays and you will find quite a lot about this issue ;)

 

While the reliability of tracks the longer they run is a known issue, the problem with the Viggen is completely different. Tracks playing the Viggen consistently result in the aircraft crashing within seconds to minutes. On the other hand I have recorded tracks of half an hour with precision flying, including bomb deliveries, air-air refueling and carrier landings which consistently replay perfectly. There is clearly something wrong specifically with the Viggen. You can't record a track with the Viggen flying a simple circuit without crashing. Go ahead and try it.

[razo+r]

While the reliability of tracks the longer they run is a known issue, the problem with the Viggen is completely different. Tracks playing the Viggen consistently result in the aircraft crashing within seconds to minutes. On the other hand I have recorded tracks of half an hour with precision flying, including bomb deliveries, air-air refueling and carrier landings which consistently replay perfectly. There is clearly something wrong specifically with the Viggen. You can't record a track with the Viggen flying a simple circuit without crashing. Go ahead and try it.

 

There were instances where it worked, but those were rare moments.

 

My F-5 is usually as Inaccurate as the Viggen. So it's not only the Viggen which is bad.

 

Do you have by any chances curves/deadzones on the F-5 that you don't have on the Viggen? As I once saw, it makes a difference in the replays having curves in the settings and when you don't.

[probad]

so far for me "ranging" the stick inputs by running it through max inputs on all axis at any point in the mission helps.

[TOViper]

so far for me "ranging" the stick inputs by running it through max inputs on all axis at any point in the mission helps.

 

did I get you right if I say in other words:

It might help when I - lets say during preliminary cockpit preparation - put the stick to full deflections in all directions, like during rudder-check?

 

This check - indeed - should be done before all flights, but as you know on the sim we are often not doing it because we are just trying out things and so on ... :huh:

[MBot]

To reinforce the point, I have just now flown two quick circuits with the F-5E and Viggen at Groom Lake. Small and smooth control inputs, no curvatures applied. The tracks are attached. The F-5E track replays fine. In the Viggen track, the aircraft crashes next to the runway.

 

Edit: There is an interesting difference in track file size for two tracks which basically show the same thing.

Edited December 27, 2017 by MBot

[TOViper]

... Edit: There is an interesting difference in track file size for two tracks which basically show the same thing.

 

The Viggen has less rudders > less data .... ;-)

[QuiGon]

While the reliability of tracks the longer they run is a known issue, the problem with the Viggen is completely different. Tracks playing the Viggen consistently result in the aircraft crashing within seconds to minutes. On the other hand I have recorded tracks of half an hour with precision flying, including bomb deliveries, air-air refueling and carrier landings which consistently replay perfectly. There is clearly something wrong specifically with the Viggen. You can't record a track with the Viggen flying a simple circuit without crashing. Go ahead and try it.

 

Alright, thanks for the explanation. Now I understand what you mean and that is indeed a bit different than the common unreliability of tracks.

[zero]

As part of troubleshooting - I did not set RADAR mode to NAV until lined up on runway. According to procedure this will calibrate compass heading.

 

It did not help. Stuck on grass after a few meters of taxing.