Ithronwise

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.