fixed Screen Flickering Since 2.9 Update

[Flappie]

Please create a new thread and attach to it:

• A DCS track
• Your options.lua (from Saved Games/DCS.../Config)
• Your dcs.log (from Saved Games/DCS.../Logs)

[Jazzadanub]

Hi,

Since I bought the Kola Map, things have gone a bit weird in my VR with crazy flashing and the water on all maps doing this (please see attached link to Youtube video). Before the Kola Map things were fine.

Unusual VR graphics behaviour since Kola Map purchase

Could really use some assistance with this, hope I have posted it to the right place

dcs.log DxDiag.txt

options.lua

Edited May 13, 2024 by Jazzadanub
Adding extra file

[BIGNEWY]

Hi, 

that looks very strange, first thing I would do is make sure the card is seated correctly, and check with fresh driver install.

 

[Jazzadanub]

34 minutes ago, BIGNEWY said:

Hi, 

that looks very strange, first thing I would do is make sure the card is seated correctly, and check with fresh driver install.

 

Hi Bignewy,

Yes strange indeed. I checked the GPU and its seated correctly, and I just installed the latest NVIDIA drivers before I took the video.

I have also deleted the fxo and metashaders2 folders.

Weirdly someone posted here with what seems a similar issue:

 

Edited May 13, 2024 by Jazzadanub

[BIGNEWY]

I've merged your post with the main thread so we can look for common clues. 

Personally not seen it in 2.9. 

I've just updated my NVIDIA driver to 552.44

[Jazzadanub]

On 5/12/2024 at 5:52 PM, Cheese16 said:

So I've never had this issue previously but it just started after the last Kola release update. It only seems to effect modules with MFDs though? I'd need to test it a bit more but the F18 and A10 are basically unusable now, P51 doesn't appear to be effected. Doesn't happen on the main menu but it does happen while paused in a mission. 

Can you look at my post and see if your's is doing what mine is.

[Jazzadanub]

19 hours ago, BIGNEWY said:

I've merged your post with the main thread so we can look for common clues. 

Personally not seen it in 2.9. 

I've just updated my NVIDIA driver to 552.44

Hi Bignewy,

Got any suggestions on something else I can try. Did a clean reinstall on the NVIDIA drivers, rechecked the GPU seating and I stress tested the GPU and there were no issues. Tried the graphic settings in game on lowest, does exactly the same thing. Tried in 2D, also the same results.

I am going to try rolling back to a restore point before the map purchase to see if does anything.

[BIGNEWY]

13 minutes ago, Jazzadanub said:

Hi Bignewy,

Got any suggestions on something else I can try. Did a clean reinstall on the NVIDIA drivers, rechecked the GPU seating and I stress tested the GPU and there were no issues. Tried the graphic settings in game on lowest, does exactly the same thing. Tried in 2D, also the same results.

I am going to try rolling back to a restore point before the map purchase to see if does anything.

If you can reproduce the issue easily please make a short as possible track replay example. We can all try to replicate then. 

thank you 

[Jazzadanub]

31 minutes ago, BIGNEWY said:

If you can reproduce the issue easily please make a short as possible track replay example. We can all try to replicate then. 

thank you 

Here is the track replay I think this is what you are after. But of a noob here When I replayed it just then it was flashing and carrying on. Restore point did nothing.

Pretense_Frontlines_Kola_5am-20240513-222607.trk

Edited May 14, 2024 by Jazzadanub

[BIGNEWY]

2 minutes ago, Jazzadanub said:

Here is the track replay I think this is what you are after. But of a noob here When I replayed it just then it was flashing and carrying on. Restore point did nothing.

Pretense_Frontlines_Kola_5am-20240513-222607.trk 8.32 MB · 0 downloads

 

thank you

[BIGNEWY]

19 minutes ago, Jazzadanub said:

Here is the track replay I think this is what you are after. But of a noob here When I replayed it just then it was flashing and carrying on. Restore point did nothing.

Pretense_Frontlines_Kola_5am-20240513-222607.trk 8.32 MB · 2 downloads

 

I could not reproduce with this track, all seems normal on my end. 

Can you do another but in single player, just with the aircraft and the terrain, If you can reproduce on a much smaller track it will be easier to ask others to reproduce. 

[Jazzadanub]

28 minutes ago, BIGNEWY said:

I could not reproduce with this track, all seems normal on my end. 

Can you do another but in single player, just with the aircraft and the terrain, If you can reproduce on a much smaller track it will be easier to ask others to reproduce. 

Is this long enough? I recorded it as well and this is how it looks on my screen Kola_test

Funny thing, I've had a look at a couple of track files back in late April and they look ok, no flickering. But my first track file in May has it.

Kola_test.trk

[BIGNEWY]

Thanks, can I ask you to try something. 

go to your saved games dcs folder, go to the config folder, and remove your options.lua ( keep it as a back up on your desktop for example )

Then restart DCS and redo your graphics option and test again. 

 

[BIGNEWY]

can you screenshot your NVIDIA control panel settings also.  

thanks

[draconus]

33 minutes ago, Jazzadanub said:

I recorded it as well and this is how it looks on my screen Kola_test

Looks like bad memory or GPU overclock but you have also lots of mods running. Try to rename the whole C:\Users\Jazza\Saved Games\DCS folder to DCS.bak and try again.

[Jazzadanub]

1 hour ago, BIGNEWY said:

can you screenshot your NVIDIA control panel settings also.  

thanks

So I tried the options.lua and it didnt make a difference. I will try what Draconus suggested next

[Jazzadanub]

1 hour ago, draconus said:

Looks like bad memory or GPU overclock but you have also lots of mods running. Try to rename the whole C:\Users\Jazza\Saved Games\DCS folder to DCS.bak and try again.

Didnt do anything either. Havent overclocked the GPU and it ran a stress test fine without any artifacting. I will run memtest overnight see what the RAM throws up.

[draconus]

1 minute ago, Jazzadanub said:

Didnt do anything either. Havent overclocked the GPU and it ran a stress test fine without any artifacting. I will run memtest overnight see what the RAM throws up.

Not gonna hurt to test but I was thinking about VRAM rather than RAM.  Good job on testing and providing results

[mkel2010]

9 hours ago, Jazzadanub said:

Hi Bignewy,

Got any suggestions on something else I can try. Did a clean reinstall on the NVIDIA drivers, rechecked the GPU seating and I stress tested the GPU and there were no issues. Tried the graphic settings in game on lowest, does exactly the same thing. Tried in 2D, also the same results.

I am going to try rolling back to a restore point before the map purchase to see if does anything.

I'm not having the problem you're experiencing, but I came across a video that just came out a few days ago about video settings in DCS. Maybe worth a look:

 

[Jazzadanub]

12 hours ago, draconus said:

Looks like bad memory or GPU overclock but you have also lots of mods running. Try to rename the whole C:\Users\Jazza\Saved Games\DCS folder to DCS.bak and try again.

It was a good suggestion thanks. So what I did overnight was try FS2020 and it was displaying unusual graphics FS2020 weird graphics so I ran a GPU stress tester which didn't identify any problems, tried MSI Kombuster no issues either. Ran Memtest overnight no problems, but still getting the feeling it was the GPU itself. Ran 3D Mark Time Spy and you can see it artifacting 3D Mark artifacting so I am pretty sure it is now the GPU.

Sorry for wasting your time fellas & @BIGNEWY It must have just been coincidental that the GPU seems to have played up the same time the Kola Map launched.

[BIGNEWY]

6 hours ago, Jazzadanub said:

Sorry for wasting your time fellas & @BIGNEWY It must have just been coincidental that the GPU seems to have played up the same time the Kola Map launched.

Never a waste of time, there is always someone in the team or community happy to help. Glad you have it sorted. 

This Older thread is fixed now so will close. 

I have moved the last two posts to a new thread