Again this stupid Mono Framework ....
I'll update later.
LuxCoreRender daily/automatic builds
Re: LuxCoreRender daily/automatic builds
check out my newest stuff http://q3de.com/research/
portfolio http://q3de.com/
MB Pro i7 2.3Ghz, IrisPro 1.5GB, GTX750m 2GB - BigSur
Xeon X5650@4Ghz, RX 5700 - BigSur , Windows 10, Ubuntu 20.04
portfolio http://q3de.com/
MB Pro i7 2.3Ghz, IrisPro 1.5GB, GTX750m 2GB - BigSur
Xeon X5650@4Ghz, RX 5700 - BigSur , Windows 10, Ubuntu 20.04
Re: LuxCoreRender daily/automatic builds
OK now all should be ....
check out my newest stuff http://q3de.com/research/
portfolio http://q3de.com/
MB Pro i7 2.3Ghz, IrisPro 1.5GB, GTX750m 2GB - BigSur
Xeon X5650@4Ghz, RX 5700 - BigSur , Windows 10, Ubuntu 20.04
portfolio http://q3de.com/
MB Pro i7 2.3Ghz, IrisPro 1.5GB, GTX750m 2GB - BigSur
Xeon X5650@4Ghz, RX 5700 - BigSur , Windows 10, Ubuntu 20.04
Re: LuxCoreRender daily/automatic builds
I really hate to be the person that keeps nagging and saying it isn't.
Last build of 17h ago, in 3.41 installs, but when you switch to rendered view gives unspecified error: I don't know to what error log it refers to, couldn't find any in my temp folder (open $TMPDIR), or any other relevant locations like Home or Blender App support in Library.
I ran Blender trought terminal with debug (don't know if there's a specific flag for Lux)
Debug file:
https://drive.google.com/file/d/1jyei1G ... share_link
Then the same release runs just fine after it compiles kernels in 3.3. But going back to 3.4 has the same behaviour

EDIT: Also found this, presumably written by you (?) , is it still relevant to new Mac versions?:
https://wiki.luxcorerender.org/Compilin ... _10.13_.2B
BTW: I keep working in 3.3.3 and all is fine, have no issues with the Lux reselase not working in 3.4x , maybe just better to keep a warning somewhere there are compatibility issues with 3.4.x?
Last build of 17h ago, in 3.41 installs, but when you switch to rendered view gives unspecified error: I don't know to what error log it refers to, couldn't find any in my temp folder (open $TMPDIR), or any other relevant locations like Home or Blender App support in Library.
I ran Blender trought terminal with debug (don't know if there's a specific flag for Lux)
Debug file:
https://drive.google.com/file/d/1jyei1G ... share_link
Then the same release runs just fine after it compiles kernels in 3.3. But going back to 3.4 has the same behaviour

EDIT: Also found this, presumably written by you (?) , is it still relevant to new Mac versions?:
https://wiki.luxcorerender.org/Compilin ... _10.13_.2B
BTW: I keep working in 3.3.3 and all is fine, have no issues with the Lux reselase not working in 3.4x , maybe just better to keep a warning somewhere there are compatibility issues with 3.4.x?
Re: LuxCoreRender daily/automatic builds
You can find it here ... i had something similar but after rendering the viewport works ...
The jpeg error is gone though.
what is you error ?
The jpeg error is gone though.
what is you error ?
check out my newest stuff http://q3de.com/research/
portfolio http://q3de.com/
MB Pro i7 2.3Ghz, IrisPro 1.5GB, GTX750m 2GB - BigSur
Xeon X5650@4Ghz, RX 5700 - BigSur , Windows 10, Ubuntu 20.04
portfolio http://q3de.com/
MB Pro i7 2.3Ghz, IrisPro 1.5GB, GTX750m 2GB - BigSur
Xeon X5650@4Ghz, RX 5700 - BigSur , Windows 10, Ubuntu 20.04
Re: LuxCoreRender daily/automatic builds
Same as yours? CUDA?
And yes, its viewport only, it renders fine, even the Oranje Juice scene that was throwing errors.

And yes, its viewport only, it renders fine, even the Oranje Juice scene that was throwing errors.
Re: LuxCoreRender daily/automatic builds
It seems to be acociated with viewport denoising beeing enabled ... all works when disabled
check out my newest stuff http://q3de.com/research/
portfolio http://q3de.com/
MB Pro i7 2.3Ghz, IrisPro 1.5GB, GTX750m 2GB - BigSur
Xeon X5650@4Ghz, RX 5700 - BigSur , Windows 10, Ubuntu 20.04
portfolio http://q3de.com/
MB Pro i7 2.3Ghz, IrisPro 1.5GB, GTX750m 2GB - BigSur
Xeon X5650@4Ghz, RX 5700 - BigSur , Windows 10, Ubuntu 20.04
Re: LuxCoreRender daily/automatic builds
Right....
also, there's no option in 3.4 to change Denoiser for Viewport:
3.3:
Surely that's the problem
also, there's no option in 3.4 to change Denoiser for Viewport:
3.3:
Surely that's the problem
Re: LuxCoreRender daily/automatic builds
RuntimeError: module compiled against API version 0x10 but this version of numpy is 0xf
ImportError: numpy.core._multiarray_umath failed to import
it seems numpy is wrong version ..... will test
ImportError: numpy.core._multiarray_umath failed to import
it seems numpy is wrong version ..... will test
check out my newest stuff http://q3de.com/research/
portfolio http://q3de.com/
MB Pro i7 2.3Ghz, IrisPro 1.5GB, GTX750m 2GB - BigSur
Xeon X5650@4Ghz, RX 5700 - BigSur , Windows 10, Ubuntu 20.04
portfolio http://q3de.com/
MB Pro i7 2.3Ghz, IrisPro 1.5GB, GTX750m 2GB - BigSur
Xeon X5650@4Ghz, RX 5700 - BigSur , Windows 10, Ubuntu 20.04
Re: LuxCoreRender daily/automatic builds
No that was not the problem ..
seems to be a missing property ... now it is time to ask if this is only macOS ... does anyone have this problem on win etc ?Traceback (most recent call last):
File "/Volumes/TOSHIBA_EXT/GitHub/Blender_Addons_2020/addons/BlendLuxCore/ui/render/viewport.py", line 68, in draw
can_use_optix = viewport.can_use_optix_denoiser(context)
File "/Volumes/TOSHIBA_EXT/GitHub/Blender_Addons_2020/addons/BlendLuxCore/properties/viewport.py", line 71, in can_use_optix_denoiser
if data.Get(prefix + ".cuda.compute.major").GetInt() >= 5:
RuntimeError: Undefined property in Properties::Get(): opencl.device.1.cuda.compute.major
check out my newest stuff http://q3de.com/research/
portfolio http://q3de.com/
MB Pro i7 2.3Ghz, IrisPro 1.5GB, GTX750m 2GB - BigSur
Xeon X5650@4Ghz, RX 5700 - BigSur , Windows 10, Ubuntu 20.04
portfolio http://q3de.com/
MB Pro i7 2.3Ghz, IrisPro 1.5GB, GTX750m 2GB - BigSur
Xeon X5650@4Ghz, RX 5700 - BigSur , Windows 10, Ubuntu 20.04
Re: LuxCoreRender daily/automatic builds
I recently added this check to only run OPTIX denoiser on newer Nvidia cards but this seems to give an error for non NVIDIA cards. I will push a fix soon.Traceback (most recent call last):
File "/Volumes/TOSHIBA_EXT/GitHub/Blender_Addons_2020/addons/BlendLuxCore/ui/render/viewport.py", line 68, in draw
can_use_optix = viewport.can_use_optix_denoiser(context)
File "/Volumes/TOSHIBA_EXT/GitHub/Blender_Addons_2020/addons/BlendLuxCore/properties/viewport.py", line 71, in can_use_optix_denoiser
if data.Get(prefix + ".cuda.compute.major").GetInt() >= 5:
RuntimeError: Undefined property in Properties::Get(): opencl.device.1.cuda.compute.major