Search Issue Tracker
Postponed means that the issue was either a feature request or something that requires major refactoring on our side. Since that makes the issue not actionable in the close future we choose to close it as Postponed and add it on our internal roadmaps and technical debt pages instead.
Postponed
Votes
0
Found in
2021.2
Issue ID
1408298
Regression
Yes
GPU PLM falls back to CPU PLM when Auto Generate is enabled during the Finalizing Bake stage
Steps to reproduce:
1. Download AdventureSampleGame project (link in the comments)
2. Open the Market scene
3. Make sure that lightmapping backend is set to Progressive GPU
4. Initiate a bake by clicking on the Generate Lighting button
5. Wait until the bake reaches Finalizing Bake stage (might be easier to see with an expanded Background Processes view within the editor)
6. Click on the Auto Generate toggle
7. Progressive GPU falls back to the Progressive CPU printing warnings in the console
Notes:
- Reproduces in every Unity editor version since the 2021.2 public release
- Reproduces only when Progressive Updates toggle is unchecked
- This issue was uncovered while investigating the following bug: https://fogbugz.unity3d.com/f/cases/1389093/
Relevant editor log print:
OpenCL Error: 'm_OpenCLRenderLightmapBuffers.GetBuffer(kRRBuf_outputValidityBuffer).EnqueueReadBuffer(openCLState, CL_TRUE, 0, numTexelsToCopy, reinterpret_cast<void*>(temp_buffer_float.data()), 0, NULL, NULL)' returned -30 (CL_INVALID_VALUE)!
OpenCL Error. Falling back to CPU lightmapper. Error callback from context: CL_INVALID_VALUE
0x00007ff65ed217ad (Unity) [StackWalker.cpp:1006] StackWalker::GetCurrentCallstack
0x00007ff65ed29019 (Unity) [StackWalker.cpp:986] StackWalker::ShowCallstack
0x00007ff66075eb61 (Unity) [Stacktrace.cpp:166] GetStacktrace
0x00007ff6616388d2 (Unity) [LogAssert.cpp:1061] DebugStringToFile
0x00007ff660a4990c (Unity) [OpenCLCheck.cpp:140] OpenCLErrorContextCallback
0x00007ff660ab4362 (Unity) [RRBakeLightmapTechnique.cpp:1072] RadeonRaysBakeLightmapTechnique::CopyCurrentBakedTileResultFromGPUToCPU
0x00007ff660ae0f4d (Unity) [RRJobCompositeLightmap.cpp:470] RadeonRaysJobCompositeLightmap::Execute
0x00007ff660a1bf91 (Unity) [BakeContextManager.cpp:354] ProcessJobs
0x00007ff660a26dca (Unity) [BakeContextManager.cpp:374] BakeContextManager::UpdateFunction
0x00007ff660a10795 (Unity) [BakeContextManager.cpp:203] BakeContextManager::DispatchUpdateFunction
0x00007ff65e908577 (Unity) [Thread.cpp:84] Thread::RunThreadWrapper
0x00007ffb53767034 (KERNEL32) BaseThreadInitThunk
0x00007ffb549e2651 (ntdll) RtlUserThreadStart
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 (2022.2.X):
This bug will be fixed by enablement work that is in progress now. To that end we are postponing this and will retest once that lands.