Page 10 of 11

Re: PhotonGI caustic cache re-factoring

Posted: Fri Nov 01, 2019 12:21 pm
by lacilaci
epilectrolytics wrote: Fri Nov 01, 2019 12:19 pm
lacilaci wrote: Fri Nov 01, 2019 12:14 pm What is samples per step?
That's the cache update period (path sample count between updates).
well then the "cache update period" or something like "compute each (#pass)" name could be a bit better maybe. But I don't know.

PGI indirect + caustic incompatibility

Posted: Sun Nov 03, 2019 4:44 pm
by epilectrolytics
I'm trying to use indirect together with caustic (Hybrid+SDS) cache but it won't work.
When both are activated, no indirect cache is written and the render looks like direct light only.
Screenshot.jpg
Now it is possible to disable caustic cache, render and save persistent indirect cache and then activate caustic cache again and render from saved cache file.
This works for indirect light but the caustics are not updated any more as if persistent indirect cache somehow prohibits caustic cache update.

Are those caches properly decoupled in the persistent file?
I remember that in the original version they were stored together.
Now with vertex merging there is no reason to store a caustic cache file any more so it should be excluded from the persistent file and be generated during rendering independently.

Re: PGI indirect + caustic incompatibility

Posted: Mon Nov 04, 2019 9:45 am
by Dade
epilectrolytics wrote: Sun Nov 03, 2019 4:44 pm I'm trying to use indirect together with caustic (Hybrid+SDS) cache but it won't work.
When both are activated, no indirect cache is written and the render looks like direct light only.
I should have fixed this problem.
epilectrolytics wrote: Sun Nov 03, 2019 4:44 pm This works for indirect light but the caustics are not updated any more as if persistent indirect cache somehow prohibits caustic cache update.
I should have fixed this problem too (the update parameter wasn't saved).

Re: PGI indirect + caustic incompatibility

Posted: Mon Nov 04, 2019 3:27 pm
by epilectrolytics
Dade wrote: Mon Nov 04, 2019 9:45 am I should have fixed this problem too (the update parameter wasn't saved).
Yep, now everything works, thanks!

Only when reading from persistent file with different settings than it was written with (enabled/disabled caches) I get weird results but that is to be expected.

Re: PGI indirect + caustic incompatibility

Posted: Mon Nov 04, 2019 3:59 pm
by Dade
epilectrolytics wrote: Mon Nov 04, 2019 3:27 pm Only when reading from persistent file with different settings than it was written with (enabled/disabled caches) I get weird results but that is to be expected.
Yes, you could literally use a cache file with a totally different scene and get some very very strange result but it is expected. It could be used for some mind blowing VFX but it would be a bit extreme :mrgreen:

Re: PhotonGI caustic cache re-factoring

Posted: Sun Dec 08, 2019 1:51 pm
by anotherbobby
kintuX wrote: Tue Oct 01, 2019 10:46 pm It really feels good, better than PSR. 8-)
Took latest daily for a spin. Nothing special, pool test scene with few changes. Didn't found any problems. :?

pooltester.jpg

LuxCore Scene: pooltester.7z

@ 2040x1080px went up to 2200 samples in 900sec (15min).

Q: Is there an option to use OIDN within LuxCoreUI?
Hi,
Tried to convert this scene into Blender 2.82 Alpha, LuxCore 2.3 Alpha0

Re: PhotonGI caustic cache re-factoring

Posted: Sun Dec 08, 2019 7:27 pm
by epilectrolytics
anotherbobby wrote: Sun Dec 08, 2019 1:51 pm Hi,
Tried to convert this scene into Blender 2.82 Alpha, LuxCore 2.3 Alpha0
Thanks, really a great demo scene by kintuX!

pool animation

Posted: Wed Dec 11, 2019 5:21 pm
by epilectrolytics
And here is an animation (without dispersion).
Took 5min48s per frame on two RTX 2070 (1000 samples + OIDN).

That means complete caustics with SDS can now be animated in LuxCore which is totally awesome!

The old firefly problem is still there (look at the water in the shadow), not much of a problem in this dynamic setting but still scenes like the wallpaper scene take very long to converge.
Clamping is no good option as it diminishes the bright parts of the caustics as well.

But this is a minor issue, caustic cache is already well usable as it is.

I used a displacement modifyer with an upwards moving noise texture for the ripples.
Once the displacement already implemented in Luxcore is exposed in Blender this could be done within the Luxcore material system.

Re: PhotonGI caustic cache re-factoring

Posted: Fri Jan 17, 2020 6:40 am
by Fox
Was studying the caustic cache, thought i share the results.
Caustic cache sss vol tests.jpg

Re: PhotonGI caustic cache re-factoring

Posted: Fri Jan 17, 2020 10:23 am
by lacilaci
Oh god, volumes inside glass are absolutely horrible in luxcore (maybe in other renderers too) there needs to be a "convincing" looking way of handling such situations.
Right we have a fix for glass (shadow color), but roughglass is dark(let's pray multiscatter ggx in future disney will fix this) and any liquid in glass will have a terrible time looking convincing.

there needs to be a cheap way for quick sss features like wax, skin, ice, juices in glass etc... Cause now we're setting up materials like a minute per object and you hit an sss problem with juice in glass and might as well try to buy rope to hang yourself on.