EEVEE Next broken normals with "High Quality Normals" / MB & "Smooth by Angle" node #114144

New Issue

Steffen Dünner · 2023-10-25T11:37:09+02:00

Steffen Dünner commented

2023-10-25 11:37:09 +02:00

System Information
Operating system: Linux-6.2.0-35-generic-x86_64-with-glibc2.35 64 Bits, X11 UI
Graphics card: NVIDIA GeForce RTX 2070 Super/PCIe/SSE2 NVIDIA Corporation 4.6.0 NVIDIA 535.104.12

Blender Version
Broken: version: 4.1.0 Alpha, branch: main, commit date: 2023-10-25 08:24, hash: 23e9ebfdbd39
Worked: (newest version of Blender that worked as expected)

Short description of error
Sorry for the lengthy title, but I found a weird looking shading bug with EEVEE Next that only happens with a certain combination of render options / modifiers.
I attached a simple repro scene.
The facetted / destroyed normals only show up if
a) "High Quality Normals" are enabled

b) Motion Blur is enabled in EEVEE Next
c) a "Smooth by Angle" modifier is added

Then you get this:

If one of these 3 prerequisites is not met, the bug disappears:

Exact steps for others to reproduce the error

Open the attached blend file: EEVEE_Next_MB_Bug_v01.blend
Switch the viewport to "Rendered" -> weird result
Now do one of these:
Switch off "Motion Blur" -> all is fine
Switch off "High Quality Normals" -> all is fine
Switch off the "Smooth by Angle" modifier -> all is fine

**System Information** Operating system: Linux-6.2.0-35-generic-x86_64-with-glibc2.35 64 Bits, X11 UI Graphics card: NVIDIA GeForce RTX 2070 Super/PCIe/SSE2 NVIDIA Corporation 4.6.0 NVIDIA 535.104.12 **Blender Version** Broken: version: 4.1.0 Alpha, branch: main, commit date: 2023-10-25 08:24, hash: `23e9ebfdbd39` Worked: (newest version of Blender that worked as expected) **Short description of error** Sorry for the lengthy title, but I found a weird looking shading bug with EEVEE Next that only happens with a certain combination of render options / modifiers. I attached a simple repro scene. The facetted / destroyed normals only show up if a) "High Quality Normals" are enabled ![image](/attachments/fd5dfd82-4f28-4973-ad00-75757f9248ae) b) Motion Blur is enabled in EEVEE Next c) a "Smooth by Angle" modifier is added Then you get this: ![image](/attachments/40fafc4f-e885-4841-bad9-800ed3c90e37) If one of these 3 prerequisites is not met, the bug disappears: ![image](/attachments/7122e5b6-d6e6-472c-bb4f-8fd712914f65) **Exact steps for others to reproduce the error** - Open the attached blend file: [EEVEE_Next_MB_Bug_v01.blend](/attachments/5cda83bc-7a7b-46b3-a79d-37098546da9a) - Switch the viewport to "Rendered" -> weird result Now do one of these: - Switch off "Motion Blur" -> all is fine - Switch off "High Quality Normals" -> all is fine - Switch off the "Smooth by Angle" modifier -> all is fine

EEVEE_Next_MB_Bug_v01.blend

133 KiB

image.png

1.6 MiB

image.png

929 KiB

image.png

3.8 KiB

Steffen Dünner added the

Type

Report

Priority