EEVEE-Next Horizon Based Global Illumination #112979

New Issue

Clément Foucault · 2023-09-27T21:52:08+02:00

Clément Foucault commented

2023-09-27 21:52:08 +02:00

Motivation

The output of ray-tracing of diffuse or high roughness glossy material is too noisy to get denoised properly and leads to too many flickering and high performance impact. We should switch to a different radiance reconstruction method for those surface.

Implementation

The idea is to use a horizon scan algorithm to take into account all samples taken in the radiance calculation. We can reuse the same samples for both diffuse and glossy BSDFs.

The result should blend into the raytrace radiance.
Glossy pixels should blend between both method depending on roughness.

Tracing should be done only once for all Closures to avoid the cost of tracing over this scan.

Should scan the entire screen if possible.

Python API

Old properties refer specifically to GTAO (gtao_distance, use_gtao_bent_normal). We should rename them to use horizon_scan or (ambient_occlusion when it makes sense) while keeping the old properties for compatibility reasons and mark them as deprecated.

Move gtao_distance to view layer property and rename ambient_occlusion_distance

Tasks

#114150 Core loop logic
#114150 Port AO Pass
#114259 Add pass in Raytrace module
#114259 Add horizon scan to raytracing module

Future

Speed up scan using caching approach like Line Sweep Ambient Occlusion.
Port AO Node (need to support inverted AO, which currently produces artifacts with the new method).

References

Horizon-Based Indirect Lighting
Screen Space Indirect Lighting with Visibility Bitmask

## Motivation The output of ray-tracing of diffuse or high roughness glossy material is too noisy to get denoised properly and leads to too many flickering and high performance impact. We should switch to a different radiance reconstruction method for those surface. ## Implementation The idea is to use a horizon scan algorithm to take into account all samples taken in the radiance calculation. We can reuse the same samples for both diffuse and glossy BSDFs. The result should blend into the raytrace radiance. Glossy pixels should blend between both method depending on roughness. Tracing should be done only once for all Closures to avoid the cost of tracing over this scan. Should scan the entire screen if possible. ## Python API Old properties refer specifically to GTAO (`gtao_distance`, `use_gtao_bent_normal`). We should rename them to use `horizon_scan` or (`ambient_occlusion` when it makes sense) while keeping the old properties for compatibility reasons and mark them as deprecated. - [ ] Move `gtao_distance` to view layer property and rename `ambient_occlusion_distance` ## Tasks - [x] #114150 Core loop logic - [x] #114150 Port AO Pass - [x] #114259 Add pass in `Raytrace` module - [x] #114259 Add horizon scan to raytracing module ## Future - Speed up scan using caching approach like Line Sweep Ambient Occlusion. - Port AO Node (need to support inverted AO, which currently produces artifacts with the new method). ## References [Horizon-Based Indirect Lighting](https://github.com/Patapom/GodComplex/blob/master/Tests/TestHBIL/2018%20Mayaux%20-%20Horizon-Based%20Indirect%20Lighting%20(HBIL).pdf) [Screen Space Indirect Lighting with Visibility Bitmask](https://arxiv.org/pdf/2301.11376.pdf)

Clément Foucault added the

Type

To Do

label 2023-09-27 21:52:08 +02:00

Clément Foucault added this to the EEVEE & Viewport project 2023-09-27 21:52:10 +02:00

Clément Foucault referenced this issue

2023-09-27 21:52:42 +02:00

EEVEE-Next #93220

Clément Foucault added the