Jump to content

Recommended Posts

Posted

Alright, so in the 1.5.2 patch notes, I saw that there was a fix for "Memory Leaks". Correct me if I'm wrong (I'm new to DCS), but I instantly thought of this as a fix for the replay tracks being inaccurate and generally different from what they're supposed to show- a problem that has plagued DCS since quite a lot of time.

So I flew out my Su-25, killed about 8 ground targets in a custom mission and when I ran dry I RTB'd safely.

When I viewed my replay track, there I had it again: my aircraft got shot down by AAA after I'd killed, like, 3 transport vehicles.

Even if the "memory leaks" fix didn't have this problem in context, I simply don't understand how and why such a persisting problem hasn't been dealt with yet. If it did, I don't really know- was this a one-off occurrence for me?

Posted

Don't hold your breath.

 

Tracks are a registering of the inputs that were made (your inputs, other players inputs, AI inputs).

With this list of inputs (= track), DCS re-plays the actions (and if everything else is equal, then you should get the same output).

 

Problem such as the one you described is that everything else is not always equal:

- reaction of an aircraft to this or that input may vary (flight model adjustment)

- random factors will be recalculated, with possible different outcomes

- lags/performance glitches may cause discrepancies

- ...etc.

 

This is linked to the nature of the track.

If tracks were a registering of what happened (and not only of what commands/inputs were made) then:

+ you would be able to read them forward or backward

+ there would be no such problem as the one you described

but

- you would loose the ability to take control (for a different view, or even to fly differently by acting on the controls)

- tracks would likely weigh more.

spacer.png

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...