Ithronwise

Besides of the colours this glitch is similar to the glitch in this topic: There are also very short flashes in wrong colours. Do you think it also is caused by a failing GPU? Unfortunately turn of automatic undervolting didn't help.

Hi Flappie, attached you can find the dcs.log. @Taz1004 currently my card runs with automatic undervolting. I could try to turn it off. But when my card is failing, why I only see this glitch in situations when an aircraft/helo starts to burn (on the ground/in the air doesn't no matter)? A burning truck, house, ship whatsoever never causes this glitch. And also in other games I don't have any glitches or other graphics issues. Best regards, Rene dcs.log

Hi Flappie, I don't have a NVIDIA card but an AMD card (RX5700 XT). Is there a similar folder for AMD? Best regards, Rene UPDATE: I have resetted the shader cache in the AMD Radeon settings (Global settings -> Reset -> Shader cache) but it didn't help.

Hi Flappie, I see the same glitch in your track. I disabled all mods, executed a cleanup and a repair including the options "Check all files (slow)" and "Search for extra files after repair" and I also deleted the fxo and metashaders2 folders, but without result. The glitch is still there (see pictures, captured from your track). The strange thing is, that the glitch is sometimes there, sometimes not or the intensity of it is different when I run the track. For example, the both glitches in picture 1 and 2 appeared only in a few number of track run-throughs, but the glitch in picture 3 appeared in every single run-through, sometimes more intense sometimes less. Best regards, Rene

Hi, I just found this bug in the rendering of the F-14B Jolly Rogers Livery (Is it know already?). The right side of the Tomcat is black (or very dark grey). If I zoom out, then it looks normal. Map was Syria. Best regards, Rene

In my opinion this issue is similar or identical to the glitch I found (besides of the colours): It happens almost every times when an air target is hit, no matter if it is on the ground or in the air. Ground objects/units or ships are not affected (at least from my expierence). It is not related to: - the new damage model for WWII (I only fly modern aircrafts) - the type of aircraft/helo (flown or hit) - the map (I see this on Caucasus, Nevada, Syria and Persian Gulf map) - the distance to the target - the angle of view - the view position (internal, external, ...) - the graphics card (Nvidia and AMD are both affected) - the version of the graphics driver I think it is caused by the rendering of the fire, flames and smoketrails of hit planes and helos, which was improved by ED several months ago. Since this update I expierence this issue. In the first months the colours were also red, yellow, orange (but also black or grey in some cases). Now I only see these black and blue (sometimes also white or grey) glitches.

Hi Flappie, hi Bignewy, here is an update to the issue I found. Attached you can find a track with a lot of black flickering (CBU-97 hittings, APKWS hittings, GAU-8 hittings). There are also some screenshots captured from a video of the same mission. The flickering appears only when I hit the Mi-8's on the ground. Hitting the fuel trucks with APKWS and GAU-8 doesn't cause the issue. For me it seems to be related to the flames of the helos. It's just a test mission to demonstrate the issue, so don't judge my flight performance too harshly. Best regards, Rene Black and blue flickering.trk

Hi Kevstosmart, sorry for my late answer. I didn't change back to an older driver. I used the 19.12.1 Radeon driver for a long time. After I ran into the described issue I tried the 20.9.1 WHQL driver but with the old Radeon GUI (not these Adrenalin GUI crap) because I need the Frame Rate Target Control setting, which isn't present in the Adrenalin GUI anymore although the function is still existing within the drivers. With the 20.9.1 driver and the increasing of the DRAM voltage the crashes are completely gone. I didn't try the newest WHQL driver (20.11.2) yet, You know, never change a running system. Best regards, Rene

Hi Flappie, actually, when this thread came up I had the same orange and yellow flashes like described, together with these black flickering. The orange flashes where gone sometime (maybe because of a DCS or a graphics driver update), but the black and grey flickering stayed. If you say that's two different glitches, then I am glad if my track can help to fix it. Thanks to Bignewy for opening a new thread. Best regards, Rene

Hi Bignewy, hi Flappie, I flew a test flight in an F-15C on the Caucasus map to demonstrate the graphical glitch (track attached). There is black and partly light grey flickering after the Su-24's are hit and going down. It seems it is caused by the smoke trails (black and light grey). Best regards, Rene Testflight Graphic glitches F-15C Caucasus.trk

Hi Jim, thanks for the hint, but Enhanced sync on or off doesn't make any difference (I already tested it and tested it again now). I am using Enhanced sync for a long time and never had problems with it in DCS. I am experiencing the described slightly stuttering during head moving only since the DCS 2.5.6.57264 Open Beta update. Best regards, Rene

The only WWII module I own is P-51D (but fly it very rarely). I see the same flickering in modern aircraft modules like F/A-18C, F-15C, F-16C, Su-33, MiG-29, Mirage 2000C and so on. I don't have a NVIDIA graphics card but an AMD card with the latest recommended driver. I saw this flickering already with the old 19.12.1 driver (maybe a little heavier), for the very first time at the beginning of September this year.

Hi Flappie, I see a black flickering at the beginning of the track (short after some of the planes have crashed into the ground), which only affects the sky (means, the whole sky from the horizon upwards is flickering black for about one or two seconds). I see another flickering (grey in this case) when your plane flies through the smoke columns, but this flickering effects the whole cockpit (or even the whole field of view). Best regards, Rene

Hi BIGNEWY, all my relevant tracks they could show the issue are corrupt, what means, if I replaying them I am flying like an idiot and crashing into ground (nothing of this happened during the real flight). If ED wants us to send tracks to investigate issues, the tracking system should be fixed urgently. Best regards, Rene

Grahpics Card: Sapphire Radeon 5700XT Nitro+ SE Graphics Driver: Adrenalin 2020 Edition 20.9.1 (Recommended by AMD) I see this glitch only in correlation with explosions of aircrafts (missile hits, crash into the ground) even if the target aircraft is hitted or crashing BVR. Sometimes it's a yellow flashing, sometimes a gray/black flashing, probably caused by a corrupt rendering of explosions, flames and smoke trails of the hitted/crashing aircraft. I guess it came together with the rendering improvements of fire and smoke. I will try to upload a track if I find one which isn't too large.

Hi Flappie, just for your information. The last two weeks I flew several missions in different aircrafts (A-10C-II, AV-8B, F-15C, F-16C, F/A-18C, Su-33) with mission durations between 45 and 90 minutes without any further CTDs. It seems the solution for my issue was a mix of graphic drivers update and DRAM voltage increasing. Best regards, Rene

The same as mine. Just a slight stuttering and only during head movements without any impact to the frame rate. The stuttering in the video of Guppy is very heavy.

Here there are two tracks they (hopefully) show the issue. The first one (F-16C Caucasus) shows the slightly stuttering by using DelanClip headtracker. The second one (F-15C Nevada) shows heavily stutters by using the mouse for view steering. In the first case the frame rate is between 60 fps and 41 fps (over large forestry areas) without any stuttering as long I look straight ahead or to the side without head moving (in flight). As soon I move my head there is a slightly stuttering without any impact to the frame rate. In the second case the frame rate is rock solid at 60 fps. As soon I move the mouse there are heavily stutters also without any impact to the frame rate. F-16C Caucasus Stuttering with Headtracking.trk F-15C Nevada Stuttering with View steering by Mouse.trk

Hi twistking, thank you for your tips. (Ingame-)Vsync wasn't active but Enhanced sync within the AMD Radeon settings was enabled. I tested DCS without this (deleted fxo and metashaders2 folders before), but unfortunately it didn't help. Fullscreen already is enabled in DCS and in Radeon settings and I also disabled the Windows fullscreen optimization for the dcs.exe several months ago. I am experiencing this slighty stuttering only since the latest update. I changed nothing else on my system or in DCS. EDIT: And another interesting observation. When I deactivate headtracking and I use the mouse instead for view steering, it also stutters (much worser than with headtracking), but only within the cockpit. The steering of the external view by mouse is absolutely fluently. Best regards, Rene

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