Issues with the viewport when activating the option "Display in front". #82240

Closed
opened 2020-10-29 23:41:40 +01:00 by Carlos Muñoz · 35 comments

System Information
Operating system: Windows
Graphics card: AMD Radeon RX 580 (last drivers)

Blender Version
Broken: 2.92 (alpha) and 2.91 (release)
Worked: work well on 2.83.9

Short description of error
Issues with the viewport when activating the option "Display in front".
It mainly happens when you activate x-ray and "display in-front" at the same time
imagen.png
viewport-bug.gif

Exact steps for others to reproduce the error
Create two cubes. Activate the xray visualization. Select an object an activate "display in front" option.
Notice: It happens ONLY in 2.91 and 2.92 version.
viewport_issues.blend

**System Information** Operating system: Windows Graphics card: AMD Radeon RX 580 (last drivers) **Blender Version** Broken: 2.92 (alpha) and 2.91 (release) Worked: work well on 2.83.9 **Short description of error** Issues with the viewport when activating the option "Display in front". It mainly happens when you activate x-ray and "display in-front" at the same time ![imagen.png](https://archive.blender.org/developer/F9129464/imagen.png) ![viewport-bug.gif](https://archive.blender.org/developer/F9129437/viewport-bug.gif) **Exact steps for others to reproduce the error** Create two cubes. Activate the xray visualization. Select an object an activate "display in front" option. **Notice: It happens ONLY in 2.91 and 2.92 version.** [viewport_issues.blend](https://archive.blender.org/developer/F9129477/viewport_issues.blend)
Author

Added subscriber: @carlosmu

Added subscriber: @carlosmu

#83001 was marked as duplicate of this issue

#83001 was marked as duplicate of this issue
Carlos Muñoz changed title from Problems with the viewport when activating the option "Display in front". to Issues with the viewport when activating the option "Display in front". 2020-10-29 23:43:25 +01:00

Added subscriber: @nicholashawkes

Added subscriber: @nicholashawkes

Added subscriber: @mano-wii

Added subscriber: @mano-wii

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

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

I cannot reproduce this problem, has it already been resolved in the latest development versions of Blender?

Please try the latest daily build: https://builder.blender.org/download/

Also, don't forget to mention the specific version you tested again.

I cannot reproduce this problem, has it already been resolved in the latest development versions of Blender? Please try the latest daily build: https://builder.blender.org/download/ Also, don't forget to mention the specific version you tested again.
Author

did you test with gpu amd?
I think that's where the problem lies.

version: 2.92.0 Alpha, branch: master, commit date: 2020-10-30 23:29, hash: 316a5914bc, type: Release
build date: 2020-10-31, 00:25:16
platform: Windows 10

2020-10-31 01-01-22.mp4

did you test with gpu amd? I think that's where the problem lies. version: 2.92.0 Alpha, branch: master, commit date: 2020-10-30 23:29, hash: 316a5914bcc6, type: Release build date: 2020-10-31, 00:25:16 platform: Windows 10 [2020-10-31 01-01-22.mp4](https://archive.blender.org/developer/F9137803/2020-10-31_01-01-22.mp4)
Member

Added subscriber: @lichtwerk

Added subscriber: @lichtwerk
Member

Could you check the following, please:

Open Blender using blender_debug_gpu.cmd that is located underneath blender.exe in the same folder. After closing Blender, a folder will open with 2 txt files. Upload them here.

Could you check the following, please: Open Blender using `blender_debug_gpu.cmd` that is located underneath blender.exe in the same folder. After closing Blender, a folder will open with 2 txt files. Upload them here.
Author

Ok!

I tried with the lastest build, and the issue persist.

blender_debug_output.txt

blender_system_info.txt

Ok! I tried with the lastest build, and the issue persist. [blender_debug_output.txt](https://archive.blender.org/developer/F9318546/blender_debug_output.txt) [blender_system_info.txt](https://archive.blender.org/developer/F9318547/blender_system_info.txt)
Member

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

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

Can you try running blender_factory_startup.cmd which is also available in the same folder as the blender.exe?
It is quite possible that this problem is being caused by some addon.

Can you try running `blender_factory_startup.cmd` which is also available in the same folder as the `blender.exe`? It is quite possible that this problem is being caused by some addon.
Author
don't work... ![imagen.png](https://archive.blender.org/developer/F9318788/imagen.png) [blender_debug_output.txt](https://archive.blender.org/developer/F9318795/blender_debug_output.txt) [blender_system_info.txt](https://archive.blender.org/developer/F9318796/blender_system_info.txt)
Author

Now the glitch came at 2.91 (final release)

glitch.jpg

Now the glitch came at 2.91 (final release) ![glitch.jpg](https://archive.blender.org/developer/F9402879/glitch.jpg)

Try running blender_debug_gpu_glitchworkaround.cmd.
There is a small chance that the viewport will work correctly in this case.
If it works, will be a good indication that the solution is simple (and the problem is in the driver).

Try running `blender_debug_gpu_glitchworkaround.cmd`. There is a small chance that the viewport will work correctly in this case. If it works, will be a good indication that the solution is simple (and the problem is in the driver).
Author
don't work ![imagen.png](https://archive.blender.org/developer/F9414910/imagen.png) [blender_debug_output.txt](https://archive.blender.org/developer/F9414915/blender_debug_output.txt) [blender_system_info.txt](https://archive.blender.org/developer/F9414917/blender_system_info.txt)

It is very difficult for us to say what is happening, because even with the same hardware we are not able to reproduce the problem.

However, the driver version installed here is more recent:

Renderer: Radeon (TM) RX 480 Graphics
Version: 4.5.13596 Core Profile Context 20.10 27.20.1034.6
It is very difficult for us to say what is happening, because even with the same hardware we are not able to reproduce the problem. However, the driver version installed here is more recent: ``` Renderer: Radeon (TM) RX 480 Graphics Version: 4.5.13596 Core Profile Context 20.10 27.20.1034.6 ```
Author

I updated drivers from 20.09 to 20.11 and the issue persists.

imagen.png

I updated drivers from 20.09 to 20.11 and the issue persists. ![imagen.png](https://archive.blender.org/developer/F9415193/imagen.png)
Member

Added subscriber: @chingis

Added subscriber: @chingis
Member

Removed subscriber: @chingis

Removed subscriber: @chingis

Added subscriber: @Harti

Added subscriber: @Harti
Author

Excuse me. Does this mean that it will no longer be fixed?
The issue persists in the latest version in the builder.
imagen.png

Excuse me. Does this mean that it will no longer be fixed? The issue persists in the latest version in the builder. ![imagen.png](https://archive.blender.org/developer/F9438332/imagen.png)

Added subscriber: @GuillermoEspertino

Added subscriber: @GuillermoEspertino

I can confirm this issue on a RX570 as well.
The steps provided by Carlos to reproduce the error cause the same type of glitches.

Blender 2.91 on Windows 10, official build from blender.org
I'm using the Pro Enterprise drivers, version 20.10.27.03-200826a-358464C-RadeonProEnterprise

In my case, the issue doesn't end with the glitches alone. I cannot turn on GPU rendering in cycles as it will hardlock the computer completely (this has been the case since 2.83 and both the regular drivers and the Pro Enterprise ones do the same, updated or not.

I can confirm this issue on a RX570 as well. The steps provided by Carlos to reproduce the error cause the same type of glitches. Blender 2.91 on Windows 10, official build from blender.org I'm using the Pro Enterprise drivers, version 20.10.27.03-200826a-358464C-RadeonProEnterprise In my case, the issue doesn't end with the glitches alone. I cannot turn on GPU rendering in cycles as it will hardlock the computer completely (this has been the case since 2.83 and both the regular drivers and the Pro Enterprise ones do the same, updated or not.

It's possible that someone made a mistake in listing unsupported graphics cards / drivers. I'll take a look. Thanks for the info.

It's possible that someone made a mistake in listing unsupported graphics cards / drivers. I'll take a look. Thanks for the info.

In #82240#1067689, @carlosmu wrote:
Excuse me. Does this mean that it will no longer be fixed?
The issue persists in the latest version in the builder.
imagen.png

It doesn’t mean that it won’t be fixed, it indicates that developers are aware of the problem but have not found a solution in the Blender side (13c3ad7e).

> In #82240#1067689, @carlosmu wrote: > Excuse me. Does this mean that it will no longer be fixed? > The issue persists in the latest version in the builder. > ![imagen.png](https://archive.blender.org/developer/F9438332/imagen.png) It doesn’t mean that it won’t be fixed, it indicates that developers are aware of the problem but have not found a solution in the Blender side (13c3ad7e).

@mano-wii Is the problem with this line of GPUs documented anywhere? It's a somewhat recent line of products that work flawlessly with other specialized CG software packages.
I'm only having this issues with Blender, when Fusion/Resolve, all the Adobe and Affinity apps, and all the Substance suite, all of them doing a pretty extensive use of OpenCL and the GPU run without any issues.
What are the specific problems that AMD should solve in their drivers?

@mano-wii Is the problem with this line of GPUs documented anywhere? It's a somewhat recent line of products that work flawlessly with other specialized CG software packages. I'm only having this issues with Blender, when Fusion/Resolve, all the Adobe and Affinity apps, and all the Substance suite, all of them doing a pretty extensive use of OpenCL and the GPU run without any issues. What are the specific problems that AMD should solve in their drivers?
Author

I update the Description.
This bug happens only in 2.91+ versions.
Work fine in 2.83.9 LTS
imagen.png

I update the Description. This bug happens only in 2.91+ versions. Work fine in 2.83.9 LTS ![imagen.png](https://archive.blender.org/developer/F9451963/imagen.png)
Author

In #82240#1067823, @GuillermoEspertino wrote:
@mano-wii Is the problem with this line of GPUs documented anywhere? It's a somewhat recent line of products that work flawlessly with other specialized CG software packages.
I'm only having this issues with Blender, when Fusion/Resolve, all the Adobe and Affinity apps, and all the Substance suite, all of them doing a pretty extensive use of OpenCL and the GPU run without any issues.
What are the specific problems that AMD should solve in their drivers?

In my case I use Unity, Maya and Photoshop without problems in the same PC.

> In #82240#1067823, @GuillermoEspertino wrote: > @mano-wii Is the problem with this line of GPUs documented anywhere? It's a somewhat recent line of products that work flawlessly with other specialized CG software packages. > I'm only having this issues with Blender, when Fusion/Resolve, all the Adobe and Affinity apps, and all the Substance suite, all of them doing a pretty extensive use of OpenCL and the GPU run without any issues. > What are the specific problems that AMD should solve in their drivers? In my case I use Unity, Maya and Photoshop without problems in the same PC.

Although I cannot confirm, I believe it is the same problem as #83179, this report has an explanation of what is happening.

Although I cannot confirm, I believe it is the same problem as #83179, this report has an explanation of what is happening.

It doesn't say anything about what's the specific issue with the driver. Apart from that, it used to work in earlier versions as Carlos pointed out.
The other issue I commented (the hardlock with GPU rendering) clearly doesn't belong to this report but was also something that changed between blender versions, which at least suggest that there is a portion of the code that is causing it.

It doesn't say anything about what's the specific issue with the driver. Apart from that, it used to work in earlier versions as Carlos pointed out. The other issue I commented (the hardlock with GPU rendering) clearly doesn't belong to this report but was also something that changed between blender versions, which at least suggest that there is a portion of the code that is causing it.

After updating the drivers (to a version after the recommended one) I was able to reproduce the problem.
Even though the steps to reproduce the problem are different, it is the same problem as #83022 (Transparency in Solid View Causes Glitch Artifacts)
So I will merge the reports

After updating the drivers (to a version after the recommended one) I was able to reproduce the problem. Even though the steps to reproduce the problem are different, it is the same problem as #83022 (Transparency in Solid View Causes Glitch Artifacts) So I will merge the reports

Closed as duplicate of #83022

Closed as duplicate of #83022

Added subscriber: @typicallyze

Added subscriber: @typicallyze

this issue is still there in the latest experimental builds

this issue is still there in the latest experimental builds
Sign in to join this conversation.
No Label
Interest
Alembic
Interest
Animation & Rigging
Interest
Asset Browser
Interest
Asset Browser Project Overview
Interest
Audio
Interest
Automated Testing
Interest
Blender Asset Bundle
Interest
BlendFile
Interest
Collada
Interest
Compatibility
Interest
Compositing
Interest
Core
Interest
Cycles
Interest
Dependency Graph
Interest
Development Management
Interest
EEVEE
Interest
EEVEE & Viewport
Interest
Freestyle
Interest
Geometry Nodes
Interest
Grease Pencil
Interest
ID Management
Interest
Images & Movies
Interest
Import Export
Interest
Line Art
Interest
Masking
Interest
Metal
Interest
Modeling
Interest
Modifiers
Interest
Motion Tracking
Interest
Nodes & Physics
Interest
OpenGL
Interest
Overlay
Interest
Overrides
Interest
Performance
Interest
Physics
Interest
Pipeline, Assets & IO
Interest
Platforms, Builds & Tests
Interest
Python API
Interest
Render & Cycles
Interest
Render Pipeline
Interest
Sculpt, Paint & Texture
Interest
Text Editor
Interest
Translations
Interest
Triaging
Interest
Undo
Interest
USD
Interest
User Interface
Interest
UV Editing
Interest
VFX & Video
Interest
Video Sequencer
Interest
Virtual Reality
Interest
Vulkan
Interest
Wayland
Interest
Workbench
Interest: X11
Legacy
Blender 2.8 Project
Legacy
Milestone 1: Basic, Local Asset Browser
Legacy
OpenGL Error
Meta
Good First Issue
Meta
Papercut
Meta
Retrospective
Meta
Security
Module
Animation & Rigging
Module
Core
Module
Development Management
Module
EEVEE & Viewport
Module
Grease Pencil
Module
Modeling
Module
Nodes & Physics
Module
Pipeline, Assets & IO
Module
Platforms, Builds & Tests
Module
Python API
Module
Render & Cycles
Module
Sculpt, Paint & Texture
Module
Triaging
Module
User Interface
Module
VFX & Video
Platform
FreeBSD
Platform
Linux
Platform
macOS
Platform
Windows
Priority
High
Priority
Low
Priority
Normal
Priority
Unbreak Now!
Status
Archived
Status
Confirmed
Status
Duplicate
Status
Needs Info from Developers
Status
Needs Information from User
Status
Needs Triage
Status
Resolved
Type
Bug
Type
Design
Type
Known Issue
Type
Patch
Type
Report
Type
To Do
No Milestone
No project
No Assignees
8 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: blender/blender#82240
No description provided.