EEVEE - Adaptive Irradiance Probe #56254

Closed
opened 2018-08-06 23:12:07 +02:00 by Tomasz Muszynski · 5 comments

In many cases, esp. corners of the interior ( at ArchViz scene) there appear problems with proper shadowing of objects by Irradiance Probe..
Eevee needs improvement for the irradinace calculation to avoid invalid light splotches esp. in regions where the single irradiance probe cell is crossing the mesh face.

I would like to propose to implement an Adaptive option to the Irradiance Probe.

  • It could be detect objects proximity somehow ( i.e. like AO is calculated ) to find where the Adaptive subdivision of Probes should be placed
  • user can set maximum the subdivision for the adaptive probes and engine could calculate needed value for specific objects proximity (equal or less to the value set by user ).
  • to avoid huge memory usage Adaptive subdivided probes could be share the memory cell size of the BASIC Irradiance probe ( use 100%-125% of memory of the base irradiance probe cell )
  • there could be an option to place Adaptive probes only at the Front-Face of the object ( to skip placing at the back-face ) - it could be spare some memory used for Adaptive Irradiance
  • to avoid bright light leaks Irradiance cloud have and option to "make backface SOLID FLAT BLACK" to avoid wrong light calculation for example for the inside walls structure of interior ( it is usually solid so do not transfer any light ). I made some tests with material where I set backface as solid black and it really helps for irradiance light leaks at corners.
  • maybe there should be an option to store Bake Lights in external file ( not inside the blend with the scene ).

What do you think about this kind of improvement?

Some crappy image of the idea you can find here: https://blender.community/c/rightclickselect/PTbbbc/eevee-adaptive-irradiance-probe-important

In many cases, esp. corners of the interior ( at ArchViz scene) there appear problems with proper shadowing of objects by Irradiance Probe.. Eevee needs improvement for the irradinace calculation to avoid invalid light splotches esp. in regions where the single irradiance probe cell is crossing the mesh face. I would like to propose to implement an Adaptive option to the Irradiance Probe. - It could be detect objects proximity somehow ( i.e. like AO is calculated ) to find where the Adaptive subdivision of Probes should be placed - user can set maximum the subdivision for the adaptive probes and engine could calculate needed value for specific objects proximity (equal or less to the value set by user ). - to avoid huge memory usage Adaptive subdivided probes could be share the memory cell size of the BASIC Irradiance probe ( use 100%-125% of memory of the base irradiance probe cell ) - there could be an option to place Adaptive probes only at the Front-Face of the object ( to skip placing at the back-face ) - it could be spare some memory used for Adaptive Irradiance - to avoid bright light leaks Irradiance cloud have and option to "make backface SOLID FLAT BLACK" to avoid wrong light calculation for example for the inside walls structure of interior ( it is usually solid so do not transfer any light ). I made some tests with material where I set backface as solid black and it really helps for irradiance light leaks at corners. - maybe there should be an option to store Bake Lights in external file ( not inside the blend with the scene ). What do you think about this kind of improvement? Some crappy image of the idea you can find here: https://blender.community/c/rightclickselect/PTbbbc/eevee-adaptive-irradiance-probe-important
Clément Foucault was assigned by Tomasz Muszynski 2018-08-06 23:12:07 +02:00

Added subscriber: @TomaszMuszynski

Added subscriber: @TomaszMuszynski

Added subscriber: @mont29

Added subscriber: @mont29

Changed status from 'Open' to: 'Archived'

Changed status from 'Open' to: 'Archived'

Thanks for the suggestion, but we do not accept feature requests or suggestions on this tracker (use forums or bf-funboard ML for that).

Thanks for the suggestion, but we do not accept feature requests or suggestions on this tracker (use forums or bf-funboard ML for that).

Ok. Thanks! Understood.
Just remember about this when the team decide to develop Irradiance computation for Eevee.
Current solution is not good for professional ArchViz.
If you need I can send you my test scene with some kitchen to do some tests (it is a real-life project that is going to be build).
https://blender.community/c/today/Xwcbbc/

Ok. Thanks! Understood. Just remember about this when the team decide to develop Irradiance computation for Eevee. Current solution is not good for professional ArchViz. If you need I can send you my test scene with some kitchen to do some tests (it is a real-life project that is going to be build). https://blender.community/c/today/Xwcbbc/
Sign in to join this conversation.
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
2 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#56254
No description provided.