Lumen icon indicating copy to clipboard operation
Lumen copied to clipboard

A Vulkan Raytracing framework for various bidirectional path tracing techniques

Results 7 Lumen issues
Sort by recently updated
recently updated
newest added

I try to render scenes\cornell_box\cornell_box_dir.json ![image](https://github.com/yuphin/Lumen/assets/3808839/e9e73adf-543c-4668-8251-ba4b7eebfc12) when I change glass sphere material to "type": "dielectric" I have different image ![image](https://github.com/yuphin/Lumen/assets/3808839/76f9d583-7101-485d-ae9f-f8da7c4855ee) i.e. roughness = 0.0 why images are different?

Compared to 2022 drivers, the current version of the VCM algorithm seems a lot slower (~%50% !). Investigate why.

Enough time : ) This does not really affect me.

Yeah, it might be a Mitsuba question. I took scenes/classroom/scene.xml and added the following: ``` ``` There didn't seem to be new lights in the rendering. scenes\bedroom\scene.xml contains 2 area...

Lumen.exe scenes/bedroom/scene.xml - Path: Bright sky through the window behind the curtain - **BDPT/VCM/ReSTIRGI: Black sky** Thanks.

- remove shader compiler in code. Use precompiled spv - use rayQuery pipeline, not RayTracing pipeline. RayQuery is faster and easy to use