Page 1 of 1

OpenCL driver API error code -30 - Cl_invalid_value

Posted: Thu Aug 27, 2020 10:38 am
by Helo
Hi all,

I'm a total newbie on LuxCore, I started using it 2 days ago on Blender 2.83 and it was working without problems,
today, I have no idea why on all the scenes I try to open I got this error message and I can't render anything.

Code: Select all

OpenCL driver API error (code: -30, file/Users/runner/work/1/s/src/luxrays/utils.cpp, line:366): CL_INVALID_VALUE 
I'm Running blender 2.83 on a Macbook Pro 2017 - 3.1 GHz Quad-Core Intel Core i7 - Radeon Pro 560 4 GB
Mac Os Catalina 10.15.6

any help?

thanks

Re: OpenCL driver API error code -30 - Cl_invalid_value

Posted: Thu Aug 27, 2020 10:43 am
by Dade
Does the i7 have and integrated GPU ? Are you trying to use the Intel GPU ?

Try to post all console log, not just the error line.

Re: OpenCL driver API error code -30 - Cl_invalid_value

Posted: Thu Aug 27, 2020 10:46 am
by Helo
I am using the Radeon 560 to render
I don't know if this is the console log you mean

Code: Select all

Traceback (most recent call last):
  File "/Users/Jay/Library/Application Support/Blender/2.83/scripts/addons/BlendLuxCore/ui/render_performance.py", line 57, in draw
    opencl = context.scene.luxcore.opencl
AttributeError: 'LuxCoreScene' object has no attribute 'opencl'

location: <unknown location>:-1


Re: OpenCL driver API error code -30 - Cl_invalid_value

Posted: Thu Aug 27, 2020 10:50 am
by B.Y.O.B.
Which LuxCore version are you using?
Does it also happen with the latest builds of v2.5?
Helo wrote: Thu Aug 27, 2020 10:46 am I don't know if this is the console log you mean

Code: Select all

Traceback (most recent call last):
  File "/Users/Jay/Library/Application Support/Blender/2.83/scripts/addons/BlendLuxCore/ui/render_performance.py", line 57, in draw
    opencl = context.scene.luxcore.opencl
AttributeError: 'LuxCoreScene' object has no attribute 'opencl'

location: <unknown location>:-1

This error is unrelated to the first one.

Re: OpenCL driver API error code -30 - Cl_invalid_value

Posted: Thu Aug 27, 2020 11:10 am
by Helo
B.Y.O.B. wrote: Thu Aug 27, 2020 10:50 am Which LuxCore version are you using?
Does it also happen with the latest builds of v2.5?
Helo wrote: Thu Aug 27, 2020 10:46 am I don't know if this is the console log you mean

Code: Select all

Traceback (most recent call last):
  File "/Users/Jay/Library/Application Support/Blender/2.83/scripts/addons/BlendLuxCore/ui/render_performance.py", line 57, in draw
    opencl = context.scene.luxcore.opencl
AttributeError: 'LuxCoreScene' object has no attribute 'opencl'

location: <unknown location>:-1

This error is unrelated to the first one.
Uh, so I guess I have no idea how to see the complete log on the console,
I'm using BlendLuxCore v2.4 , I do not see a 2.5 on the website :?:

Re: OpenCL driver API error code -30 - Cl_invalid_value

Posted: Thu Aug 27, 2020 11:16 am
by B.Y.O.B.
Helo wrote: Thu Aug 27, 2020 11:10 am Uh, so I guess I have no idea how to see the complete log on the console,
Start Blender from a terminal, try to render until you get the "error code -30 - Cl_invalid_value" error, then close Blender and the log leading up to the error should be visible in the terminal.
Helo wrote: Thu Aug 27, 2020 11:10 am I'm using BlendLuxCore v2.4 , I do not see a 2.5 on the website
It's here: https://github.com/LuxCoreRender/BlendLuxCore/releases
("BlendLuxCore latest build")

Re: OpenCL driver API error code -30 - Cl_invalid_value

Posted: Thu Aug 27, 2020 11:42 am
by Helo
B.Y.O.B. wrote: Thu Aug 27, 2020 11:16 am
Helo wrote: Thu Aug 27, 2020 11:10 am Uh, so I guess I have no idea how to see the complete log on the console,
Start Blender from a terminal, try to render until you get the "error code -30 - Cl_invalid_value" error, then close Blender and the log leading up to the error should be visible in the terminal.
Helo wrote: Thu Aug 27, 2020 11:10 am I'm using BlendLuxCore v2.4 , I do not see a 2.5 on the website
It's here: https://github.com/LuxCoreRender/BlendLuxCore/releases
("BlendLuxCore latest build")
ok, no clue why, but starting Blender for terminal kinda fixed the issue....
Thank you so much!