Intel GPU: Shadows stop working properly when changing render pass in viewport #109269

New Issue

Félix Vallières · 2023-06-23T03:08:04+02:00

Félix Vallières commented

2023-06-23 03:08:04 +02:00

System Information
Operating system: Windows-10-10.0.19044-SP0 64 Bits
Graphics card: Intel(R) UHD Graphics 620 Intel 4.5.0 - Build 30.0.101.1404

Blender Version
Broken: version: 3.5.1, branch: blender-v3.5-release, commit date: 2023-04-24 18:11, hash: e1ccd9d4a1d3
Worked: (newest version of Blender that worked as expected)

Short description of error
When doing a certain shading setup and changing render pass, the shadows break.

Exact steps for others to reproduce the error

Create a new project, keeping the render engine to eevee
Make a new material and apply on default cube
Connect any image texture into the color input of principled bsdf
Connect any image texture into the normal input of principled bsdf while setting its color space to non-color
Switch viewport shading to rendered
Switch render pass to shadow and then back to combined
The lights will now not produce any light unless their shadow setting is turned off

Any other nodes added before or in-between the image texture node do not seem to affect the result.
The shadows will stay like this until blender is closed and reopened again.

**System Information** Operating system: Windows-10-10.0.19044-SP0 64 Bits Graphics card: Intel(R) UHD Graphics 620 Intel 4.5.0 - Build 30.0.101.1404 **Blender Version** Broken: version: 3.5.1, branch: blender-v3.5-release, commit date: 2023-04-24 18:11, hash: `e1ccd9d4a1d3` Worked: (newest version of Blender that worked as expected) **Short description of error** When doing a certain shading setup and changing render pass, the shadows break. **Exact steps for others to reproduce the error** - Create a new project, keeping the render engine to eevee - Make a new material and apply on default cube - Connect any image texture into the color input of principled bsdf - Connect any image texture into the normal input of principled bsdf while setting its color space to non-color - Switch viewport shading to rendered - Switch render pass to shadow and then back to combined - The lights will now not produce any light unless their shadow setting is turned off Any other nodes added before or in-between the image texture node do not seem to affect the result. The shadows will stay like this until blender is closed and reopened again.

Capture d’écran 2023-06-22 210514.png

99 KiB

Glitch Shadow.blend

873 KiB

Félix Vallières added the

labels 2023-06-23 03:08:05 +02:00

Pratik Borhade commented

2023-06-23 05:46:21 +02:00

Hi, thanks for the report. Unable to confirm the problem.
Could you check again in 3.6-beta?: https://builder.blender.org/download/daily/
See whether updaing iGPU driver makes any difference: https://www.intel.in/content/www/in/en/support/products/96551/graphics/intel-hd-graphics-family/intel-hd-graphics-620.html

**System Information**
Operating system: Windows-10-10.0.22000-SP0 64 Bits
Graphics card: NVIDIA GeForce RTX 3050 Laptop GPU/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 532.03

Hi, thanks for the report. Unable to confirm the problem. Could you check again in 3.6-beta?: https://builder.blender.org/download/daily/ See whether updaing iGPU driver makes any difference: https://www.intel.in/content/www/in/en/support/products/96551/graphics/intel-hd-graphics-family/intel-hd-graphics-620.html ``` **System Information** Operating system: Windows-10-10.0.22000-SP0 64 Bits Graphics card: NVIDIA GeForce RTX 3050 Laptop GPU/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 532.03 ```

Pratik Borhade added

Status

Needs Information from User

and removed

Status

Needs Triage

labels 2023-06-23 05:46:30 +02:00

YimingWu commented

2023-06-23 06:35:25 +02:00

I'm not able to reproduce this problem on a intel i7 UHD 620 (Windows and Linux) or an NVidia K5100M (Linux).

It could be possibly glitches in shader compilation where it may somehow go out of sync with viewport refreshing. Is the problem 100% reproducible? Could you try blender_debug_gpu.cmd and blender_debug_gpu_workaround.cmd to log GPU-related errors? (As indicated here) Thanks!

I'm not able to reproduce this problem on a intel i7 UHD 620 (Windows and Linux) or an NVidia K5100M (Linux). It could be possibly glitches in shader compilation where it may somehow go out of sync with viewport refreshing. Is the problem 100% reproducible? Could you try `blender_debug_gpu.cmd` and `blender_debug_gpu_workaround.cmd` to log GPU-related errors? ([As indicated here](https://docs.blender.org/manual/en/3.6/troubleshooting/crash.html#windows)) Thanks!

Félix Vallières commented

2023-06-23 07:14:27 +02:00

Hi, I was able to reproduce it multiple time trying to figure out what nodes caused the issue. I am going to sleep soon so I will attempt what you have suggested when I wake up.

Félix Vallières commented

2023-06-23 19:36:33 +02:00

Here are the results from blender_debug_gpu.cmd and blender_debug_gpu_workaround.cmd as demanded.

These were performed on the same blend file given earlier.

Hopefully these help figure out what's causing this.

Here are the results from `blender_debug_gpu.cmd` and `blender_debug_gpu_workaround.cmd` as demanded. These were performed on the same blend file given earlier. Hopefully these help figure out what's causing this.

blender_debug_gpu_glitchworkaround.zip

15 KiB

blender_debug_gpu.zip

7.1 KiB

👍 1

Pratik Borhade added

Status

Needs Triage

and removed

Status

Needs Information from User

labels 2023-06-24 06:17:49 +02:00

sentharn commented

2023-08-08 02:44:59 +02:00

I can confirm this on my Arc A770 on Windows 11, using Blender 3.6.1, using the provided file. All that is needed is to open it, go to Shading workspace (maybe unnecessary), flip from Combined to Shadow, and then back to Combined render layer in the viewport.

I am using latest beta driver version 31.0.101.4578

System info and screenshot attached for this bug report and confirmation. As well as debug info from running debug with glitch workaround.

I'm reproducing a similar bug on a private project but don't have enough info to create a bug report. My project appears to be triggered by enabling a hair system when there's heavy texture/geometry usage, or by adding too many shader nodes to a tree. Flipping render layers doesn't work and my project actually works with debug workarounds.

The final look of the bug is the same but the path to get to it is probably different. Triggering the above bug and then opening my project results in the same lightless look, interestingly. I suspect intel opengl or graphics compiler implementation...just whining...

I can confirm this on my Arc A770 on Windows 11, using Blender 3.6.1, using the provided file. All that is needed is to open it, go to Shading workspace (maybe unnecessary), flip from Combined to Shadow, and then back to Combined render layer in the viewport. I am using latest beta driver version 31.0.101.4578 System info and screenshot attached for *this* bug report and confirmation. As well as debug info from running debug with glitch workaround. I'm reproducing a similar bug on a private project but don't have enough info to create a bug report. My project appears to be triggered by enabling a hair system when there's heavy texture/geometry usage, or by adding too many shader nodes to a tree. Flipping render layers doesn't work and my project actually works with debug workarounds. The final look of the bug is the same but the path to get to it is probably different. Triggering the above bug and then opening my project results in the same lightless look, interestingly. I suspect intel opengl or graphics compiler implementation...just whining...

system-info.txt

19 KiB

blender_debug_output.txt

2.6 MiB

shadow_bug.jpg

138 KiB

Philipp Oeser added the

Download

What's New

Blender Studio

Manual

Developers Blog

Documentation

Benchmark

Blender Conference

Development Fund

One-time Donations

Intel GPU: Shadows stop working properly when changing render pass in viewport #109269