Page 2 of 2

Re: LuxCoreRender v2.4beta1 released

Posted: Tue Jul 07, 2020 9:36 am
by B.Y.O.B.
This was indeed a bug in v2.4beta1, it has since been fixed (in latest daily builds).
(However it is not related to pointiness but to the invert node)

Re: LuxCoreRender v2.4beta1 released

Posted: Thu Jul 09, 2020 12:10 pm
by pepe
Yes, with the daily build works. Thank you.

Re: LuxCoreRender v2.4beta1 released

Posted: Sun Jul 12, 2020 2:04 am
by kumaran7
Why there is no NON-Opencl build addon?.

Re: LuxCoreRender v2.4beta1 released

Posted: Sun Jul 12, 2020 5:51 am
by acasta69
Now there is a single, unified executable that can detect if OpenCL or Cuda are present and use them. If none of the two is detected, CPU only is used.

Re: LuxCoreRender v2.4beta1 released

Posted: Sun Jul 12, 2020 6:47 pm
by afecelis
provisory wrote: Mon Jun 29, 2020 5:29 pm This new version crashes for me in Blender 2.83 when denoising during render, either when pressing Rerfesh Denoiser or stop the render.
In Blender viewport and in standalone LuxCoreUI it seems to be fine.
The OS is Kubuntu 19.10.
I attached console output and Blender crash txt for the default cube scene.
Same here, it's crashing badly both on windows/linux, I switched the kernel to CUDA for OPENCL. It starts doing the initial compilation, after a while it displays the rendered preview for a second and then it simply crashes and closes.

Re: LuxCoreRender v2.4beta1 released

Posted: Sun Jul 12, 2020 7:41 pm
by B.Y.O.B.
afecelis wrote: Sun Jul 12, 2020 6:47 pm Same here, it's crashing badly both on windows/linux, I switched the kernel to CUDA for OPENCL. It starts doing the initial compilation, after a while it displays the rendered preview for a second and then it simply crashes and closes.
That sounds like a different issue than the one provisory described (no denoiser involved).
Can you upload a testscene that reproduces the crash, and tell us which GPU(s) you have?

Re: LuxCoreRender v2.4beta1 released

Posted: Tue Oct 27, 2020 11:51 pm
by afecelis
Sorry for the late reply. It seems to have been fixed in the official release. I got 2x Geforce GTX1070, with latest Nvidia studio drivers V.456.71