Viewport Display: In front. Glitches (just in 3dViewport background). AMD. #67615

New Issue

Juanfran Matheu · 2019-07-24T22:23:21+02:00

Juanfran Matheu commented

2019-07-24 22:23:21 +02:00

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: 38d4483c6a
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(?

2019-07-24 21-58-24.mp4

When Changing modes and workspaces

2019-07-24 22-03-09.mp4

**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: `38d4483c6a` 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(? [2019-07-24 21-58-24.mp4](https://archive.blender.org/developer/F7627043/2019-07-24_21-58-24.mp4) When Changing modes and workspaces [2019-07-24 22-03-09.mp4](https://archive.blender.org/developer/F7627052/2019-07-24_22-03-09.mp4)

Juanfran Matheu commented

2019-07-24 22:23:21 +02:00

Added subscriber: @jfmatheu

Germano Cavalcante commented

2019-07-25 16:54:09 +02:00

Added subscriber: @mano-wii

Germano Cavalcante commented

2019-07-25 16:54:09 +02:00

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

Juanfran Matheu commented

2019-07-27 19:44:19 +02:00

@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?)

2019-07-27 19-30-48.mp4

MonsterTest.blend

@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?) [2019-07-27 19-30-48.mp4](https://archive.blender.org/developer/F7632196/2019-07-27_19-30-48.mp4) [MonsterTest.blend](https://archive.blender.org/developer/F7632204/MonsterTest.blend)

Germano Cavalcante commented

2019-07-27 22:51:19 +02:00

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.

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.

Juanfran Matheu commented

2019-07-28 16:22:56 +02:00

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...

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...

Sybren A. Stüvel commented

2019-08-06 14:32:45 +02:00

Added subscriber: @dr.sybren

Sybren A. Stüvel commented

2019-08-06 14:32:45 +02:00

@jfmatheu since this is so tricky for us to reproduce, can you test with the latest build from https://builder.blender.org/download/? Maybe it was fixed along with other bugfixes.

Juanfran Matheu commented

2019-08-06 16:10:06 +02:00

Sure! @dr.sybren

Juanfran Matheu commented

2019-08-06 16:24:01 +02:00

@dr.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)

@dr.sybren I still have this problem with 2.81. Also updated to new driver version of AMD. ![image.png](https://archive.blender.org/developer/F7651703/image.png) Later I'll try with a new file created with 2.81 (this is from 2.80)

Sybren A. Stüvel commented

2019-08-06 16:55:54 +02:00

Added subscriber: @Jeroen-Bakker

Sybren A. Stüvel commented

2019-08-06 16:55:54 +02:00

@Jeroen-Bakker do you have the means to investigate this?

Jeroen Bakker commented

2019-08-07 08:57:10 +02:00

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. @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

Thanks!

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. @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` Thanks!

Juanfran Matheu commented

2019-08-07 21:40:26 +02:00

@Jeroen-Bakker

system-info.txt

Console_Info_Debug_GPU.txt

@Jeroen-Bakker [system-info.txt](https://archive.blender.org/developer/F7653524/system-info.txt) [Console_Info_Debug_GPU.txt](https://archive.blender.org/developer/F7653525/Console_Info_Debug_GPU.txt)

Juanfran Matheu commented

2019-08-11 09:16:37 +02:00

@Jeroen-Bakker Hi, yesterday I reported this https://developer.blender.org/T68519 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.

Germano Cavalcante commented

2019-08-12 16:35:10 +02:00

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

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

Juanfran Matheu commented

2019-08-12 16:55:56 +02:00

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

2019-08-12 16-45-05.mp4

Addons are fine @mano-wii (Jump to 1:58 to see the effect triggered) [2019-08-12 16-45-05.mp4](https://archive.blender.org/developer/F7660454/2019-08-12_16-45-05.mp4)

Sybren A. Stüvel commented

2019-08-13 13:57:50 +02:00

Removed subscriber: @dr.sybren

Jeroen Bakker commented

2020-01-21 08:24:17 +01:00

Changed status from 'Needs Developer To Reproduce' to: 'Needs User Info'

Jeroen Bakker commented

2020-01-21 08:24:17 +01:00

@jfmatheu Is this issue still happening with the latest blender and AMD drivers? We have never been able to reproduce this issue, but AMD has done a lot of improvements in their GPU drivers that might have solved this issue.

Juanfran Matheu commented

2020-01-21 14:50:20 +01:00

Hi @Jeroen-Bakker I can't reproduce it now with last 2.82 beta and last AMD drivers, glitches are gone!

But I notice another issue and is that the behaviour expected using 'in front' option is kinda broken, just see:

It's supposed to show the lines and points correctly to be able to edit them, but can't work with this. Also the behaviour looks inverted, far edges are more sharp/accurate while near edges and points are not.

The same if I create a new project :

And the file :
InFrontBadBehaviour.blend

Hi @Jeroen-Bakker I can't reproduce it now with last 2.82 beta and last AMD drivers, glitches are gone! But I notice another issue and is that the behaviour expected using 'in front' option is kinda broken, just see: ![image.png](https://archive.blender.org/developer/F8292004/image.png) It's supposed to show the lines and points correctly to be able to edit them, but can't work with this. Also the behaviour looks inverted, far edges are more sharp/accurate while near edges and points are not. The same if I create a new project : ![image.png](https://archive.blender.org/developer/F8292021/image.png) And the file : [InFrontBadBehaviour.blend](https://archive.blender.org/developer/F8292024/InFrontBadBehaviour.blend)

Evan Wilson commented

2020-01-24 16:28:24 +01:00

Added subscriber: @EAW

Evan Wilson commented

2020-01-24 16:28:24 +01:00

Changed status from 'Needs User Info' to: 'Resolved'

Evan Wilson closed this issue

2020-01-24 16:28:24 +01:00

Evan Wilson self-assigned this 2020-01-24 16:28:24 +01:00

Evan Wilson commented

2020-01-24 16:28:24 +01:00

I can't reproduce it now with last 2.82 beta and last AMD drivers, glitches are gone!

Glad to hear! I will close this as resolved.

But I notice another issue and is that the behaviour expected using 'in front' option is kinda broken, just see:
It's supposed to show the lines and points correctly to be able to edit them, but can't work with this. Also the behaviour looks inverted, far edges are more sharp/accurate while near edges and points are not.

Please open new report for this issue. We can only have one issue per report, otherwise issues become impossible to track.

> I can't reproduce it now with last 2.82 beta and last AMD drivers, glitches are gone! Glad to hear! I will close this as resolved. > But I notice another issue and is that the behaviour expected using 'in front' option is kinda broken, just see: >It's supposed to show the lines and points correctly to be able to edit them, but can't work with this. Also the behaviour looks inverted, far edges are more sharp/accurate while near edges and points are not. Please open new report for this issue. We can only have one issue per report, otherwise issues become impossible to track.

Sign in to join this conversation.

No Label

Download

What's New

Blender Studio

Manual

Developers Blog

Documentation

Benchmark

Blender Conference

Development Fund

One-time Donations

Viewport Display: In front. Glitches (just in 3dViewport background). AMD. #67615