OpenCL driver API error code: -30

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
docgfx
Posts: 3
Joined: Fri Nov 14, 2025 1:55 pm

OpenCL driver API error code: -30

Post by docgfx »

Hi!
Please help!

BlendLuxCore suddenly stopped working.
I keep getting the following error message:

OpenCL driver API error (code: -30, file:/Users/runner/work/LuxCore/LuxCore/src/luxrays/utils/ocl.cpp, line: 372): CL_INVALID_VALUE

I am using Blender 4.5.3 on a Macbook Pro M3 (worked without any issues a few weeks ago).
I tried BlendLuxCore 2.10.1 and 2.10.2, still getting the same error.

The only thing that might have changed is my MacOS version.
I have updated from MacOS Tahoe 26.0 to 26.1 recently.

Any ideas?

Thank you very much in advance!
docgfx
Posts: 3
Joined: Fri Nov 14, 2025 1:55 pm

Re: OpenCL driver API error code: -30

Post by docgfx »

Solved (at least temporarily).

Go to Edit - Preferences - Add-ons - BlendLuxCore - Preferences - choose CPU as Film Device.

I still hope LuxCoreRender will support Metal someday.
epilectrolytics
Donor
Donor
Posts: 818
Joined: Thu Oct 04, 2018 6:06 am

Re: OpenCL driver API error code: -30

Post by epilectrolytics »

When updating MacOS you might have to delete (user)/luxcorerender.org/ocl_kernel_cache folder before starting LuxCore.

A Metal version would be great indeed.
docgfx
Posts: 3
Joined: Fri Nov 14, 2025 1:55 pm

Re: OpenCL driver API error code: -30

Post by docgfx »

Thank you!

Deleting the cache folder solved the problem as well 8-)
soun89
Posts: 1
Joined: Wed Jan 21, 2026 11:42 am

Re: OpenCL driver API error code: -30

Post by soun89 »

Yes, that error is just MacOS and OpenCL being picky. When you update MacOS, the old ocl_kernel_cache can become invalid and give you that "CL_INVALID_VALUE" (-30) error. When you delete the cache folder, it resets it so that LuxCore can compile new kernels without any problems. That's pretty much the only way to fix it until they get proper Metal support. If you get the error in the middle of a project, switching to CPU rendering is also a safe option.
Post Reply