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.
-
Hu3ainAli
Nov 16, 2021 21:23
I was facing the same problem and after tweaking every options it seems to be the Light map size.
when I increase the lightmap size above 2048 the renderer automatically switch over CPU from GPU and I receive the same error message. CL_MEM_OBJECT_ALLOCATION_FAILURE error executing CL_COMMAND_WRITE_BUFFER on GeForce RTX 2060 (Device 0).It works for me now Baking on GPU Progressive with the 2048 x 2048 lightmap resolution.
-
Fernando-Ferreira
Jul 22, 2021 01:27
07/21/2021 with unity 2021.1.15f1 and still this problem
-
davelister00169
May 12, 2021 21:24
"Fixed"
...2021.1.6F disagrees heavily with that statement ;P
-
koloved
Mar 04, 2021 20:47
SOLUTION: Install NVIDIA Studio Driver
its fixed my issue
-
adambielecki
Dec 30, 2020 15:06
Might work if you turn off Prioritize View in Lightmapping Settings.
-
adambielecki
Dec 30, 2020 15:00
Still happening in 2019.4.16.
Works well on unreal engine tough :P -
unity_TIA5gEFbyI4sHg
Dec 20, 2020 09:10
Unity 2020.2.0f1
OpenCL Error. Falling back to CPU lightmapper. Error callback from context: Not enough GPU memory to fit lightmap in memory, even in tiled baking mode. Available GPU memory: 3.58 GB
CPU - i7 10700
GeForce RTX 2060 Super (8 GB) -
jorge_acm
Dec 03, 2020 15:03
2020 and Unity still with this problem.
-
Braims
Oct 14, 2020 09:43
Error: Denoising step using GPU Lightmapper failed while trying to write the result to an OpenCL buffer.
Error: Baking will restart on fallback backend.
Error: 'PVR Composite Lightmap' job failed with error code: 1 ('Cancelled.').Laptop: MSI Prestige
CPU - i7 10710U
GPU - GTX 1650 Super Max-Q -
marcfawsitt
May 16, 2020 08:03
@ARYSSA thank you...holy crap i couldn't figure out why it kept going back to cpu and un clicking Prioritize view worked 100% for me. awesome
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
- SerializedPropertyChangeEvent is invoked when initially binding PropertyFields in custom Editor
- UI Panel is not visible when HDR and STP filter are enabled
- Crash on GfxDeviceD3D11Base::DrawBuffersIndirect when opening a specific project
- OnTriggerExit2D is called in Play mode when undoing component adding
- Builds fail with "Execution failed for task ':launcher:checkReleaseDuplicateClasses'" error when the newer version of the In-App Purchasing package is installed on a specific project
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.