Bug: Material flickering when I copy object

When I create a material (even a simple flat-colored one) then copy (regular copy with shift D) the object and give it a different material, the original object’s preview (in material preview mode) flickers between its own material (actually applied to it) and the one from the copy (that it shouldn’t even know exists).
Does anyone else have this issue? I haven’t found any mention of it anywhere.

Additional note: it happens when I create a mesh with the same geometry, so if the original mesh is the default cube, the bug happens too if I add a new cube (instead of copying); and if the original mesh is the default cube that I added a loop cut to, and the “copy” is a freshly added default cube, then the bug happens to the non-loop-cut faces only.
Additional note 2: I’m using blender 5.2.2.

Edit: Here is a video showing the bug (starting from the default “new scene with a cube”): https://www.youtube.com/watch?v=L_nQSJGO-xk

Just a wild guess: Is the copied object positioned exactly at the same place as the original object?
Does the flickering go away when you move one of the objects slightly?

If this works: Google “Z-Fighting”. This happens when two or more polygons cover the same 3D space and cause all kinds of artifacts.

no, I moved it so I could see both clearly. There is no overlap.

I just edited the original message with a link to a video showing it.

Wow! I’ve never seen anything like this. :thinking:

You’re using EEVEE, does this also happen when using Cycles?

Can you try to switch off “Temporal Reprojection” or “Denoising” in EEVEE?
(You may have to switch your Render Engine to EEVEE to have access to these settings, in your video you’re just using the “Material Preview”).

Thank you for the suggestions; I just tried them.
Both eevee and cycles do that, even with Temporal Reprojection turned off. I did not find any “denoise” option in eevee (I assumed you were talking about the Properties > Scene tab) except under “raytracing”, which is turned off, and turning off Cycles’ denoise (under Sampling > Viewport and Sampling > Render) did not fix it either
I’ll have access to a different computer next week, so I’ll check whether it does it there too.

Your GPU drivers are definitely up to date, right?

I think so.
I’m using a LTS distribution (not the very last one, but one that was released last year), and the drivers are the recommended ones.

No such behaviour with 5.2.2 on my side ( linux debian 12)..

that’s good to know, thank you!

Ohh… and what’s really weird here is this “fading” to the other material.. so you are sure no AI assistant has taken over your PC ??? :sweat_smile:

Ohh my.. because of AI i now get really weird ideas… :anxious_face_with_sweat:

I also checked and no such behavior (5.2.2 Open Suse)

The main thing to check apart from GPU and drivers would be addons, If you are using addons try turning them off one by one and also all of them at once (it could be that 2 different addons are fighting each other).

This certainly is not “normal behavior”. So maybe also list all your system specs, OS, Hardware etc

Maybe someone with similar specs could try and confirm.

Besides making sure the drivers are actually up to date, I would try switchin OpenGL and Vulcan graphics backends in the preferences to see if that makes a difference. That seems to solve quite a few problems lately. There seem to be different kinds of bugs in each. But I think it’s the GPU drivers. Makes sense - 5.2.2 was released few days ago, it makes sense that they develop stuff with most recent drivers and so that gets tested most.

Switching to Vulkan fixed it! Thank you (and everyone who answered!).

For posterity: it’s in Edit > Preferences > System > Display Graphics > Backend

Another advantage is that shader compilation should be a lot faster :smiley:. In Blender 5.3 Vulkan is the default.