Strange artifacts in interface

So for the past two weeks, I occasionally see weird anomalies like this in the interface:




The two times it's happened before, a simple restart seemed to clear it.
It does NOT appear to be affecting the files or the edit in anyway other than making it funky to figure out what's on the timeline.

If I switch into fairlight or color or fusion the file names all read clearly.

Any thoughts on what is causing this? Something on my end?

Been two weeks and I'm still getting this error. It doesn't happen all the time. Sometimes a restart of Resolve fixes it. Sometimes a restart of my computer fixes it. Sometimes I'll be working in one section (i.e Fairlight or Color and I'll switch back to something else, like the editor and it suddenly appears.

Capture from today's bout of it.



I've tried deleting preferences. Reinstalling Resolve. It happens on any project I currently have in the Projects Manager, not just one.

Looks like a GPU with insufficient cooling to me, or even a dying one.
Check your computer for dust, it's often a surprise how much is building up in the cooling system.

Looks like a GPU with insufficient cooling to me, or even a dying one.
Check your computer for dust, it's often a surprise how much is building up in the cooling system.

Will do.

I really, really hope it isn't the later. Yikes.

Looks like a GPU with insufficient cooling to me, or even a dying one.
Check your computer for dust, it's often a surprise how much is building up in the cooling system.

Welp, after two and a half days of support with Apple, diagnostics, deleting, reinstalling, reinstalling everything, updating, unplugging and plugging in various attachments including an eGPU, Apple says it's not my system. Doesn't happen on ANYTHING else on my machine. Just Davinci Resolve.

Where do I go for some full on support from Blackmagic with this now?

I'm not saying it's not the GPU dying, but I had similar looking artifacts on the interface too with the earlier beta, after using the depth map (or the magic mask, I don't remember). It fixed it by restarting Resolve.

And I have an nVidia card, on Windows (op has an AMD one on Mac)

Don't know if it's related to any harddrive memory cache, but did you also check your harddrive if it got any bad read/write sectors?

(By "cache" I don't mean render cache but operational cache of the Resolve UI or something like that.)

I'm not saying it's not the GPU dying, but I had similar looking artifacts on the interface too with the earlier beta, after using the depth map (or the magic mask, I don't remember). It fixed it by restarting Resolve.

And I have an nVidia card, on Windows (op has an AMD one on Mac)

Sometimes restarting fixed things but not always. It was really erratic to be honest. And I'm on 17.4. Haven't yet upgraded to the beta as I'm usually a bit cautious about them. Although maybe the fixes in 18 somehow do get at this.

Don't know if it's related to any harddrive memory cache, but did you also check your harddrive if it got any bad read/write sectors?

(By "cache" I don't mean render cache but operational cache of the Resolve UI or something like that.)

Yeah, did this several times. I'm actually currently wiping everything completely clean (instead of just a fresh OS install) and reinstalling my entire system. We'll see what happens.

After this, I may just do a db backup and then upgrade to 18 to see if that fixes it. Right now, I'm trying to track down a download for 17.4. lolfof.

I had them on 18 (beta 3 and/or 4) I don't remember.
If I get them again I'll definitively take as screenshot this time

You know, I've been using Resolve for going on three years now.

Why...why...why...why is the process of installing Resolve Studio and getting it activated so foreign?

I haven't done an install, just upgrades in a while and I cannot for the life of me get to a place to enter my activation key???????

Yeah, I realize, totally off-topic from the original post but it's definitely still part of the trouble shooting process.

Is it installing? Is it giving you an error?

Michael, is it possible you downloaded the free instead of the Studio version? When running Studio for the first time you should see the activation screen where you enter the code. A screen similar to this one.

Michael, is it possible you downloaded the free instead of the Studio version? When running Studio for the first time you should see the activation screen where you enter the code. A screen similar to this one.

Yeah that's what ended up happening. Not doing it very often you forget the 'features' in place to prevent cracking. I finally got it working. Thanks!

Don't know if it's related to any harddrive memory cache, but did you also check your harddrive if it got any bad read/write sectors?

(By "cache" I don't mean render cache but operational cache of the Resolve UI or something like that.)

Yeah, did this several times. I'm actually currently wiping everything completely clean (instead of just a fresh OS install) and reinstalling my entire system. We'll see what happens.

After this, I may just do a db backup and then upgrade to 18 to see if that fixes it. Right now, I'm trying to track down a download for 17.4. lolfof.

So this didn't fix it, problem came back.

I've not backed up all project and going to try upgrading to the 18 open beta to see if that cures the ills.

It could still be the GPU. DR is hammering GPUs like about nothing else, the GPUs in the older 'ashtray' Mac Pro were regularly freaking out rendering with DR.

It could still be the GPU. DR is hammering GPUs like about nothing else, the GPUs in the older 'ashtray' Mac Pro were regularly freaking out rendering with DR.

Okay, not going to jinx anything right now.

18 didn't fix it either. BUT. Because I completely started 100% fresh with a clean wipe of the computer (not a fresh install) and then building back up slowly with my other programs, I THINK I've found the culprit.

Haven't seen the bug since.

If all goes well through the weekend I'll post the reason/fix/gaff on Monday. I very much appreciate all the feedback and help.

Fingers crossed everyone. lolfof.

Here, after adding strokes to the magic mask, the whole interface started to glitch

Since I'm on a Windows 10 machine, with a nVidia card, totally different config from OP (Mac and AMD graphics card), and never had this on 17, it looks like it's mostly related to Resolve itself.

I don't have any glitches like this on any other software

The thing is, it doesn't always appears. There must be a chain of events that triggers this. Because when it starts, it doesn't stop. The GPU is totally IDLE.

Here the video of it

PS.
I had the same things happening with an older nVidia driver, I updated to the latest Studio one last week

Here the video of it

PS.
I had the same things happening with an older nVidia driver, I updated to the latest Studio one last week

Yikes, sorry this is happening.

I don't have nVidia drivers. Radeon both internal and eGPU. (on a mac.)

My problem has been fixed.

Been working all weekend without a reoccurence.

Turns out it was a plugin.

A very, very naughty plugin.

In all my other troubleshooting I deactivated all plugins to test out and it didn't change.

However, with this last step, since I completely wiped my computer clean, I decided to work slowly and ANY time I made a change to the system, I worked for it a bit before I added anything else. The moment I added this plug in, the problem came back. So I deactivated AND deleted the plug in.

Works.

Well, it's even worse now for me... nothing basic in resolve works...

After using magic mask, the whole UI glitches like crazy

Here the video of it

PS.
I had the same things happening with an older nVidia driver, I updated to the latest Studio one last week

Yikes, sorry this is happening.

I don't have nVidia drivers. Radeon both internal and eGPU. (on a mac.)

My problem has been fixed.

Been working all weekend without a reoccurence.

Turns out it was a plugin.

A very, very naughty plugin.

In all my other troubleshooting I deactivated all plugins to test out and it didn't change.

However, with this last step, since I completely wiped my computer clean, I decided to work slowly and ANY time I made a change to the system, I worked for it a bit before I added anything else. The moment I added this plug in, the problem came back. So I deactivated AND deleted the plug in.

Works.

I've been dealing with this problem for months, disabled one of my plugins and my Davinci finally worked! Thank you so much man <3

Here the video of it

PS.
I had the same things happening with an older nVidia driver, I updated to the latest Studio one last week

Yikes, sorry this is happening.

I don't have nVidia drivers. Radeon both internal and eGPU. (on a mac.)

My problem has been fixed.

Been working all weekend without a reoccurence.

Turns out it was a plugin.

A very, very naughty plugin.

In all my other troubleshooting I deactivated all plugins to test out and it didn't change.

However, with this last step, since I completely wiped my computer clean, I decided to work slowly and ANY time I made a change to the system, I worked for it a bit before I added anything else. The moment I added this plug in, the problem came back. So I deactivated AND deleted the plug in.

Works.

I've been dealing with this problem for months, disabled one of my plugins and my Davinci finally worked! Thank you so much man <3

Which plugin?
I get weird glitches (not like these anymore) when I'm using the magic mask.
I got the black blocks after using Resolve's internal plugin like magic mask

Some of the GiantUniverse OFX did weird things too for me, but not like that.

What was the plugin? I have the same problem.
Why the secrecy with the plugin name?

All Red Giant Universe plug-ins became useless after Maxon bought them. They don’t care about updating them.

I stopped using them too they are too buggy now.
Some companies are really trash

No I dont use them but still have this issue