solved Different Screen Flickering Bug

[CRAZYZOMBITZ]

Hello, I have seen the other post about screen flickering however I believe I'm experiencing a different bug altogether. When I play any DCS F14B mission, my screen will start to flicker, and it slowly gets worse the more I play. Its a fast flicker that begins at the edges of my screen, which gets progressively worse making the entire screen flicker. It only happens with the F14B, (I own the F16, F18, and AV8B aswell and have not experienced this with those aircraft). However after I play a mission with the F14, the loading screens will start to flicker aswell (which they don't when I initially start the game). I've tried deleting the DCS.openbeta folder in my C:\Users\USER\Saved Games folder and I've completely uninstalled and re installed the entire game (and modules) to no avail. The flickering also doesn't show up on screen recordings, and I have an error code 31 with my microsoft basic display adapter, which I am also trying to figure out with their support, but I believe it to be unrelated.

my pc specs are:

RTX 3070

Ryzen 7 7700x

32 GB DDR5 RAM

and my c drive is a WD black NVMe (which is what the game is installed on).

Any help would be greatly appreciated!

[Flappie]

Hi. I'm pretty sure the F-14 alone is not responsible for your issue (otherwise the forum would be filled with threads about such an issue). However, the F-14 being highly detailed, maybe it's a matter of PC resources.

You should monitor your PC while flying the F-16C (for instance), then do the same thing while flying the F-14. See how RAM, VRAM, CPU and GPU are doing for each aircraft. This might help you find what is the source of the flickering.

Oh, and just in case, add DCS main path as an exception to your antivirus.

[CRAZYZOMBITZ]

I monitored my pc while flying the F14 and F16, and the system load looks identical. CPU usage maxes at like 25% (its only really using 3 cores out of the 8), GPU usage is pretty much at a constant 100% and memory maxes at 50% usage. I also figured out the issue causing a code 31 with the microsoft display driver, which hasn't fixed this issue.

[CRAZYZOMBITZ]

I also watched my VRAM and I believe it might be a video memory leak causing the issue. For reference my card has 8GB VRAM. When I first start the game my VRAM usage sits around ~1.3GB's, and when I load into a mission with the F14, the full 8GB is used. When I exit the mission into the main menu however, the VRAM usage sits around ~4.5GB.

dcs.log also heres my dcs.log

[Flappie]

Thanks. Your Windows has a small pagefile. Let's see if your issue disappears with a bigger one. Try this: https://mcci.com/support/guides/how-to-change-the-windows-pagefile-size/

Init size: 32768

Max size: 32768

Ensure you have at least 50 GB of free space on your pagefile drive beforehand.

[CRAZYZOMBITZ]

Unfortunately that hasn't fixed the problem.

heres another ddcs.logcs.log where it was flickering really bad.

EDIT: I added a track of a mission where I experienced flickering, although I don't believe it'll help as after that mission my loading screens started to flicker aswell.

flicker track.trk

Edited February 21, 2023 by CRAZYZOMBITZ

[Flappie]

One of your device was disconnected @3m50s into the mission:

023-02-21 21:08:51.288 INFO    Dispatcher (Main): loadMission Done: Сontrol passed to the player
2023-02-21 21:08:51.298 INFO    GRAPHICSVISTA (Main): Creating Resource "Unicode" of type 1
2023-02-21 21:09:06.939 INFO    LUA (Main): Lua CPU usage: metric: average mission execution: 0.3333 %
2023-02-21 21:09:08.178 INFO    APP (Main): Screen: Settings
2023-02-21 21:09:12.260 INFO    LUA (Main): Lua CPU usage: metric: average mission execution: 0.6142 %
2023-02-21 21:12:42.621 INFO    APP (Main): Device unplugged: \\?\SWD#DAFUPnPProvider#uuid:b096b470-861e-5358-b47b-8c965d73bf00#{2a323d9d-edf1-430b-ab95-5860894493d4}
2023-02-21 21:12:42.827 INFO    APP (Main): Device unplugged: \\?\SWD#DAFUPnPProvider#uuid:b096b470-861e-5358-b47b-8c965d73bf00#{ac4630a5-0b64-46e5-981b-12535fc1f5de}
2023-02-21 21:12:43.061 INFO    APP (Main): Device unplugged: \\?\SWD#DAFUPnPProvider#uuid:b096b470-861e-5358-b47b-8c965d73bf00#{1dc7cf2a-9167-5887-b1b2-16e04384f64c}
2023-02-21 21:12:43.288 INFO    APP (Main): Device unplugged: \\?\SWD#DAFUPnPProvider#uuid:717de83d-3dde-9da3-e858-6374431560cf#{2a323d9d-edf1-430b-ab95-5860894493d4}
2023-02-21 21:12:43.489 INFO    APP (Main): Device unplugged: \\?\SWD#DAFUPnPProvider#uuid:717de83d-3dde-9da3-e858-6374431560cf#{ac4630a5-0b64-46e5-981b-12535fc1f5de}
2023-02-21 21:12:43.734 INFO    APP (Main): Device unplugged: \\?\SWD#DAFUPnPProvider#uuid:717de83d-3dde-9da3-e858-6374431560cf#{1dc7cf2a-9167-5887-b1b2-16e04384f64c}
2023-02-21 21:12:43.939 INFO    APP (Main): Device unplugged: \\?\SWD#DAFUPnPProvider#uuid:bf66b062-72da-4005-cfb7-967b43788e00#{2a323d9d-edf1-430b-ab95-5860894493d4}
2023-02-21 21:12:44.148 INFO    APP (Main): Device unplugged: \\?\SWD#DAFUPnPProvider#uuid:bf66b062-72da-4005-cfb7-967b43788e00#{ac4630a5-0b64-46e5-981b-12535fc1f5de}
2023-02-21 21:12:44.352 INFO    APP (Main): Device unplugged: \\?\SWD#DAFUPnPProvider#uuid:bf66b062-72da-4005-cfb7-967b43788e00#{1dc7cf2a-9167-5887-b1b2-16e04384f64c}
2023-02-21 21:16:10.456 ERROR   ED_SOUND (Main): invalid source_params(F14_PILOT_COCKPIT:aircrafts/f-14/touchdown): gain
2023-02-21 21:16:10.485 WARNING LOG (8536): 1 duplicate message(s) skipped.
2023-02-21 21:16:10.485 ERROR   ED_SOUND (Main): invalid source_params(F14_PILOT_COCKPIT:aircrafts/f-14/groundroll): gain
2023-02-21 21:16:10.674 ERROR   ED_SOUND (Main): invalid source_params(F14_PILOT_COCKPIT:aircrafts/f-14/touchdown): gain
2023-02-21 21:16:35.208 ERROR   ED_SOUND (Main): invalid source_params(woLA-16777728:aircrafts/engines/rearclosehighpower): gain
2023-02-21 21:16:36.529 ERROR   ED_SOUND (Main): invalid source_params(woLA-16777728:aircrafts/engines/afterburnerrearclose): gain
2023-02-21 21:16:36.529 ERROR   ED_SOUND (Main): invalid source_params(woLA-16777728:aircrafts/engines/heavy_rear_afterburner_crackle): gain
2023-02-21 21:16:36.529 ERROR   ED_SOUND (Main): invalid source_params(woLA-16777728:aircrafts/engines/afterburnerrearclose): gain
2023-02-21 21:16:39.931 ERROR   ED_SOUND (Main): invalid source_params(F14_PILOT_COCKPIT:foley/damage_impact): gain
2023-02-21 21:16:39.948 ERROR   ED_SOUND (Main): invalid source_params(F14_PILOT_COCKPIT:foley/damage_missileimpact): gain
2023-02-21 21:19:42.757 INFO    LUA (Main): Lua CPU usage: metric: average mission execution: 0.3973 %
2023-02-21 21:19:44.215 INFO    Dispatcher (Main): Stop

 

Was it the moment the issue started showing up?

I see you have SSAA enabld in your graphic options. Does the issue persist if you disable SSAA?

You said the screen flickers don't show up in screen recordings. That would mean the monitor alone does this. What is your monitor model?

[CRAZYZOMBITZ]

 

50 minutes ago, Flappie said:

Was it the moment the issue started showing up?

it might have been

50 minutes ago, Flappie said:

I see you have SSAA enabld in your graphic options. Does the issue persist if you disable SSAA?

I'll have to check

50 minutes ago, Flappie said:

You said the screen flickers don't show up in screen recordings. That would mean the monitor alone does this. What is your monitor model?

its an LG 27GL63T and I have GSYNC enabled

 

also it might be unrelated but I had a crash while attempting to load an empty mission with the F14A

dcs.log this is the log from that

 

also is there any way to tell what device unplugged?

Edited February 21, 2023 by CRAZYZOMBITZ

[Flappie]

45 minutes ago, CRAZYZOMBITZ said:

also is there any way to tell what device unplugged?

I used this software once for my job: https://www.nirsoft.net/utils/usb_log_view.html

It worked very well.

47 minutes ago, CRAZYZOMBITZ said:

also it might be unrelated but I had a crash while attempting to load an empty mission with the F14A

dcs.log this is the log from that

Your log doesn't shows the crash. It was probably an eternal freeze, which means no clue in the log file unfortunately.

I've just found someone's thread about what looks like the exact same issue. You should definitely talk to the guy:

 

Another one disabled G-Sync and the issue was gone:

 

You might have something conflicting with G-Sync.

[CRAZYZOMBITZ]

I disabled G sync, and ssaa aswell as disabling hot plugs and changing my settings in nvidia control panel to the settings in the post. I have re enabled G sync and ssaa with no issues, so my guess is it was either a bad nvidia control panel setting messing with something, or the hot plugs issue, or both. Either way the issue is fixed! Thanks!

[Flappie]

Great! Thanks for your feedback.