Search Issue Tracker
Fixed in 2022.1.X
Votes
0
Found in
2021.1
2021.2
2022.1
2022.1.0a8
Issue ID
1364204
Regression
No
[GPU PLM]Fallback to CPU PLM with: '!useRadeon || (!radeonDenoiser.IsNull()' after switching filtering settings and rebaking GI
Steps to repro:
1. Open the attached project;
2. In the Test Runner window (Window>General>Test Runner) under the Baking foldout section select BakeLightingGPU test;
3. In the Test Runner window under the Baking foldout section Shift-click and select BakeLightingGPUSubtractive to select all GPU PLM baking tests in this section;
4. In the Test Runner window right-click on the selection and press Run Selected button;
5. Wait until the tests are executed.
Expected result:
Selected tests pass successfully.
Actual result:
The tests fail with the following errors:
`Assertion failed on expression: '!useRadeon || (!radeonDenoiser.IsNull() && radeonDenoiser->GetRefCount() <= 1)'
`OpenCL Error. Falling back to CPU lightmapper. Error callback from context: IntersectionApi::Commit failure: likely out of GPU resources.`
`rif call failed with code -12.`
The lightmapper falls back to CPU PLM.
Notes:
- Reproducible on Windows 10 with NVIDIA GeForce RTX 2080 with the latest NVIDIA driver 471.96;
- Reproducible in Versions 2022.1.0a8, 2021.2.0b12, 2021.1.21f1;
- The case might be hardware and driver specific.
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- VFX Graph particles are not culled when using URP and Frustum Culling is enabled on VFX Mesh Output
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
Add comment