Search Issue Tracker
Fixed in 2020.1.X
Votes
0
Found in
2020.1.0a12
Issue ID
1195547
Regression
Yes
[GPU PLM] CL_INVALID_PROGRAM error and fallback to CPU Lightmapper after launching the GPU bake for the first time
Steps to repro:
1. Open the attached project and 'SampleScene' scene;
2. In the Lighting window click 'Generate Lighting' button.
Expected result:
Bake with GPU Lightmapper completes withour errors.
Actual result:
The error:
"OpenCL Error. Falling back to CPU lightmapper. Error callback from context: CL_INVALID_PROGRAM" is shown. The lightmapper falls back to CPU Lightmapper. See attached video.
Regression introduced in 2020.1.0a12.
Workaround is to launch the bake again.
Notes:
- Reproducible in version 2020.1.0a12;
- Not reproducible in 2020.1.0a11, 2019.3.0b9, 2019.2.12f1, 2019.1.14f1;
- Reproducible with GPU Lightmapper only;
- Reproducible on NVIDIA GeForce RTX 2080 with the latest NVIDIA drivers on Windows and on AMD Radeon 560 on OSX;
- Reproducible in the legacy, Universal RP and HDRP.
Comments (1)
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
- Can’t delete gradient keys with Mac keyboard or context menu options
- Editor freezes for a few minutes when closing or switching a VFX window that was opened in a previous project
- UI Overlaps when switching Render Pipeline Asset for different Quality Levels in Quality Project Settings
- Ray Tracing Shader link to the documentation isn’t working
- Warning "BatchRendererGroups currently don't support override shaders" is spammed in Play mode when using H-Trace WSGI with BatchRenderGroups
FlooferLand
Jul 26, 2024 23:01
This is an issue in Unity 2023 now. Clearing GI cache and other workarounds don't work