Blender 2.82a crashes if I try to enable LuxCoreRender.
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.
Blender 2.82a crashes if I try to enable LuxCoreRender.
I recently downloaded LuxCoreRender. The installation doesn't give any error messages. If I try to enable LuxCoreRender Blender crashes. Does anyone know what to do?
Re: Blender 2.82a crashes if I try to enable LuxCoreRender.
Some information like OS, Lux versions, etc.
Are you on MacOS ?
Re: Blender 2.82a crashes if I try to enable LuxCoreRender.
I'm experiencing this same issue.
Specs:
macOS Catalina v10.15.4 (19E266)
MacBook Pro (Retina, 15-inch, Mid 2015 | MacBookPro11,5)
Blender 2.82a
BlendLuxcore 2.3
I've tried the method elsewhere on this forum of having Security & Privacy open and accepting each piece of the package as the warnings come up (after replacing Embree libs with newest version from Intel). It worked at first, but then Blender crashed and always crashed after that.
I've tried the CPU and CPU+OpenCL builds.
I've also tried earlier versions of Blender.
Really interested in trying this renderer, hope it is working again soon!
Thanks.
Specs:
macOS Catalina v10.15.4 (19E266)
MacBook Pro (Retina, 15-inch, Mid 2015 | MacBookPro11,5)
Blender 2.82a
BlendLuxcore 2.3
I've tried the method elsewhere on this forum of having Security & Privacy open and accepting each piece of the package as the warnings come up (after replacing Embree libs with newest version from Intel). It worked at first, but then Blender crashed and always crashed after that.
I've tried the CPU and CPU+OpenCL builds.
I've also tried earlier versions of Blender.
Really interested in trying this renderer, hope it is working again soon!
Thanks.
Re: Blender 2.82a crashes if I try to enable LuxCoreRender.
2.81 is the most recent version that works on my end (Mojave).
I've read on the Github issues that there is a known bug in 2.82+ mac
I've read on the Github issues that there is a known bug in 2.82+ mac