Ithronwise

Hi ED Team, hi DCS pilots, since the DCS 2.5.6.57264 Open Beta update I am experiencing a slightly stuttering when I look around with my headtracking clip (DelanClip with PS3 Eye Camera and Opentrack). The game frame rate stays between 40 and 60 fps (it is locked at 60 fps) and DCS runs without any stutters even over the large towns at the Syria or the Persian Gulf map . But the head movement isn't fluent anymore. Especially when I turn my head slowly there is a permanently slightly stuttering (no frame rate decreasing). This destroys the immersion for me and wasn't definitely not existent before the update. I already deleted the fxo and metashaders2 folders and also cleaned and repaired the DCS installation. Do you have any hints for me? Are there other users with similar experiences? Best regards, Rene dcs.log

No it wasn't. My DRAM has a factory clock of 3000MHz. Before I upgraded it from 32GB to 64GB it ran with 3200MHz and 1.2V without any issues (all above 2666MHz is overclocking speed for my mainboard). After the upgrade it wasn't stable with this RAM clock and also with lower overclocking speed settings, even with 1.35V (Windows didn't start or crashed with bluescreens). I read that Ryzen processors don't like DRAM overclocking when all RAM banks are full, not sure if it's true. So I set the RAM to non-overclocking speed of 2666MHz with 1.2V. With this it was stable so it seemed. But maybe 1.2V is not enough for four 16GB DIMMs in some cases with high load. The GPU runs with undervolting.

Hi Flappie, yesterday I deactivated all third party mods (these were A-4E-C by Heclak, Su-57 by Cubanace and some liveries for different aircraft types), then I flew the syria mission and had no crash. Today I activated the mods again (except Su-57 because I had installed it only for testing), flew the Syria mission and also had no crash. But in both cases the mission duration was a little shorter than one hour. Not sure whether duration time could be a factor. What I did also yesterday was to increase the DRAM voltage from 1.2V (it was the auto setting in the BIOS) to 1.35V (the max. recommended voltage for my DRAM). I don't know whether to less DRAM voltage can cause such kind of crashes. I will keep it watching and testing. If this has solved my issue I will report to you. Thanks again for your help! Best regards, Rene

Hi Flappie, I disabled "Enhanced Sync" both at Global and DCS profile within the Radeon settings, deleted the fxo and the metashaders2 folders again, started the game, flew the same mission as before (Syria map, Su-33). More than 1 hour later I finished the mission by landing on the Kuznetsov with the last drop of fuel, folded the wings, rolled to the parking position and ... crash! Very frustrating. Attached you can find the dcs.log and the dxdiag.txt (the .trk file is to large for upload). Best regards, René dcs.20201031-100926.log dxdiag.txt

Here they are (the Radeon settings are in german, sorry for that). I will try the newest AMD driver tomorrow. Thanks for your help.

I have deleted the fxo and metashaders2 folder, upgraded my Windows 10 to version 20H2 (2004 wasn't offered anymore) but it crashed again, Su-33, Syria map, same mission.This time neither a .trk file nor a .crash file was written, only the dcs.log file (attached). It crashed to desktop without any error message. dcs.log

Hi Flappie, I will try. But normally I clean these both folders everytime I change something in the DCS or Radeon settings (also when I install a new graphics driver). Windows 10, yeah I know, I am a little paranoid with these upgrades because there is a lot of issue reports every time Microsoft is "blessing" us with one of these upgrades, so I do it so rarely as possible. But I also will do it and hopefully it will resolve this problem. Thank you very much for your fast help. Best regards, Rene

Hi ED team, for almost two weeks I am facing with sporadically crashes in DCS. The first one was after a long mission with the A-10C II at the NTTR map ten days ago, the second one in a Su-33 at the Syria map about one hour ago. After the first mission I checked the dcs.log and crash.log and found some issues with the graphics driver (access violation by atidxx64.dll). At this time i still used the old 19.12.1 AMD driver. So I changed to the new recommended driver (20.9.1). But also with this I had a crash for the same cause. Attached you can find the dcs.log and .trk file of this newest CTD. Hope you have some hints for solving this problem. Best Regards, Rene dcs.log dcs.20201030-153723.trk

It's definitely not the TGP. The track I attached on my first posting was without targeting pod, but with Mavs. I also think, that the bug is related to them.

I experienced this bug when I switch between A/G- or A/A- and NAV mode. Suddenly the distance to the chosen waypoint in the HUD increases (see trackfile, Nevada map is needed), as soon I switch back to NAV. The position of the waypoint also isn't correct anymore. F-16C Bug Waypoint Distance Tonopah NTTR 01.trk

Not only on the Syria and the Caucasus map, but also on the Persian Gulf (experienced in a F/A-18C) and NTTR (experienced in a Su-33 and a MiG-29S). The first time I saw this was just after the last major update. It happens every time there is an explosion / fire (on the ground or in the air) in the field of view.