I've got 2 issues when trying to render caustics with the cache and light tracing.
First issue is the fireflies. These paths really should be disabled because the caustics are handled by both the cache and light tracing, but there presence make my renders basically unusable.
Second issue is that the brightness of the caustics doesn't seem to be correct. The material of the cube is 100% reflective, so the caustic and reflection of the caustic should be the same brightness, yet the reflection is noticeably brighter. This may be an issue with the metropolis estimation, but I'm not entirely sure about it
The scene attached below used a daily build from a day ago, and a daily build of Blender 2.90
Caustic issues
Forum rules
Please upload a testscene that allows developers to reproduce the problem, and attach some images.
Please upload a testscene that allows developers to reproduce the problem, and attach some images.
- Theo_Gottwald
- Posts: 109
- Joined: Fri Apr 24, 2020 12:01 pm
Re: Caustic issues
In Blender 2.9 i have several issues, especially crashes when using Mantaflow, but also with Luxcore.
So i recommend to stick - at least when there are problems - with 2.83.
So i recommend to stick - at least when there are problems - with 2.83.
Get Blender-Quickbuttons and configure over 100 Blender-Buttons individual to your needs.
Visit my YouTube-Channel: Theo's Fun Videos and watch several Blender related Videos.
Join @Dreamstime and sell your Renderings to the world.
Visit my YouTube-Channel: Theo's Fun Videos and watch several Blender related Videos.
Join @Dreamstime and sell your Renderings to the world.
-
- Posts: 47
- Joined: Tue Apr 17, 2018 1:07 pm
Re: Caustic issues
These issues persist when using 2.83
This isn't an issue with blender, it's an issue with LuxCore
This isn't an issue with blender, it's an issue with LuxCore
Re: Caustic issues
I suspect it's the Light Tracing, but I can't really speak to that.jgrover110 wrote: ↑Mon Jul 13, 2020 10:51 am First issue is the fireflies. These paths really should be disabled because the caustics are handled by both the cache and light tracing, but there presence make my renders basically unusable.
I get the same result as you. Blender 2.83, LuxCore 2.4 beta 1jgrover110 wrote: ↑Mon Jul 13, 2020 10:51 am Second issue is that the brightness of the caustics doesn't seem to be correct. The material of the cube is 100% reflective, so the caustic and reflection of the caustic should be the same brightness, yet the reflection is noticeably brighter. This may be an issue with the metropolis estimation, but I'm not entirely sure about it
If I use PhotonGI only (no Light Tracing), at 12K samples, the brightness is equal, although it does seem like it might be a little too bright overall?
If I disable the PhotonGI cache and use Light Tracing, the result is still quite noisy at 12K samples; the brightness is equal.
If I disable the Light Tracing as well (pure path tracing), the brightness is equal, although a little noisier at 12K samples.
With BiDir Metropolis at 2K samples I get almost the correct brightness, it's just a little brighter in the reflection.
With BiDir Sobol at 2K samples I get equal brightness, it's just... very noisy and will take a long time to converge.
Conclusion:
In 2 of the 3 cases where Metropolis was used (BiDir, Light Tracing + PhotonGI) the brightness was not equal. However, when Light Tracing was used on its own, the brightness was equal.
With Light Tracing + PhotonGI the result feels quite like their contributions are additive, so you get the brightness from PhotonGI, plus the brightness from Light Tracing.
Hope this helps
AMD Ryzen Threadripper PRO 5995WX 64-Cores | 2x Gigabyte RTX 4090 Gaming OC
ASUS Pro WS WRX80E-SAGE SE WIFI | 256GB Kingston Server Premier ECC Unbuffered DDR4
ASUS Pro WS WRX80E-SAGE SE WIFI | 256GB Kingston Server Premier ECC Unbuffered DDR4