Page MenuHome

Viewport Display: In front. Glitches (just in 3dViewport background). AMD.
Open, Waiting for Developer to ReproducePublic


System Information
Operating system: Windows-10-10.0.18362 64 Bits
Graphics card: Radeon RX 580 Series ATI Technologies Inc. 4.5.13570 Core Profile Context 19.7.2 26.20.13001.16003

Blender Version
Broken: version: 2.80 (sub 74), branch: master, commit date: 2019-07-18 14:52, hash: rB38d4483c6a51
Worked: (optional)

Short description of error
Creepy broken pixels over the 3dviewport, just in the background itself, is not affecting how the mesh looks/draws or the UI elements (and gizmos)
Also is very related to the 'in front' option in viewport display but is not about the other known issue about 'in front' option that makes weird effects in the faces of the model.
This weird effects every time has triggered (randomly) to me while modeling (edit mode) and is transfered to other modes and to other workspaces as well (but not all of them).
I found that If the the effect is triggered when turning on in front option or tweaking the viewport display options (Display as... ) while in front is active, it will stay there even when turning off in front option later
My graphics card is new and drivers are updated so if it's about a graphic card issue maybe is about a compatibility issue with amd(?

When Changing modes and workspaces



Event Timeline

Germano Cavalcante (mano-wii) lowered the priority of this task from Needs Triage by Developer to Needs Information from User.Jul 25 2019, 4:54 PM

Can you provide a simple .blend file so it will be easer to investigate this problem.

@Germano Cavalcante (mano-wii) Well I can provide this file and... sometimes it triggers... but when you reopen Blender it's ok again (in most cases). So the fact is if you open it and all it's ok (at least at the start)... In this case probably will means a lack of compatibility with amd(?) If it's useful for You, I can try to run Blender with the command line for gpu. --debug-gpu-force-workarounds or any other to see what happens.

Here is a video provocating (by first time in this file) this issue in the same blend file that I provide you here

(Also I notice in the video that when I switched from sculpt to edit mode I had vertices selected but I didn't.... e.e I even didn't switched to edit mode before, just a cube with some subdivs and from there to sculpt mode til the moment of the video I provided. So.. maybe is a bug?)

I have a setup similar:

Operating system: Windows-10-10.0.18941 64 Bits
Graphics card: Radeon (TM) RX 480 Graphics ATI Technologies Inc. 4.5.13570 Core Profile Context 19.7.2 26.20.13001.16003

Maybe I would be able to reproduce the problem.
But I tried the file, edited the mesh, changed the workspace, x-ray, and nothing.

Yeah, as I said I reopen the file and it's ok (in most cases, sometimes it opens bad), no issues, and then with some time editing and working around... it comes back by magic, at least this is what is happenning to me (literaly). And always is trigger because of ''in front'' option in solid and textured display mode, BUT not always happen or happen if you switch to other workspace. That's the all thing.

It isn't an easy issue to reproduce or debug at all... So not sure what can it be. I wish to have linux installed to try it so we can discard things but I don't...

@Juanfran Matheu (jfmatheu) since this is so tricky for us to reproduce, can you test with the latest build from Maybe it was fixed along with other bugfixes.

@Sybren A. Stüvel (sybren)

I still have this problem with 2.81. Also updated to new driver version of AMD.

Later I'll try with a new file created with 2.81 (this is from 2.80)

Sybren A. Stüvel (sybren) raised the priority of this task from Needs Information from User to Waiting for Developer to Reproduce.Aug 6 2019, 4:55 PM

@Jeroen Bakker (jbakker) do you have the means to investigate this?

Jeroen Bakker (jbakker) lowered the priority of this task from Waiting for Developer to Reproduce to Needs Information from User.EditedAug 7 2019, 8:57 AM

Seems like a faulty blit function (unlikely) or an incorrect GLState (likely but then should be reproduceable by any Polaris based card) or an incorrect framebuffer...

At this point we cannot tell for sure until we can reproduce it. @Juanfran Matheu (jfmatheu) just to be sure can you also provide us with the system-info.txt that is generated by Blender using Help -> Save System Info.

Also can you provide us with the blender gpu-log when reproducing the error.

blender.exe --debug-gpu


@Jeroen Bakker (jbakker)

@Jeroen Bakker (jbakker) Hi, yesterday I reported this and looks like an issue from AMD drivers with Windows 10 May update. I don't know if it's related to the issue reported here in some point (or not), but I wanted You to know about it, just in case it turns out to be like that.

This could be related to some addon.
Pls, try with the factory settings (File -> Defaults -> Load Factory Settings).

Addons are fine @Germano Cavalcante (mano-wii)
(Jump to 1:58 to see the effect triggered)

Bastien Montagne (mont29) raised the priority of this task from Needs Information from User to Waiting for Developer to Reproduce.Aug 20 2019, 11:12 AM