Unity Issue Tracker - [GPU PLM] Fallback from GPU to CPU lightmapper in CL_PROFILING_INFO_NOT_AVAILABLE when baking with GPU Lightmapper

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

Progressive Lightmapper

Sep 20, 2018

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.

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.

Comments (25)

giorat96

Oct 19, 2018 20:09

Getting this error as well - 'OpenCL Error. Falling back to CPU lightmapper. Error callback from context: CL_PROFILING_INFO_NOT_AVAILABLE'

And if I manually switch to use GPU with "./Unity.exe -OpenCL-PlatformAndDeviceIndices 1 0" I get this errors:
Assertion failed on expression: 'IsCLEventCompleted(data.startEvent, isStartEventAnError)'
Assertion failed on expression: 'IsCLEventCompleted(events->m_StartMarker, isStartEventAnError)'

My specs for reference
CPU - i7-6500U @ 2.5GHz
GPU - NVidia 940MX
RAM - 8GB
UltronTM

Oct 04, 2018 21:32

I have no problem when using default settings in Lighting Window by clicking its Reset. However, setting Direct Samples to 128 from default 32, will cause this problem. Reducing Lightmap Resolution from default 40 to 35 texels per unit fixes it again.

My specs with Unity 2018.3.0b4 on Windows 10:

CPU: i5 6600
GPU: GTX 1080ti
RAM: 8GB
maartene

Oct 03, 2018 18:25

Getting the same error.
My specs:
CPU: i5 6500 @ 3.2Ghz
GPU: MSI GTX 960 2GB
RAM: 16GB
Unity 2018.3.0b4 on Windows 10 (all updates)
Thall33

Oct 01, 2018 07:55

Also error - OpenCL Error. Falling back to CPU lightmapper. Error callback from context: CL_MEM_OBJECT_ALLOCATION_FAILURE error executing CL_COMMAND_WRITE_BUFFER on GeForce GTX 1070 (Device 0).

When I change to no-directional mode.
Thall33

Oct 01, 2018 07:50

Getting this error as well - 'OpenCL Error. Falling back to CPU lightmapper. Error callback from context: CL_PROFILING_INFO_NOT_AVAILABLE'

My specs for reference

CPU - i7 7700K Intel @ 4.5GHz
GPU - EVGA 1070 gtx ftw
RAM - Corsair Vengence Pro RBG 3200Mhz 2 x 16GB
MB - Z270 Mark 2