visual glitch when using high bitdepth in eevee #81941
Labels
No Label
Interest
Alembic
Interest
Animation & Rigging
Interest
Asset Browser
Interest
Asset Browser Project Overview
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
EEVEE & Viewport
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
Virtual Reality
Interest
Vulkan
Interest
Wayland
Interest
Workbench
Interest: X11
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
EEVEE & Viewport
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
Platform
FreeBSD
Platform
Linux
Platform
macOS
Platform
Windows
Priority
High
Priority
Low
Priority
Normal
Priority
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
3 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: blender/blender#81941
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
System Information
Operating system: Windows-10-10.0.19041-SP0 64 Bits
Graphics card: AMD Radeon RX 5700 XT ATI Technologies Inc. 4.5.13587 Core Profile Context 20.4.2 26.20.15029.27017
Blender Version
Broken: version: 2.91.0 Alpha, branch: master, commit date: 2020-10-19 16:47, hash:
3d26cd01b9
Short description of error
If high bitdepth shadows are enabled in eevee you get weird artifacs near lights
Exact steps for others to reproduce the error
I haven't found if this is a know issue/limitation, so sorry if it is.
with high bitdepth enabled:
without high bitdepth enabled:
Note that small changes in the light power can make a huge difference:
Also note that the artifact doesnt only happen below the lamp, it also happens on the sides
highbitglitch.blend
Added subscriber: @Diogo_Valadares
Added subscribers: @fclem, @mano-wii
I don't know if it includes this, but according to the manual, shadows can produce artifacts.
This is a reason for having configurable values for
Clip Start
andBias
. (https://docs.blender.org/manual/en/dev/render/eevee/lighting.html#common-parameters)I think this is a limitation due to finite-precision or floating-point arithmetic in general.
@fclem, is this a bug or limitation?
Yes, changing those values seems to fix the problem, I couldn't find the reason why it was being caused as I only looked on this page of the manual: https://docs.blender.org/manual/en/latest/render/eevee/render_settings/shadows.html
thanks for the explanation ^^
Changed status from 'Needs Triage' to: 'Archived'
Your clip start is way too small for the space the light covers, hence the glitch. So nothing abnormal here.