Page 13 of 15

Re: A baking test scene

Posted: Thu Dec 19, 2019 12:04 pm
by epilectrolytics
Dade wrote:
Thu Dec 19, 2019 10:08 am
it was an overflow of accumulated luminance in Metropolis sampler.
Big thanks for fixing this!
Going to test this soon.
Dade wrote:
Thu Dec 19, 2019 11:04 am
Very first caustic baking and glTF export: https://skfb.ly/6PzuS
As far as I know, it has never been done before. The baked map alone is quite a beauty:
A beauty it is!
And rendered as emissive with LuxCore or Cycles this should do SDS-paths on the go.

Re: A baking test scene

Posted: Thu Dec 19, 2019 12:13 pm
by Racleborg
May I please see the Blender file so I can see how to do this?

Thank you

Re: A baking test scene

Posted: Thu Dec 19, 2019 1:17 pm
by epilectrolytics
Now I took the (small resolution) map Dade posted above and implemented it in B.Y.O.B.'s original scene:
Screen Shot.jpg
Instant SDS-caustics in Cycles viewport!
(LuxCore works too, but way slower)

Re: A baking test scene

Posted: Thu Dec 19, 2019 6:27 pm
by epilectrolytics
epilectrolytics wrote:
Mon Dec 16, 2019 4:09 pm
While the second image looks like correct caustics the first one shows apparently the light trace brightness issue that I have reported repeatedly in the respective thread.
Apparently I was wrong, the brightness variation I meant mainly in combination with rough glass is another thing and still persists after the last fix of the caustic explosion reported here.

Re: A baking test scene

Posted: Thu Dec 19, 2019 9:46 pm
by Racleborg
Bakeallobjects: When OPENCL is used then the .exr files are all almost black with just a splash of what looks like the caustic. (Image attached)

If just CPU is used, then everything is ok?

Re: A baking test scene

Posted: Thu Dec 19, 2019 10:20 pm
by Dade
Racleborg wrote:
Thu Dec 19, 2019 9:46 pm
Bakeallobjects: When OPENCL is used then the .exr files are all almost black with just a splash of what looks like the caustic. (Image attached)

If just CPU is used, then everything is ok?
Only BAKECPU exists, you can not bake objects with OpenCL :?:

Re: A baking test scene

Posted: Thu Dec 19, 2019 10:34 pm
by Racleborg
I'm referring to the render settings in Blender which I had presumed where exported with the Luxcore Filesaver? (images attached), for which I haven't had any issues with until recently.

But no problem as I will just ensure that it is switched to CPU from now on :)

Re: A baking test scene

Posted: Fri Dec 20, 2019 8:21 am
by Dade
Racleborg wrote:
Thu Dec 19, 2019 10:34 pm
I'm referring to the render settings in Blender which I had presumed where exported with the Luxcore Filesaver? (images attached), for which I haven't had any issues with until recently.
I assume BlendLuxCore set the CPU/GPU light /path tracing partition to 0.0 when using PATHOCL (it is different when you use PATHCPU) so you were baking only the light tracing part of the rendering by selecting PATHOCL.

Re: A baking test scene

Posted: Fri Dec 20, 2019 8:30 am
by Racleborg
I assume BlendLuxCore set the CPU/GPU light /path tracing partition to 0.0 when using PATHOCL (it is different when you use PATHCPU) so you were baking only the light tracing part of the rendering by selecting PATHOCL.
Thank you for the explanation

Re: A baking test scene

Posted: Fri Dec 20, 2019 8:48 am
by Racleborg
With Blender is set to: CPU. Light tracing ON, Caustic cache ON , then when Bake All Objects is running in LUXCOREUI a message is regularly occurring ?(image attached)

Thank you