EEVEE-Next: Plane Probe "Display Data" doesn't work properly #119800
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
4 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: blender/blender#119800
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 11
Graphics card: 4060ti
Blender Version
Broken: 4.2.0 Alpha 2024-03-22
Worked: Not sure, but it did work before.
Short description of error
Plane probe does not work at all by default.
(Planar probes are evaluated during raytracing and requires at least screen tracing. So that works as intended and is not considered a bug.)
Turning Display Data on shows it in a very buggy way, especially in Material Preview/with a background.
Turning Ray Tracing makes it work properly, albeit with a blurry reflection based on the settings.
Turning Display Data and Ray Tracing on makes it flicker between the blurry reflection and the broken one.
Exact steps for others to reproduce the error
Make a simple scene utilizing a Plane Probe and you should see the issue.
Just to make the process quicker (and to ensure we are all on the same page): could you please share your example .blend file where this is already set up?
Tried to leave the camera at a position where the reflection freaks out.
Seems like planar probes are not reset when viewport changes but seems to only effect the debug option. This part is a bug.
Planar probes are evaluated during raytracing and requires at least screen tracing. So that works as intended and is not considered a bug.
EEVEE-Next: Plane Probe doesn't work properlyto EEVEE-Next: Plane Probe "Display Data" doesn't work properlyThx checking @Jeroen-Bakker , changed title and description accordingly
There is also an issue with the depth test. I could reproduce it when the = display (debug) buffer gets outside the viewport... When this happens the debug view isn't drawn due to failing depth tests.
The depth bias issue has been fixed and checked with Clement how to solve this issue.
@fclem @Jeroen-Bakker : since part of the issue described here was apparently discarded based on false assumptions (that probes always need raytracing enabled), do we need to reopen this?
Sorry, I was under the assumption we were talking about sphere light-probes. Planar Light-probes do need raytracing and are not compatible with Blended materials.