LuxCoreRender Forums

So the solution is to add:

if (isnan(ray->o.x) || isnan(ray->o.y) || isnan(ray->o.z) || isnan(ray->d.x) || isnan(ray->d.y) || isnan(ray->d.z))
return false;

in EmbreeAccel::Intersect() function in src/luxrays/accelerators/embreeaccel.cpp file


I have updated the source with your solution ...

MCurto wrote: Fri Jan 06, 2023 10:20 pm Does the Mac version requires any special adaptations/extra work?

Apparently the Mac build does not succeed because of an expired certificate.
Maybe u3dreal can fix that, if he has time. Let's wait and see.

Mac builds should be up again, thanks to u3dreal.

Hi, yes, apparently there has been a problem in the automatic build for BlendLuxCore.
I have run the pipeline again, hopefully everything's ok again in some minutes.

EDIT: It failed again, I have now run everything from scratch, including LuxCore. It will take 1 hour or so, let's see...

EDIT 2: it ...

Windows builds are now based on Python 3.10, so the should be compatible with Blender 3.1 (apart from the above mentioned problem with mesh export).
A new build should be ready in 1 hour or so.

CMake Error at CMakeLists.txt:126 (MESSAGE):
--> Could not locate required Intel Oidn files - Please check


It's working flawlessly here:

...
...
-- Intel OIDN support: enabled
...
...
Compilazione completata.
Avvisi: 0
Errori: 0

Tempo trascorso 00:10:52.96

Are you sure you are using the ...

From a quick test I just did, it should be possible to disable Optix by adding a "cuda.optix.devices.select" property, but this can only be done in a render config file, not from blendluxcore.
See for example the last line in the following excerpt from "render.cfg":
opencl.cpu.use = 0
opencl.gpu ...

This is a very strange, it look like something wrong in your Build Tools install.
Can you please check with Visual Studio Installer that you have at least one Windows 10 SDK installed?


Screenshot 2022-02-13 171732.png


It does not have to be the same that I have, but there should be at least ...

Ok, this is happening because either one of the used programs or our build script cannot properly handle the space in "C:\Program Files".
You can solve this by moving the whole "luxcorerender" folder out of "C:\Program Files" to a different location without spaces in the path name.

"C:\Program Files\luxcorerender\WindowsCompile\.\cmake-build-x64.bat"


This is not according to that step 5: you have collapsed two separate lines into one and forgot the beginning of the first line.
The first command should be
cd C:\Program Files\luxcorerender\WindowsCompile
This will take ...