GUI Flicker on Mouse Move

Hi all,

I've just installed Resolve for the first time and it's running very smoothly, except that the background grey flickers between shades of green and red in the main window when I move my mouse over different panels and buttons. This does not show in video while editing, or in rendered video. I couldn't find any threads describing this issue.

This only happens in Resolve. My specs are a Ryzen 3600X processor and a GTX 2070 Super. My monitor is 1920x1080 at 144Hz.

Any advice? Thanks in advance.

I should add it also stops a few seconds after I open an in-program window like preferences, or a drop-down menu.

[Rohit Singhal]

Can you check if your GPU driver is up to date? Maybe you might need a clean install of the driver. There is an option during the initial installation screens for the driver.

[Peter Chamberlain]

after the driver update, try refreshing the monitor at 72 and see if that changes anything.
if not, take a phone video and post a link to it here so we can see.

Thanks for the responses! Reinstalling the drivers didn't fix anything, neither did changing my refresh rate - but it reminded me that I have a FreeSync monitor and a Nvidia GPU. Creating an app profile for Resolve in NVIDIA Control Panel where I set the monitor technology from 'gsync compatible' to 'fixed refresh' fixed the issue!

Hi!

I just wanted to say thank you for your solution, i was having the same issue with Resolve, but with a GSync monitor and 2070 Super (actually your system is identical to mine).

I tried the monitor setting in the nVidia Control Panel and it works like a charm.

The issue might be something to be looked at by Blackmagic though.

Thanks for the responses! Reinstalling the drivers didn't fix anything, neither did changing my refresh rate - but it reminded me that I have a FreeSync monitor and a Nvidia GPU. Creating an app profile for Resolve in NVIDIA Control Panel where I set the monitor technology from 'gsync compatible' to 'fixed refresh' fixed the issue!

Hey guys. I'm having the same issue but on my iMac Pro screen when moving the mouse, and only when plugged into my new LG OLED TV. It even does it when the TV is powered off. It only stops if I unplug the USB-C to HDMI cable. The TV screen does NOT flicker though. I had a cheaper LG TV and it did not have the same problem. I think the LG OLED TV is VVidea enabled too. Any ideas on how to fix this issue?

Same issue here when moving mouse. I'm also getting very fast timeline flickering during playback (playback itself is not flickering, just the clips in the full-screen timeline view).

I'm using dual screens with a MBP 2018, 2.6 GHz 6-Core Intel Core i7 on Catalina 10.15.7. Davinci Resolve is running 17.1.

EDIT: Swapping the main display in the Dual Screen menu from the external display to the MBP screen and back again has fixed it, for now at least.

Hm though i was going mad. Also some flickering at the bottom 5% of the screen on mac/hackintosh with dual radeon 56. Its there sometimes when i move the mouse and only started with 17.1
Untill and including 17.0 i had zero crashes for the last year or so including every beta and all super stable on mojave but 17.1 i had alteady several crashes. Thinking about going back as adds nothing i need other then M1 balast.
Lots of variables to investigate but no time now. Maybe at some later point i will revisit.

To be a bit more specific , i can draw with a finder window on the Resolve UI by moving it across it. Like a lighter shadow you draw on the screen. It disappears if you make Resolve the active window again. So something going on with GPUdrivers there.

Also the H264 HW acceleration is slower on 17.1 with the new HW accc switch on, then on 17.0 (that on my dual radeon setup does not need a switch as is native on).
Diff is not huge but noticeable. 1-2% by just playing ity back in media pool on a 14 core machine is still someting.
Also the GPU seems to work a bit harder. Repeatable by switching back and forth.
Maybe related to 17.1 beeing optimised for Catalina now and i am on Mojave.
Or the M1 balast.
Either way, seems for now 17.0 is my end station.....

2021-03-13_17-21-38.png (157.33 KiB) Viewed 3120 times

Yeah - its an issue... 2years after the thread.

Purchased Resolve studio and have flicker now when the mouse moves.
Dances with the mouse!
(actually not funny - bothers the eyes)

Asus - laptop - Nvidia GTX
Windows 10 (updated to 11 - then clean installed back to 10)
and I looked in the Nvidia control panel only seeing settings for 3D - nadda for a display in any menu.
* So that solution is a no go for me.

Would love to see this in a quick fix update...
Refresh rate on my system is either 60 or 120 and thats it, and neither worked in solving this.

Thanks guys... look forward to the 70s disco strobe effect staying on the dance floor... not on my monitor.

In the six years I have used Resolve, and all the versions from 14 up to 18.1.1, I have never seen this issue. Both my HD monitors are set to their native 100% resolution and are running at 60hz. This is with an Nvidia GTX 1060.

this morning my resolve suddenly flickered like mad while I moved my mouse across it. No flickering when mouse was stationary. I assumed it was a problem with the external monitor I have on my macbook, a samsung uhd, but then the monitor didnt flicker unless I was active on the resolve app (while the resolve app was not the active app but still lay on the monitor, moving mouse over caused no flickering). Then it turns out it was flickering in the same fashion on my laptop monitor as well. Took a cue to enable dual screen, and the problem is gone. This seems the only way to stop it on my system.

I arrived at this older thread due to having the same issue.

Win 11
RTX 4090
Resolve 18.6.5
LG C2 OLED Display

Regardless of G-Sync setting the interface was manically flickering seemingly for no reason on and off when mousing around.

Eventually I stopped it by going to the Nvidia "Manage 3D Settings", choosing Resolve, and changing "Preferred refresh rate" to "Application controlled"

Not sure why this works, but it put an end to the problem.

Hopefully if anyone else ends up at this thread after Googling the issue, it helps.