Clipping Region in blender v3.2 and up is causing a werid artifact #101897

New Issue

Mohamad Belal ALKassab · 2022-10-18T13:31:05+02:00

2022-10-18 13:31:05 +02:00

System Information
Operating system: Windows-10-10.0.22000-SP0 64 Bits
Graphics card: AMD Radeon RX 6600M ATI Technologies Inc. 4.5.0 Core Profile Context 22.10.1.221003

Blender Version
Broken: version: 3.3.1, branch: master, commit date: 2022-10-04 18:35, hash: b292cfe5a9
Worked: (newest version of Blender that worked as expected)

Short description of error
weird colorful noise when using Clipping region ALT+B

Exact steps for others to reproduce the error
it happens by simply using the clipping region, it happens in both object mode and edit mode

Diagnosis that I tried (USEFUL NOTES{F13703419} FOR FIXING THE PROBLEM)
what is causing it?:

I noticed that the bug is only on the Viewport Overlays it seems like it's smth related to the graphical smoothing done by "viewport overlay smooth wires" from blender preferences -> viewport -> Quality -> Smooth Wires. I can turn of that for Overlay and for Edit mode, but it's just hiding the problem not fixing it, also the selected objects highlight (active element and not active element) are both still showing the same artifact and I don't know how to turn off smoothing for this part.

is it gpu driver problem?

it most likely is a conflict between blender and my gpu, I don't think it's a driver problem tho because I tried the latest two gpu drivers available from amd, and both of them are showing the same problem. I tried running blender using my integrated gpu and tried my RX6600M gpu and in both cases it happend, I don't know if the smoothing is done on the gpu level or cpu level tho so it could be not related to which gpu I use

What versions of blender does it happen in?

I mainly use blender from steam with auto updates, I noticed the problem when I was using v3.3.1 then I tried few older versions by manually installing them from the offical blender website, the bug doesn't show up in v3.1.2 and v2.79b however it's in showing up in v3.2.0 and v3.3.0 and v3.3.1 -not steam version- I didn't test more versions tho

P.S. my device -Legion 5- has a mux switch, when I did the bug report the mux switch is turned off which means the integrated GPU is disconnected thus it's not showing up in the bug report, however when I tried to check the bug

untitled.blend

**System Information** Operating system: Windows-10-10.0.22000-SP0 64 Bits Graphics card: AMD Radeon RX 6600M ATI Technologies Inc. 4.5.0 Core Profile Context 22.10.1.221003 **Blender Version** Broken: version: 3.3.1, branch: master, commit date: 2022-10-04 18:35, hash: `b292cfe5a9` Worked: (newest version of Blender that worked as expected) **Short description of error** weird colorful noise when using Clipping region ALT+B **Exact steps for others to reproduce the error** it happens by simply using the clipping region, it happens in both object mode and edit mode **Diagnosis that I tried** (USEFUL NOTES{[F13703419](https://archive.blender.org/developer/F13703419/Untitled.png)} FOR FIXING THE PROBLEM) what is causing it?: - I noticed that the bug is only on the Viewport Overlays it seems like it's smth related to the graphical smoothing done by "viewport overlay smooth wires" from blender preferences -> viewport -> Quality -> Smooth Wires. I can turn of that for Overlay and for Edit mode, but it's just hiding the problem not fixing it, also the selected objects highlight (active element and not active element) are both still showing the same artifact and I don't know how to turn off smoothing for this part. is it gpu driver problem? - it most likely is a conflict between blender and my gpu, I don't think it's a driver problem tho because I tried the latest two gpu drivers available from amd, and both of them are showing the same problem. I tried running blender using my integrated gpu and tried my RX6600M gpu and in both cases it happend, I don't know if the smoothing is done on the gpu level or cpu level tho so it could be not related to which gpu I use What versions of blender does it happen in? - I mainly use blender from steam with auto updates, I noticed the problem when I was using v3.3.1 then I tried few older versions by manually installing them from the offical blender website, the bug doesn't show up in v3.1.2 and v2.79b however it's in showing up in v3.2.0 and v3.3.0 and v3.3.1 -not steam version- I didn't test more versions tho P.S. my device -Legion 5- has a mux switch, when I did the bug report the mux switch is turned off which means the integrated GPU is disconnected thus it's not showing up in the bug report, however when I tried to check the bug ![Untitled2.png](https://archive.blender.org/developer/F13703620/Untitled2.png) ![Untitled.png](https://archive.blender.org/developer/F13703623/Untitled.png) ![Untitled3.png](https://archive.blender.org/developer/F13703629/Untitled3.png) ![Untitled4.png](https://archive.blender.org/developer/F13703647/Untitled4.png) [untitled.blend](https://archive.blender.org/developer/F13703650/untitled.blend)

Mohamad Belal ALKassab commented

2022-10-18 13:31:05 +02:00

Added subscriber: @4D374D44

blender-admin commented

2022-10-18 13:31:05 +02:00

#103716 was marked as duplicate of this issue

Pratik Borhade commented

2022-10-18 15:36:48 +02:00

Added subscribers: @persun, @mano-wii, @Jeroen-Bakker, @PratikPB2123

Pratik Borhade commented

2022-10-18 15:36:48 +02:00

Changed status from 'Needs Triage' to: 'Needs Developer To Reproduce'

Pratik Borhade commented

2022-10-18 15:36:48 +02:00

Thanks for the report. This issue is related to newer AMD drivers
@persun also mentioned a similar problem in #100034#1403919
Not sure weather this issue requires a separate report. @mano-wii and @Jeroen-Bakker, can you comment?

Thanks for the report. This issue is related to newer AMD drivers @persun also mentioned a similar problem in #100034#1403919 Not sure weather this issue requires a separate report. @mano-wii and @Jeroen-Bakker, can you comment?

Kevin Chau commented

2022-10-18 20:13:47 +02:00

Added subscriber: @slickeez

Kevin Chau commented

2022-10-18 20:13:49 +02:00

Removed subscriber: @slickeez

Mohamad Belal ALKassab commented

2022-10-18 22:38:39 +02:00

Thanks for the fast reply, so yeah this problem is apparently not showing up when using the recommended AMD driver v22.5.1 -I tested it- as others (jbakker and persun) have pointed out, and it's showing up in driver versions higher than that including AMD pro driver v22.q3

The driver v22.5.1 was released on 28th April, and the latest driver is released on 4th October, so as I've understood the only solution for now is to use the v22.5.1?
Is this a blender problem that blender needs to fix? or is it an AMD problem?

Thanks

Thanks for the fast reply, so yeah this problem is apparently not showing up when using the recommended AMD driver v22.5.1 -I tested it- as others (jbakker and persun) have pointed out, and it's showing up in driver versions higher than that including AMD pro driver v22.q3 The driver v22.5.1 was released on 28th April, and the latest driver is released on 4th October, so as I've understood the only solution for now is to use the v22.5.1? Is this a blender problem that blender needs to fix? or is it an AMD problem? Thanks

Lahcene Belbachir commented

2022-10-19 18:36:32 +02:00

Added subscriber: @LahceneB

Lahcene Belbachir commented

2022-10-19 18:36:32 +02:00

In #101897#1434067, @4D374D44 wrote:
Thanks for the fast reply, so yeah this problem is apparently not showing up when using the recommended AMD driver v22.5.1 -I tested it- as others (jbakker and persun) have pointed out, and it's showing up in driver versions higher than that including AMD pro driver v22.q3

The driver v22.5.1 was released on 28th April, and the latest driver is released on 4th October, so as I've understood the only solution for now is to use the v22.5.1?
Is this a blender problem that blender needs to fix? or is it an AMD problem?

Thanks

It could be a depth buffer issue, apparently they might work differently in recent drivers, as explained here:

https:*developer.blender.org/T100034#1411628

> In #101897#1434067, @4D374D44 wrote: > Thanks for the fast reply, so yeah this problem is apparently not showing up when using the recommended AMD driver v22.5.1 -I tested it- as others (jbakker and persun) have pointed out, and it's showing up in driver versions higher than that including AMD pro driver v22.q3 > > The driver v22.5.1 was released on 28th April, and the latest driver is released on 4th October, so as I've understood the only solution for now is to use the v22.5.1? > Is this a blender problem that blender needs to fix? or is it an AMD problem? > > Thanks It could be a depth buffer issue, apparently they might work differently in recent drivers, as explained here: [https:*developer.blender.org/T100034#1411628 ](https:*developer.blender.org/T100034#1411628)

Pratik Borhade commented

2023-01-09 05:20:55 +01:00

Added subscribers: @IronArm90, @mod_moder

Pratik Borhade commented

2023-01-09 05:22:56 +01:00

Hi, does this issue persist with newer AMD drivers?
Similar problem is fixed in newer drivers: #100034#1447765

Hi, does this issue persist with newer AMD drivers? Similar problem is fixed in newer drivers: #100034#1447765

Philipp Oeser removed the

Download

What's New

Blender Studio

Manual

Developers Blog

Documentation

Benchmark

Blender Conference

Development Fund

One-time Donations

Clipping Region in blender v3.2 and up is causing a werid artifact #101897