Search Issue Tracker
Won't Fix
Won't Fix in 2021.3.X
Votes
0
Found in
2021.3.7f1
Issue ID
UUM-10653
Regression
No
"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.
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
- Error “Shader error in 'YSCloudCover': call to 'tex3D' is ambiguous at Assets/YSCloudCoverText.shader(606) (on d3d11)“ is present when compiling tex3D shader with DXC
- Placeholder asset is not loaded with Advertisement Legacy sample when using the latest version of the package
- Addressables content build fails but the Player build is successful when building a development build
- Out-of-bounds memory access with multiple CanvasRenderers under a Canvas when using Mesh API
- Inspector tries to access file after it was deleted when the file was locked in Inspector window
Resolution Note:
Given the low user impact of this issue and the fact that there are other (better) denoisers available, we are deciding not to fix this issue.
Resolution Note (2021.3.X):
Given the low user impact of this issue and the fact that there are other (better) denoisers available, we are deciding not to fix this issue.