Blender 2.82a crashes if I try to enable LuxCoreRender.

Use this forum for general user support and related questions.
Forum rules
Please upload a testscene that allows developers to reproduce the problem, and attach some images.
Post Reply
Liryuk
Posts: 1
Joined: Tue Mar 24, 2020 3:44 pm

Blender 2.82a crashes if I try to enable LuxCoreRender.

Post by Liryuk »

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?
User avatar
Dade
Developer
Developer
Posts: 5672
Joined: Mon Dec 04, 2017 8:36 pm
Location: Italy

Re: Blender 2.82a crashes if I try to enable LuxCoreRender.

Post by Dade »

Liryuk wrote: Tue Mar 24, 2020 3:47 pm 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?
Some information like OS, Lux versions, etc. :?:

Are you on MacOS ?
Support LuxCoreRender project with salts and bounties
lem0nayde
Posts: 1
Joined: Thu Apr 02, 2020 3:01 am

Re: Blender 2.82a crashes if I try to enable LuxCoreRender.

Post by lem0nayde »

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.
User avatar
melMass
Posts: 13
Joined: Wed Apr 01, 2020 9:26 pm

Re: Blender 2.82a crashes if I try to enable LuxCoreRender.

Post by melMass »

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
Post Reply