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

New Issue

Omar Enrique Aguilar Aquino · 2022-07-27T23:57:47+02:00

2022-07-27 23:57:47 +02:00

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.

Render view (corruption is limited to the cube):

Exact steps for others to reproduce the error

Open attached .blend file
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

**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)

Omar Enrique Aguilar Aquino commented

2022-07-27 23:57:47 +02:00

Added subscriber: @Corps3

blender-admin commented

2022-07-27 23:57:47 +02:00

#102616 was marked as duplicate of this issue

blender-admin commented

2022-07-27 23:57:47 +02:00

#102559 was marked as duplicate of this issue

blender-admin commented

2022-07-27 23:57:47 +02:00

#102525 was marked as duplicate of this issue

blender-admin commented

2022-07-27 23:57:47 +02:00

#101876 was marked as duplicate of this issue

blender-admin commented

2022-07-27 23:57:47 +02:00

#101841 was marked as duplicate of this issue

blender-admin commented

2022-07-27 23:57:47 +02:00

#101349 was marked as duplicate of this issue

blender-admin commented

2022-07-27 23:57:47 +02:00

#100965 was marked as duplicate of this issue

blender-admin commented

2022-07-27 23:57:47 +02:00

#100732 was marked as duplicate of this issue

blender-admin commented

2022-07-27 23:57:47 +02:00

#100517 was marked as duplicate of this issue

blender-admin commented

2022-07-27 23:57:47 +02:00

#100400 was marked as duplicate of this issue

Pratik Borhade commented

2022-07-28 01:48:26 +02:00

Added subscriber: @PratikPB2123

Pratik Borhade commented

2022-07-28 01:48:26 +02:00

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

Pratik Borhade commented

2022-07-28 01:48:26 +02:00

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)

Omar Enrique Aguilar Aquino commented

2022-07-28 02:48:19 +02:00

tutorial modelado 2.blend

[tutorial modelado 2.blend](https://archive.blender.org/developer/F13323252/tutorial_modelado_2.blend)

Omar Enrique Aguilar Aquino commented

2022-07-28 02:54:38 +02:00

i think this happen when i add a background image

Sun Kim commented

2022-07-28 05:16:21 +02:00

Added subscriber: @persun

Sun Kim commented

2022-07-28 05:16:21 +02:00

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

Solid view:

Render view (corruption is limited to the cube):

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

Pratik Borhade commented

2022-07-28 05:28:01 +02:00

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

Pratik Borhade commented

2022-07-28 05:28:01 +02:00

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.

Pratik Borhade commented

2022-07-29 05:30:39 +02:00

Added subscriber: @mano-wii

Pratik Borhade commented

2022-07-29 05:30:39 +02:00

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

Germano Cavalcante commented

2022-07-29 16:06:36 +02:00

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

Germano Cavalcante commented

2022-07-29 16:06:36 +02:00

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

Germano Cavalcante commented

2022-07-29 20:14:34 +02:00

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

Gcbo commented

2022-08-02 02:17:14 +02:00

Added subscriber: @sycszero

Gcbo commented

2022-08-02 02:19:29 +02:00

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

Solid view:

Render view (corruption is limited to the cube):

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

Jeroen Bakker commented

2022-08-02 12:10:06 +02:00

Added subscriber: @Jeroen-Bakker

Jeroen Bakker commented

2022-08-02 12:10:06 +02:00

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.

Lahcene Belbachir commented

2022-08-07 21:26:07 +02:00

Added subscriber: @LahceneB

Lahcene Belbachir commented

2022-08-07 21:26:07 +02:00

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

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)

Lahcene Belbachir commented

2022-08-12 20:52:01 +02:00

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

Sun Kim commented

2022-08-14 20:16:18 +02:00

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.

Jesse Yurkovich commented

2022-08-14 21:42:24 +02:00

Added subscriber: @Aditya-Raotole

Lahcene Belbachir commented

2022-08-15 00:53:20 +02:00

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!

Sun Kim commented

2022-08-15 14:51:10 +02:00

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

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

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

Lahcene Belbachir commented

2022-08-16 15:26:25 +02:00

Thanks for the great tip!

Jesse Yurkovich commented

2022-08-20 08:30:34 +02:00

Added subscriber: @Marcelo_Herrera

Germano Cavalcante 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

2022-08-31 20:59:34 +02:00

Germano Cavalcante commented

2022-08-31 20:59:48 +02:00

Added subscriber: @2905710881

Jeroen Bakker commented

2022-09-02 15:30:35 +02:00

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 2022-09-02 15:30:45 +02:00

Pratik Borhade commented

2022-09-10 13:01:55 +02:00

Added subscriber: @Revendi

Danil commented

2022-09-10 13:15:22 +02:00

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

Gcbo commented

2022-09-23 08:38:30 +02:00

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

Pratik Borhade commented

2022-09-26 14:33:35 +02:00

Added subscribers: @lunasn0wfall, @deadpin

Evan Wilson commented

2022-10-15 16:29:32 +02:00

Added subscriber: @Cxstin

Pratik Borhade commented

2022-10-17 17:42:09 +02:00

Added subscriber: @DeltaWave0x

Lahcene Belbachir commented

2022-10-19 18:47:50 +02:00

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.

Pratik Borhade commented

2022-11-15 14:19:23 +01:00

Added subscriber: @Orin-3

Germano Cavalcante commented

2022-11-17 15:36:12 +01:00

Added subscriber: @YoungStingray03

周建峰 commented

2022-11-18 08:57:31 +01:00

This comment was removed by @2905710881

*This comment was removed by @2905710881*

周建峰 commented

2022-11-18 08:58:48 +01:00

This issue seems to have been fixed in the 22.11.1 driver

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

Sun Kim commented

2022-11-18 09:05:42 +01:00

In #100034#1447764, @2905710881 wrote:
This issue seems to have been fixed in the 22.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 22.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.

Pratik Borhade commented

2022-11-18 14:14:30 +01:00

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

Pratik Borhade commented

2022-11-27 04:53:39 +01:00

Added subscriber: @NicoleRu

Germano Cavalcante commented

2022-11-30 19:49:43 +01:00

Changed status from 'Confirmed' to: 'Resolved'

Germano Cavalcante closed this issue

2022-11-30 19:49:43 +01:00

Germano Cavalcante commented

2022-11-30 19:49:43 +01:00

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.

Pratik Borhade referenced this issue

2023-02-23 06:09:22 +01:00

Graphical glitch in ortho mode when image has depth of "back" #105087

Jesse Yurkovich referenced this issue

2023-03-18 01:37:33 +01:00

Why this happens? (Fixed) ❤️ #105864

Pratik Borhade referenced this issue

2023-03-21 04:47:36 +01:00

Grid artifacts when adding an image to the background #105934

Sun Kim referenced this issue

2023-03-26 06:28:23 +02:00

Glitch #106137