EEVEE shadow artifacts on some meshes #124080

Closed
opened 2024-07-03 08:14:07 +02:00 by ^~^ · 7 comments

System Information
Operating system: Windows-10-10.0.19045-SP0 64 Bits
Graphics card: NVIDIA GeForce GTX 1660 SUPER/PCIe/SSE2 NVIDIA Corporation 4.6.0 NVIDIA 555.99

Blender Version
Broken: version: 4.2.0 Beta, branch: blender-v4.2-release, commit date: 2024-07-02 18:32, hash: edd1749e2222

Short Description
EEVEE render artifacts with shadow render

Steps to Reproduce

  • Open attached .blend file
  • Switch to EEVEE viewport render
  • Enable shadow

test.blend

**System Information** Operating system: Windows-10-10.0.19045-SP0 64 Bits Graphics card: NVIDIA GeForce GTX 1660 SUPER/PCIe/SSE2 NVIDIA Corporation 4.6.0 NVIDIA 555.99 **Blender Version** Broken: version: 4.2.0 Beta, branch: blender-v4.2-release, commit date: 2024-07-02 18:32, hash: `edd1749e2222` **Short Description** EEVEE render artifacts with shadow render **Steps to Reproduce** - Open attached .blend file - Switch to EEVEE viewport render - Enable shadow [test.blend](https://projects.blender.org/attachments/d5ad0a16-4b89-4770-9f15-00c47fc738ac)
^~^ added the
Type
Report
Severity
Normal
Status
Needs Triage
labels 2024-07-03 08:14:07 +02:00
Member

Hi, thanks for the report. Can you attach the affected .blend file?

Hi, thanks for the report. Can you attach the affected .blend file?
Pratik Borhade added
Status
Needs Information from User
and removed
Status
Needs Triage
labels 2024-07-03 08:52:28 +02:00
Member
Hidden to cleanup comments

Also @hornpub please follow the bug report template for future bug reports. That includes providing a working verison of Blender (if there is one and you have the time to test for it), a short description of the issue, and the steps to reproduce.


And once agian, please don't tag people (E.g. developers like Clément) unless it is neccesary or helpful (E.g. Tagging a developer because of a regression in a change they made).

If you know the issue is a regression from a change caused by a specific developer, please include that information in your report (E.g. A link to the change that caused the issue) rather than just tagging the developer.

<details> <summary>Hidden to cleanup comments</summary> Also @hornpub please follow the bug report template for future bug reports. That includes providing a working verison of Blender (if there is one and you have the time to test for it), a short description of the issue, and the steps to reproduce. --- And [once agian](https://projects.blender.org/blender/blender/issues/123937#issuecomment-1227230), please don't tag people (E.g. developers like Clément) unless it is neccesary or helpful (E.g. Tagging a developer because of a regression in a change they made). If you know the issue is a regression from a change caused by a specific developer, please include that information in your report (E.g. A link to the change that caused the issue) rather than just tagging the developer. </details>
Author
Hidden to cleanup comments

Also @hornpub please follow the bug report template for future bug reports. That includes providing a working verison of Blender (if there is one and you have the time to test for it), a short description of the issue, and the steps to reproduce.


And once agian, please don't tag people (E.g. developers like Clément) unless it is neccesary or helpful (E.g. Tagging a developer because of a regression in a change they made).

If you know the issue is a regression from a change caused by a specific developer, please include that information in your report (E.g. A link to the change that caused the issue) rather than just tagging the developer.

<details> <summary>Hidden to cleanup comments</summary> > Also @hornpub please follow the bug report template for future bug reports. That includes providing a working verison of Blender (if there is one and you have the time to test for it), a short description of the issue, and the steps to reproduce. > > --- > > And [once agian](https://projects.blender.org/blender/blender/issues/123937#issuecomment-1227230), please don't tag people (E.g. developers like Clément) unless it is neccesary or helpful (E.g. Tagging a developer because of a regression in a change they made). > > If you know the issue is a regression from a change caused by a specific developer, please include that information in your report (E.g. A link to the change that caused the issue) rather than just tagging the developer. </details>
1.8 MiB
Author

Hi, thanks for the report. Can you attach the affected .blend file?

sure here it is 🙂

> Hi, thanks for the report. Can you attach the affected .blend file? sure here it is 🙂
Member

With the file provided, I can confirm the issue. Marking as confirmed and setting to high priority as it is a regression from 4.1 EEVEE.

With the file provided, I can confirm the issue. Marking as confirmed and setting to high priority as it is a regression from 4.1 EEVEE.
Alaska added this to the 4.2 LTS milestone 2024-07-03 13:36:20 +02:00
Alaska changed title from EEVEE | shadow to EEVEE shadow artifacts on some meshes 2024-07-03 13:36:33 +02:00
Member

Can confirm as well

Can confirm as well

This is unfortunately a limitation of the shadow maps. These are aliasing artifacts that we correct for slopped surfaces but cannot remove on faces directly perpendicular to the light itself surrounded by slopped faces.

You can mitigate the issue by:

  • Increasing the resolution (reducing the shadow Resolution Limit parameter).
  • Changing the shadow Filter size (but that can just change the appearance of the artifact, not remove it completely).
This is unfortunately a limitation of the shadow maps. These are aliasing artifacts that we correct for slopped surfaces but cannot remove on faces directly perpendicular to the light itself surrounded by slopped faces. You can mitigate the issue by: - Increasing the resolution (reducing the shadow `Resolution Limit` parameter). - Changing the shadow `Filter` size (but that can just change the appearance of the artifact, not remove it completely).
Blender Bot added
Status
Archived
and removed
Status
Confirmed
labels 2024-07-03 14:01:54 +02:00
Clément Foucault added
Type
Known Issue
and removed
Type
Report
labels 2024-07-03 14:02:03 +02:00
Sign in to join this conversation.
No Label
Interest
Alembic
Interest
Animation & Rigging
Interest
Asset System
Interest
Audio
Interest
Automated Testing
Interest
Blender Asset Bundle
Interest
BlendFile
Interest
Collada
Interest
Compatibility
Interest
Compositing
Interest
Core
Interest
Cycles
Interest
Dependency Graph
Interest
Development Management
Interest
EEVEE
Interest
Freestyle
Interest
Geometry Nodes
Interest
Grease Pencil
Interest
ID Management
Interest
Images & Movies
Interest
Import Export
Interest
Line Art
Interest
Masking
Interest
Metal
Interest
Modeling
Interest
Modifiers
Interest
Motion Tracking
Interest
Nodes & Physics
Interest
OpenGL
Interest
Overlay
Interest
Overrides
Interest
Performance
Interest
Physics
Interest
Pipeline, Assets & IO
Interest
Platforms, Builds & Tests
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
Viewport & EEVEE
Interest
Virtual Reality
Interest
Vulkan
Interest
Wayland
Interest
Workbench
Interest: X11
Legacy
Asset Browser Project
Legacy
Blender 2.8 Project
Legacy
Milestone 1: Basic, Local Asset Browser
Legacy
OpenGL Error
Meta
Good First Issue
Meta
Papercut
Meta
Retrospective
Meta
Security
Module
Animation & Rigging
Module
Core
Module
Development Management
Module
Grease Pencil
Module
Modeling
Module
Nodes & Physics
Module
Pipeline, Assets & IO
Module
Platforms, Builds & Tests
Module
Python API
Module
Render & Cycles
Module
Sculpt, Paint & Texture
Module
Triaging
Module
User Interface
Module
VFX & Video
Module
Viewport & EEVEE
Platform
FreeBSD
Platform
Linux
Platform
macOS
Platform
Windows
Severity
High
Severity
Low
Severity
Normal
Severity
Unbreak Now!
Status
Archived
Status
Confirmed
Status
Duplicate
Status
Needs Info 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
4 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: blender/blender#124080
No description provided.