Search Issue Tracker
Fixed in 2022.2.X
Votes
0
Found in
2022.2.0a8
2022.2.0a9
Issue ID
1412720
Regression
Yes
[CPU PLM][Denoising] "Baked lightmap denoising failed" error after changing denoiser to Radeon Pro and rebaking GI
Steps to repro:
1. Open the attached project and CornellBoxCrashTest scene;
2. In the Preferences window (Edit>Preferences...>GICache) press Clean Cache button;
3. In the Lighting window (Window>Rendering>Lighting) press Generate Lighting button;
4. Wait until lighting is baked;
5. When the Lighting is baked in the Lighting window expand the Direct Denoiser dropdown and select "Radeon Pro";
6. In the Preferences window (Edit>Preferences...>GICache) press Clean Cache button;
7. In the Lighting window (Window>Rendering>Lighting) press Generate Lighting button;
Expected result:
No errors are thrown during the bake.
Actual result:
Error:
"Baked lightmap denoising failed on final lightmap 2. The final baked lightmap is likely to be of poor quality. Try disabling the denoiser or lowering the Lightmap Size." is shown.
See attached video.
Notes:
- Reproducible in Version 2022.2.0a9;
- Not reproducible in Version 2022.2.0a7;
- Reproducible on Windows and NVIDIA GeForce RTX 2080 GPU;
- Reproducible when baking on CPU PLM;
- Reproducible when Radeon Pro denoiser is enabled;
- The issue might not happen all the time and is potentially timing-sensitive; If it doesn't repro try pressing Generate Lighting once again after the initial repro steps.
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
Add comment