Glitches with new AMD drivers (Adrenalin 22.7.1 or 22.8.2) when overlay has transparent images #100034

Closed
opened 7 months ago by Corps3 · 56 comments

System Information
Operating system: Windows-10-10.0.19041-SP0 64 Bits
Graphics card: AMD Radeon(TM) RX Vega 11 Graphics ATI Technologies Inc. 4.5.0 Core Profile Context 22.7.1.220725
Graphics card: Radeon (TM) RX 480 Graphics ATI Technologies Inc. 4.5.0 Core Profile Context 22.8.2.220819

Blender Version
Broken: version: 3.2.1, branch: master, commit date: 2022-07-05 15:44, hash: a2d59b2dac
Worked: version 3.1.2 (official release), not when rebuilding it from scratch...

Short description of error
When I import some image with transparency to appear as a scene object, distorted colored lines appear as shown in the attached image.
img2.png
img.png

RefImage.png

Render view (corruption is limited to the cube):

RefImage_renderview.png

Exact steps for others to reproduce the error

Also happens for camera-images, but only when in back. when set to front it renders fine. For empties this is the same.
RefImage_cam.blend

**System Information** Operating system: Windows-10-10.0.19041-SP0 64 Bits Graphics card: AMD Radeon(TM) RX Vega 11 Graphics ATI Technologies Inc. 4.5.0 Core Profile Context 22.7.1.220725 Graphics card: Radeon (TM) RX 480 Graphics ATI Technologies Inc. 4.5.0 Core Profile Context 22.8.2.220819 **Blender Version** Broken: version: 3.2.1, branch: master, commit date: 2022-07-05 15:44, hash: `a2d59b2dac` Worked: version 3.1.2 (official release), not when rebuilding it from scratch... **Short description of error** When I import some image with transparency to appear as a scene object, distorted colored lines appear as shown in the attached image. ![img2.png](https://archive.blender.org/developer/F13323112/img2.png) ![img.png](https://archive.blender.org/developer/F13323111/img.png) ![RefImage.png](https://archive.blender.org/developer/F13323327/RefImage.png) Render view (corruption is limited to the cube): ![RefImage_renderview.png](https://archive.blender.org/developer/F13323338/RefImage_renderview.png) **Exact steps for others to reproduce the error** - Open attached .blend file [RefImage.blend](https://archive.blender.org/developer/F13323330/RefImage.blend) Also happens for camera-images, but only when in back. when set to front it renders fine. For empties this is the same. [RefImage_cam.blend](https://archive.blender.org/developer/F13451665/RefImage_cam.blend)
Poster

Added subscriber: @Corps3

Added subscriber: @Corps3
Collaborator

#102616 was marked as duplicate of this issue

#102616 was marked as duplicate of this issue
Collaborator

#102559 was marked as duplicate of this issue

#102559 was marked as duplicate of this issue
Collaborator

#102525 was marked as duplicate of this issue

#102525 was marked as duplicate of this issue
Collaborator

#101876 was marked as duplicate of this issue

#101876 was marked as duplicate of this issue
Collaborator

#101841 was marked as duplicate of this issue

#101841 was marked as duplicate of this issue
Collaborator

#101349 was marked as duplicate of this issue

#101349 was marked as duplicate of this issue
Collaborator

#100965 was marked as duplicate of this issue

#100965 was marked as duplicate of this issue
Collaborator

#100732 was marked as duplicate of this issue

#100732 was marked as duplicate of this issue
Collaborator

#100517 was marked as duplicate of this issue

#100517 was marked as duplicate of this issue
Collaborator

#100400 was marked as duplicate of this issue

#100400 was marked as duplicate of this issue
Collaborator

Added subscriber: @PratikPB2123

Added subscriber: @PratikPB2123
Collaborator

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

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

Thanks for the report. Please attach the .blend file shown in the picture.
I suspect this is same as #83022 (Transparency in Solid View Causes Glitch Artifacts)

Thanks for the report. Please attach the .blend file shown in the picture. I suspect this is same as #83022 (Transparency in Solid View Causes Glitch Artifacts)
Poster
[tutorial modelado 2.blend](https://archive.blender.org/developer/F13323252/tutorial_modelado_2.blend)
Poster

i think this happen when i add a background image

i think this happen when i add a background image

Added subscriber: @persun

Added subscriber: @persun

I can confirm this. (Windows 10 / RX570 / installed latest driver 22.7.1)

Solid view:

RefImage.png

Render view (corruption is limited to the cube):

RefImage_renderview.png

RefImage.blend

As far as I can see:

  • This happens when reference image's depth setting is set to Back
  • It corrupts viewport overlay drawings like grid, global axes, drawings for camera and light, but transform gizmos are not affected
  • It doesn't matter if view is orthographic or perspective
  • This does not happen in 2.93 and 3.1.2 but happens in 3.2.1 and 3.3
I can confirm this. (Windows 10 / RX570 / installed latest driver 22.7.1) Solid view: ![RefImage.png](https://archive.blender.org/developer/F13323327/RefImage.png) Render view (corruption is limited to the cube): ![RefImage_renderview.png](https://archive.blender.org/developer/F13323338/RefImage_renderview.png) [RefImage.blend](https://archive.blender.org/developer/F13323330/RefImage.blend) As far as I can see: - This happens when reference image's depth setting is set to Back - It corrupts viewport overlay drawings like grid, global axes, drawings for camera and light, but transform gizmos are not affected - It doesn't matter if view is orthographic or perspective - This does not happen in 2.93 and 3.1.2 but happens in 3.2.1 and 3.3
Collaborator

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

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

Thanks for the information. Seems GPU specific issue.
I'll check again with AMD GPU. Resetting the status for now.

Thanks for the information. Seems GPU specific issue. I'll check again with AMD GPU. Resetting the status for now.
Collaborator

Added subscriber: @mano-wii

Added subscriber: @mano-wii
Collaborator

My GPU has been moved by AMD to legacy support so can't update drivers (and with old drivers this issue is not replicable)
@mano-wii, can you check with your AMD GPU: AMD Radeon RX 480

Operating system: Windows-10-10.0.19043-SP0 64 Bits
Graphics card: AMD Radeon(TM) 535 ATI Technologies Inc. 4.5.14831 Core Profile Context 21.5.2 27.20.21003.8013```
My GPU has been moved by AMD to legacy support so can't update drivers (and with old drivers this issue is not replicable) @mano-wii, can you check with your AMD GPU: `AMD Radeon RX 480` ```System Information Operating system: Windows-10-10.0.19043-SP0 64 Bits Graphics card: AMD Radeon(TM) 535 ATI Technologies Inc. 4.5.14831 Core Profile Context 21.5.2 27.20.21003.8013```
Collaborator

Changed status from 'Needs Triage' to: 'Confirmed'

Changed status from 'Needs Triage' to: 'Confirmed'
Collaborator

I can confirm the problem.
It appears to be a recent regression as the same issue is not seen on 0e9367fc29.
I'm not sure if my driver is the latest, I didn't need to update it.
Investigating...


System Information
Operating system: Windows-10-10.0.22000-SP0 64 Bits
Graphics card: Radeon (TM) RX 480 Graphics ATI Technologies Inc. 4.5.0 Core Profile Context 22.20.00.20.220516

I can confirm the problem. It appears to be a recent regression as the same issue is not seen on 0e9367fc29. I'm not sure if my driver is the latest, I didn't need to update it. Investigating... --- **System Information** Operating system: Windows-10-10.0.22000-SP0 64 Bits Graphics card: Radeon (TM) RX 480 Graphics ATI Technologies Inc. 4.5.0 Core Profile Context 22.20.00.20.220516
Collaborator

It's strange, but the problem seems to be introduced in 9015952c9c.
That commit doesn't show anything suspicious.

Actually I got confused with the settings in the preferences. The bug is also seem in old versions

~~It's strange, but the problem seems to be introduced in 9015952c9c.~~ ~~That commit doesn't show anything suspicious.~~ Actually I got confused with the settings in the preferences. The bug is also seem in old versions

Added subscriber: @sycszero

Added subscriber: @sycszero

In #100034#1396454, @persun wrote:
I can confirm this. (Windows 10 / RX570 / installed latest driver 22.7.1)

Solid view:

RefImage.png

Render view (corruption is limited to the cube):

RefImage_renderview.png

RefImage.blend

As far as I can see:

  • This happens when reference image's depth setting is set to Back
  • It corrupts viewport overlay drawings like grid, global axes, drawings for camera and light, but transform gizmos are not affected
  • It doesn't matter if view is orthographic or perspective
  • This does not happen in 2.93 and 3.1.2 but happens in 3.2.1 and 3.3

i have the same problem, with amd 6900xt

> In #100034#1396454, @persun wrote: > I can confirm this. (Windows 10 / RX570 / installed latest driver 22.7.1) > > Solid view: > > ![RefImage.png](https://archive.blender.org/developer/F13323327/RefImage.png) > > Render view (corruption is limited to the cube): > > ![RefImage_renderview.png](https://archive.blender.org/developer/F13323338/RefImage_renderview.png) > > [RefImage.blend](https://archive.blender.org/developer/F13323330/RefImage.blend) > > As far as I can see: > > - This happens when reference image's depth setting is set to Back > - It corrupts viewport overlay drawings like grid, global axes, drawings for camera and light, but transform gizmos are not affected > - It doesn't matter if view is orthographic or perspective > - This does not happen in 2.93 and 3.1.2 but happens in 3.2.1 and 3.3 i have the same problem, with amd 6900xt
Collaborator

Added subscriber: @Jeroen-Bakker

Added subscriber: @Jeroen-Bakker
Collaborator

Looking at the automatic recommendations of AMD driver version 22.5.1 should be used. 22.7.1 is not the preferred drivers (at least for the Vega card I am using)
When using 22.5.1 I don't have this issue.

When selecting optional driver would install 22.7.1 which shows the issue in the driver. For now I will lower the priority as stuff can fail when not using recommended drivers.

If there are recommended setups failing we could raise the issue again.

Looking at the automatic recommendations of AMD driver version 22.5.1 should be used. 22.7.1 is not the preferred drivers (at least for the Vega card I am using) When using 22.5.1 I don't have this issue. When selecting optional driver would install 22.7.1 which shows the issue in the driver. For now I will lower the priority as stuff can fail when not using recommended drivers. If there are recommended setups failing we could raise the issue again.

Added subscriber: @LahceneB

Added subscriber: @LahceneB

I can confirm this as well, driver 22.7.1 using an RX 5600 XT.

image_2022-08-07_202804004.png

I can confirm this as well, driver 22.7.1 using an RX 5600 XT. ![image_2022-08-07_202804004.png](https://archive.blender.org/developer/F13344909/image_2022-08-07_202804004.png)

Did anyone try out the new drivers released today (22.8.1) to see if this issue is fixed?

Did anyone try out the new drivers released today (22.8.1) to see if this issue is fixed?

In #100034#1403233, @LahceneB wrote:
Did anyone try the new drivers release today (22.8.1) to see if this issue is fixed?

I tried, the issue is still there.

> In #100034#1403233, @LahceneB wrote: > Did anyone try the new drivers release today (22.8.1) to see if this issue is fixed? I tried, the issue is still there.
Collaborator

Added subscriber: @Aditya-Raotole

Added subscriber: @Aditya-Raotole

In #100034#1403598, @persun wrote:

In #100034#1403233, @LahceneB wrote:
Did anyone try the new drivers release today (22.8.1) to see if this issue is fixed?

I tried, the issue is still there.

Thanks for the info!

> In #100034#1403598, @persun wrote: >> In #100034#1403233, @LahceneB wrote: >> Did anyone try the new drivers release today (22.8.1) to see if this issue is fixed? > > I tried, the issue is still there. Thanks for the info!

This also happens when you set view clipping region. (Confirmed with 22.7.1 and 22.8.1. Not happening in 22.5.1. So likely the same cause.)

RefImageViewRegion.png

Also I found a workaround for the time being or in case this won't be fixed for a while.

  • Go Preferences > Viewport > Quality > Smooth Wires and uncheck Overlay. Now corruption is limited to selection outlines. Since selection outlines are rarely shown in Edit or Sculpt mode, you probably can work with it

ViewportCorruptionWorkaround.jpg

  • If you really want corruption-free viewport. You can hide selection outlines in viewport overlay settings. Gizmo-based objects (lights, camera) are fine but for meshes, it's really hard to know what's selected without outlines. Instead, turning on wireframe display can help you see that
This also happens when you set view clipping region. (Confirmed with 22.7.1 and 22.8.1. Not happening in 22.5.1. So likely the same cause.) ![RefImageViewRegion.png](https://archive.blender.org/developer/F13387323/RefImageViewRegion.png) Also I found a workaround for the time being or in case this won't be fixed for a while. - Go `Preferences > Viewport > Quality > Smooth Wires` and uncheck `Overlay`. Now corruption is limited to selection outlines. Since selection outlines are rarely shown in Edit or Sculpt mode, you probably can work with it ![ViewportCorruptionWorkaround.jpg](https://archive.blender.org/developer/F13387336/ViewportCorruptionWorkaround.jpg) - If you really want corruption-free viewport. You can hide selection outlines in viewport overlay settings. Gizmo-based objects (lights, camera) are fine but for meshes, it's really hard to know what's selected without outlines. Instead, turning on wireframe display can help you see that

Thanks for the great tip!

Thanks for the great tip!
Collaborator

Added subscriber: @Marcelo_Herrera

Added subscriber: @Marcelo_Herrera
mano-wii changed title from orthographic Mode Bug after AMD Update to Glitches with new AMD drivers (Adrenalin 22.7.1 or 22.8.2) when overlay has transparent images 5 months ago
Collaborator

Added subscriber: @2905710881

Added subscriber: @2905710881
Collaborator

Did some more experiments today. What I did see was that the depth test was is enabled for background images (for under alpha transparency), but there was no depth buffer attached. Attaching one didn't solve the issue. Next week want to add a assert around this case to make sure that Blender warns developers to attach the correct framebuffer.

It could be that previous drivers would reused the last attached depth buffer, but recent drivers unset the depth buffer what lead to reading from uninitialized GPU memory.
Root cause hasn't been found yet.

Did some more experiments today. What I did see was that the depth test was is enabled for background images (for under alpha transparency), but there was no depth buffer attached. Attaching one didn't solve the issue. Next week want to add a assert around this case to make sure that Blender warns developers to attach the correct framebuffer. It could be that previous drivers would reused the last attached depth buffer, but recent drivers unset the depth buffer what lead to reading from uninitialized GPU memory. Root cause hasn't been found yet.
Jeroen-Bakker self-assigned this 5 months ago
Collaborator

Added subscriber: @Revendi

Added subscriber: @Revendi

I would like to note that blender version 2.90.1 does not have this problem.

I would like to note that blender version 2.90.1 does not have this problem.

temporary workaround,
Here is a video,
https://www.youtube.com/watch?v=lEzBYmL0mfM

blender 3.3.0 with AMD DRIVERS 22.9.1

temporary workaround, Here is a video, https://www.youtube.com/watch?v=lEzBYmL0mfM blender 3.3.0 with AMD DRIVERS 22.9.1
Collaborator

Added subscribers: @lunasn0wfall, @deadpin

Added subscribers: @lunasn0wfall, @deadpin
EAW commented 4 months ago

Added subscriber: @Cxstin

Added subscriber: @Cxstin
Collaborator

Added subscriber: @DeltaWave0x

Added subscriber: @DeltaWave0x

In #100034#1421437, @sycszero wrote:
temporary workaround,
Here is a video,
https://www.youtube.com/watch?v=lEzBYmL0mfM

blender 3.3.0 with AMD DRIVERS 22.9.1

Thanks, I hope this workaround will help tracking down the root of the issue.

> In #100034#1421437, @sycszero wrote: > temporary workaround, > Here is a video, > https://www.youtube.com/watch?v=lEzBYmL0mfM > > blender 3.3.0 with AMD DRIVERS 22.9.1 Thanks, I hope this workaround will help tracking down the root of the issue.
Collaborator

Added subscriber: @Orin-3

Added subscriber: @Orin-3
Collaborator

Added subscriber: @YoungStingray03

Added subscriber: @YoungStingray03

This comment was removed by @2905710881

*This comment was removed by @2905710881*

2.1.jpg

This issue seems to have been fixed in the 21.11.1 driver

![2.1.jpg](https://archive.blender.org/developer/F13940309/2.1.jpg) This issue seems to have been fixed in the 21.11.1 driver

In #100034#1447764, @2905710881 wrote:
This issue seems to have been fixed in the 21.11.1 driver

Indeed! From AMD's release notes :

Fixed Issues
OpenGL applications using MSAA may see visual corruption.

> In #100034#1447764, @2905710881 wrote: > This issue seems to have been fixed in the 21.11.1 driver Indeed! From AMD's [release notes ](https://www.amd.com/en/support/kb/release-notes/rn-rad-win-22-11-1): > **Fixed Issues** > OpenGL applications using MSAA may see visual corruption.
Collaborator

@Jeroen-Bakker / @mano-wii , can you also check whether this is fixed in newer AMD driver (see last two comments).

@Jeroen-Bakker / @mano-wii , can you also check whether this is fixed in newer AMD driver (see last two comments).
Collaborator

Added subscriber: @NicoleRu

Added subscriber: @NicoleRu
Collaborator

Changed status from 'Confirmed' to: 'Resolved'

Changed status from 'Confirmed' to: 'Resolved'
mano-wii closed this issue 2 months ago
Collaborator

I can confirm the problem is fixed in driver 21.11.1
It seems like a solution so I'm closing the report.

The report can be reopened if further investigation is required.

I can confirm the problem is fixed in driver 21.11.1 It seems like a solution so I'm closing the report. The report can be reopened if further investigation is required.
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/Collada
Interest/Compositing
Interest/Core
Interest/Cycles
Interest/Dependency Graph
Interest/Development Management
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/Modeling
Interest/Modifiers
Interest/Motion Tracking
Interest/Nodes & Physics
Interest/Overrides
Interest/Performance
Interest/Performance
Interest/Physics
Interest/Pipeline, Assets & I/O
Interest/Platforms, Builds, Tests & Devices
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
legacy module/Animation & Rigging
legacy module/Core
legacy module/Development Management
legacy module/Eevee & Viewport
legacy module/Grease Pencil
legacy module/Modeling
legacy module/Nodes & Physics
legacy module/Pipeline, Assets & IO
legacy module/Platforms, Builds, Tests & Devices
legacy module/Python API
legacy module/Rendering & Cycles
legacy module/Sculpt, Paint & Texture
legacy module/Triaging
legacy module/User Interface
legacy module/VFX & Video
legacy project/1.0.0-beta.2
legacy project/Asset Browser (Archived)
legacy project/BF Blender: 2.8
legacy project/BF Blender: After Release
legacy project/BF Blender: Next
legacy project/BF Blender: Regressions
legacy project/BF Blender: Unconfirmed
legacy project/Blender 2.70
legacy project/Code Quest
legacy project/Datablocks and Libraries
legacy project/Eevee
legacy project/Game Animation
legacy project/Game Audio
legacy project/Game Data Conversion
legacy project/Game Engine
legacy project/Game Logic
legacy project/Game Physics
legacy project/Game Python
legacy project/Game Rendering
legacy project/Game UI
legacy project/GPU / Viewport
legacy project/GSoC
legacy project/Infrastructure: Websites
legacy project/LibOverrides - Usability and UX
legacy project/Milestone 1: Basic, Local Asset Browser
legacy project/Nodes
legacy project/OpenGL Error
legacy project/Papercut
legacy project/Pose Library Basics
legacy project/Retrospective
legacy project/Tracker Curfew
legacy project/Wintab High Frequency
Meta/Good First Issue
Meta/Papercut
migration/requires-manual-verification
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 & Devices
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 Information 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
12 Participants
Notifications
Due Date

No due date set.

Dependencies

No dependencies set.

Reference: blender/blender#100034
Loading…
There is no content yet.