Search Issue Tracker
Fixed in 2020.1.X
Votes
1
Found in
2019.1.0b1
Issue ID
1120397
Regression
No
[GPU PLM][OSX]CL_INVALID_PROGRAM errors and fallback to CPU PLM after baking with GPU PLM on OSX if the Editor path has a space
Prerequisites:
An Apple machine with discrete GPU having more than 2GB of VRAM is needed to repro this bug.
Steps to repro:
1. Open attached project and 'ProgressiveLightmappingExample' scene;
2. In the Lighting window press 'Generate Lighting' button.
Expected result:
Baking on GPU completes successfully.
Actual result:
Errors:
- 'OpenCL Error. Falling back to CPU lightmapper. Error callback from context: CL_INVALID_KERNEL'
- 'OpenCL Error. Falling back to CPU lightmapper. Error callback from context: [CL_INVALID_KERNEL] : OpenCL Error : clEnqueueNDRangeKernel failed: invalid kernel 0x0'
and
- `OpenCL Error. Falling back to CPU lightmapper. Error callback from context: [CL_INVALID_BUILD_OPTIONS] : OpenCL Error : clBuildProgram failed: Invalid build options "-D APPLE -D USE_SAFE_MATH -cl-std=CL1.2 -I /Applications/2019.1/Unity 2019.1.0b1_83b3ba1f99df/Unity.app/Contents/Resources/OpenCL/kernels/"`
are shown. Baking backend falls back to CPU Lightmapper. See attached video.
Notes:
- Reproducible in 2019.1.0b1, 2019.2.0a2, 2019.3.0a2, 2019.3.0a3;
- Reproducible on every project that uses GPU PLM on OSX;
- Reproducible on AMD GPU;
- Reproducible only with GPU PLM; not reproducible with CPU PLM or Enlighten.
- Reproducible only when the path to the Unity Editor installation has space;
- Reproducible on OSX 10.13.3 and OSX 10.13.4; Not reproducible on Windows 10.
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Editor crashes on StoredGraphicsBuffer::GetGfxBufferID when VFX Graph property is modified during Play Mode and Application.targetFrameRate is used to limit FPS
- Crash on NVAPI_Thunk when changing Player resolution while HDR display is used and Direct3D12 is set as the graphics API
- Only one out of multiple cameras is shown in the Play Mode while HDR display is used and Direct3D12 is set as the graphics API
- The "Paste Component as New" option is incorrectly displayed as active despite the action being prohibited
- "TLS Allocator ALLOC_TEMP_TLS" errors are thrown when unsuccessfully importing an FBX file
gabebigboxvr
Apr 01, 2019 03:41
We reproduced this on Windows 10
"OpenCL Error. Falling back to CPU lightmapper. Error callback from context: Max allocation size supported by this device is 2.00 GB. 3.00 GB requested."
CPU: Intel i7 7700HQ with 64 GB System RAM
GPU: Titan V with 12GB VRAM