Jump to content

Recommended Posts

Posted

Playing the same track file provide different results/outcome in the missions.

Now let’s start from the beginning:

I was playing a small SP mission training SA8 evasion on the Syrian map. (attached: TestMovingTG.miz)

And after 00:06:38 of playing I experienced the following graphical bug (see Pic)

Link to short video of BUG: https://streamable.com/z1ujih

GreanBlackSpot.jpg

So, I ended the game, exit DCS and made a copy of track and log + a copy of the Tacview file for bug reporting: (Attached: BlackGreen.trk  + As_Played_dcs.log + As_played_Tacview.acmi).

Now before reporting this “graphical bug”, I decided to see if I could reproduce, so this morning, I did the following:

Emptying fxo-  Tracks- and the logs- folders. Copied my original backup of BlackGreen.trk  to the Tracks folder, Disconnected my joystick and throttle. Opened DCS 2_7 stable then replayed BlackGreen.trk.

This time the replay mission only lasted for 00:06:29 min and this time I got hit by the SAM´s. Last night I survived the SAM´s (remember this is a replay of a mission so the outcome should be the same).

Attached file from first replay are 01_replay_org_dcs.log + 01_replay_org_Tacview.acmi

Last night I evaded the SAM´s and now in the first replay I got hit weird !!

Just to test if I was missing something, I decided to go for one more try with the replay. So, I exit DCS deleted the BlackGreen.trk in the DCS folder and the log´s.

Copied my original backup of BlackGreen.trk to DCS mission folder, run DCS run Replay to see what happened this time:

The result is that I Crash/fly in to ground after 00:05:39 min  

Attached files from the second replay: 2_replay_dcs.log + 2_replay_Tacview.acmi + 2_replay_BlackGreenGroundImpact.trk.

So, until now I have not been able to reproduce the “graphical bug”, because DCS replay function changes the outcome and the length of a mission every time I replay this track.

As_Played_dcs.log As_played_Tacview.acmi 2_replay_Tacview.acmi 2_replay_BlackGreenGroundImpact.trk 2_replay_dcs.log 01_replay_org_Tacview.acmi 01_replay_org_dcs.log TestMovingTG.miz

  • Thanks 1
Posted

This is a known issue with DCS track files

Windows 11 Home ¦ Z790 AORUS Elite AX motherboard ¦ i7-13700K ¦ 64GB Corsair Vengeance DDR5 memory @ 5600MHz ¦ Samsung 990 Pro 1TB SSD for OS, Samsung 980 Pro 2TB SSD for DCS ¦ MSI GeForce RTX 4090 Gaming X Trio 24GB ¦ Virpil WarBRD base with VFX grip, Thrustmaster A10c and F/A-18 grips ¦ VKB Gunfighter Mk4 and MCG Pro ¦ Thrustmaster Warthog Throttle ¦ VKB STECS Throttle ¦ Virpil TCS rotor base with Shark and AH-64D  grips ¦ MFG Crosswinds ¦ Total Controls Multi-Function Button Box ¦ Pimax Crystal

Posted

It does help sometimes - generally shorter tracks work better

  • Like 1

Windows 11 Home ¦ Z790 AORUS Elite AX motherboard ¦ i7-13700K ¦ 64GB Corsair Vengeance DDR5 memory @ 5600MHz ¦ Samsung 990 Pro 1TB SSD for OS, Samsung 980 Pro 2TB SSD for DCS ¦ MSI GeForce RTX 4090 Gaming X Trio 24GB ¦ Virpil WarBRD base with VFX grip, Thrustmaster A10c and F/A-18 grips ¦ VKB Gunfighter Mk4 and MCG Pro ¦ Thrustmaster Warthog Throttle ¦ VKB STECS Throttle ¦ Virpil TCS rotor base with Shark and AH-64D  grips ¦ MFG Crosswinds ¦ Total Controls Multi-Function Button Box ¦ Pimax Crystal

Posted (edited)

hi

 

i already made a thread for this "green/black" bug, please add future posts here:

 

in regards to trackfile inaccuracy: yes, they detoriate quickly. anything more than 15 minutes of flight is a gamble. if youre dodging missiles and cannons, then the outcome is entirely random each time, because even tiniest difference in positioning will cause very different outcome.

Edited by dorianR666

CPU: AMD Ryzen 5 1600X

GPU: AMD RX 580

  • Recently Browsing   0 members

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