1.5.7 to 1.5.8 and back track inconsistencies

[WytchCrypt]

Hi all,

 

I wanted to try the new 1.5.8 beta because I read that it fixed a problem with the Su33 airbrake indicator lamp. I opened a command window and ran, "DCS_updater.exe update 1.5.8.12162.404 openbeta" and it updated as expected. I tested and it indeed did fix the Su33 airbrake indicator lamp issue; however, it introduced some odd problems into track recording. I decided openbeta isn't for me and reverted to the previous stable release by running, "DCS_updater.exe update 1.5.7.11762.396" and it updated as expected.

 

All good, except now many of the track files I originally created before testing the 1.5.8 openbeta now playback incorrectly! It seems to be restricted to my "carrier qual" missions where I take off from a land base and land on the Kuznetsov. On the replays, I consistently ditch in the water about 10 meters to the left of the carrier instead of making a clean landing on the deck as originally recorded. Oddly enough, the track recordings of my "carrier qual" missions that do not involve taking off from a land base are still perfectly correct.

 

Has anyone experienced anything like this? It doesn't make any sense why the mission recordings originally made on the stable 1.5.7 of late September 2017 would no longer playback correctly on the stable 1.5.7 of early December. Was there a significant change between them that might account for a few meters difference in land base location or something?

 

Thanks!

[Art-J]

Mind you, there were five sub-version updates of 1.5.7 between September and December. Even smallest FM change made to Su-33 in either of them is enough to throw off the track, given the method of recording used by DCS. Actually, with the shoddy reliability of replay engine, consider yourself lucky if tracks run OK on the very same version anyway :D. By definition, you should not expect DCS tracks to work correctly for the time being.

 

You might try experimenting with rollback to any of these sub-versions and see if it helps, but you will want to update the game at some point in the future anyway.

[WytchCrypt]

Thanks Art-J, makes sense, I had a feeling it was something like this :smilewink:

 

It's really bizarre though, any mission that begins in the air or on the carrier replays accurately, any that begin on land end up a few meters off the carrier for landing...oops, I should say splashdown!

 

Anyway, you mention not expecting tracks to work at this time. Is there an effort to tighten up the track creation and playback processes in the future?

[Art-J]

We've been told months ago that ED are aware, but track desync problem reasons are too complicated for a quick fix. No more news on the subject that I'm aware of.

 

Reliability of tracks is plane-, mission- and hardware dependent, so some of them will play just fine, while the others will go bonkers almost immediately. Expect anything :D.

[WytchCrypt]

Got it :smilewink:

 

I find it interesting that all the years I flew LOMAC (and Flanker 2.5, 2.0 & DOS versions before that) I never recall a single time my recorded track file played back incorrectly...not once. Then again, DCS certainly appears to be much more complex as far as the number of objects that can be moving around, not to mention the triggered events that can effect the outcome of a track so I guess track inconsistencies are somewhat inevitable :unsure: