Search Issue Tracker
Fixed in 2019.1.X
Fixed in 2018.3.X
Votes
4
Found in
2018.3.0b3
Issue ID
1083099
Regression
No
[GPU PLM] Fallback from GPU to CPU lightmapper in CL_PROFILING_INFO_NOT_AVAILABLE when baking with GPU Lightmapper
Prerequisites:
You'll need the Labs Shadowmask project: https://ono.unity3d.com/test-data/gi-tests/LabsShadowmask
Steps to repro:
1. Open attached project and 'TheLabs_Shadowmask' scene;
2. In the Lighting window select 'Progressive GPU' lightmapper;
3. In the Lighting window click on 'Generate Ligthing' button.
Expected result:
Baking on GPU is executed without falling back to CPU Lightmapper or asserts.
Actual result:
Lightmapper backend falls back to CPU Lightmapper. The fallback is accompanied with the following errors:
'OpenCL Error. Falling back to CPU lightmapper. Error callback from context: CL_PROFILING_INFO_NOT_AVAILABLE'
and
`Assertion failed on expression: 'IsCLEventCompleted(events->m_StartMarker, isStartEventAnError)'`.
See attached video and actual.png screenshot.
Notes:
- Reproducible in 2019.1.0a1, 2018.3.0b3, 2018.3.0b2, 2018.3.0b1. ;
- Not reproducible in 2018.3.0a11;
- Reproducible when baking GeForce GTX 1070 and GeForce 640M; not reproducible on GeForce GTX 1080.
- Reproducible on Windows 10;
- Assert in IsCLEventCompleted might not be directly related to the fallback to CPU LM bug;
- The issue also happens in the new project with cubes and planes;
- The bug might not happen every time; if it doesn't try reloading Editor, cleaning GI cache/baked data and rebaking. Additionally, bake several time with changing light settings (Mixed>Baked) and move the viewport while baking.
-
neighborlee
May 09, 2020 12:40
Still here in 2019.3.13f1, Windows 10 GTX 950 2gb 8gb ram i5-3570
-
Lauris48
Mar 03, 2020 10:18
Same here in Unity 2019.3.3f1
-
i9mobile
Feb 18, 2020 17:48
Same problem here:
OpenCL Error. Falling back to CPU lightmapper. Error callback from context: CL_MEM_OBJECT_ALLOCATION_FAILURE error executing CL_COMMAND_NDRANGE_KERNEL on GeForce RTX 2080 Ti (Device 0).
OpenCL Error. Falling back to CPU lightmapper. Error callback from context: CL_MEM_OBJECT_ALLOCATION_FAILURE
Calling Deallocate on pointer, that can not be deallocated by allocator ALLOC_TEMP_THREAD
-
BrennanH
Dec 28, 2019 22:08
I just ran into
OpenCL Error. Falling back to CPU lightmapper. Error callback from context: CL_MEM_OBJECT_ALLOCATION_FAILURE
OpenCL Error. Falling back to CPU lightmapper. Error callback from context: CL_MEM_OBJECT_ALLOCATION_FAILURE error executing CL_COMMAND_NDRANGE_KERNEL on GeForce GTX 1070 (Device 0).
Windows 10, GeForce GTX 1070
-
create3dgames
Jul 10, 2019 22:53
Still an issue in 2019.3
-
r-kamphuis
May 16, 2019 06:00
still here in 2019.2.0b
-
ArkadiuszR
May 14, 2019 15:46
Same here. Unity 2019.1.0f2
-
Weidz_
Jan 15, 2019 19:52
Same error;
OpenCL Error. Falling back to CPU lightmapper. Error callback from context: CL_INVALID_PROGRAM
CPU - i7 8700K Intel
GPU - RTX 2080Ti
Driver NVIDIA 417.71
RAM - 2 x 32GB -
Weidz_
Jan 15, 2019 19:51
Same error;
OpenCL Error. Falling back to CPU lightmapper. Error callback from context: CL_INVALID_PROGRAM
CPU - i7 8700K Intel
GPU - RTX 2080Ti
Driver NVIDIA 417.71
RAM - 2 x 32GB -
aryssa
Oct 20, 2018 16:06
fixed for me when i desable "Prioritize view"
cpu i7 4790
gpu 770 gtx 4go
ram 16go
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
- Articulation Body with 'Revolute' Joint Type has erratic behavior when Upper Limit is set to above 360
- WebGL Player fails to render Scene when Terrain with Detail Mesh is added and WebGPU Graphics API is used
- Inconsistent errors are logged when different types are passed into the Query "Q<>" method in UIToolkit and the ancestor VisualElement is null
- Crash on GetMaterialPropertyByIndex when opening a specific Scene
- Discrepancies in the styling are present when using a TSS file instead of a USS file in custom EditorWindow
Resolution Note (fix version 2019.1):
Verified in 2019.1.0a6 (370df4c90d4b) and in 2018.3.0b7 (af029f4527e0) with using GeForce GTX1070 and GeForce 640m GPUs.