Search Issue Tracker
Fixed in 2020.1.X
Votes
0
Found in
2019.3
2019.3.0b12
Issue ID
1201654
Regression
No
[GPU PLM][AMD] Radeon Pro Denoise maxes VRAM and hangs
Repro:
Find a machine with recent AMD hardware, Windows 10 and current drivers. tested using AMD's November 15th 2019 driver build (26.20.13031.18002)
Download and import the attached repro project DenoiseFailBuiltIn.zip
Open the Scene Test.unity
Ensure Radeon Pro is selected as the Direct and Indirect Denoiser
Ensure Lightmap Resolution is set high enough to require more than 1x1024 lightmap
Hit Generate
Note:
GPUZ records 7.7gb of VRAM used when denoising a simple Scene with cube on plane. Seems to be a massive jump in memory usage going from 1x set of lightmaps to more. Even 1x1024 and a 1x512 is enough to cause the machine to stall.
Expected:
Ideally we should be able to denoise lightmaps regardless of Scene complexity and available VRAM. At worst, we should just fall-back to no denoising and write an informative error to the Console.
Workaround:
For AMD card users, set the maximum lightmap resolution to 1024 until this issue is fixed.
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Errors are thrown after redoing Nested Prefab Variant creation
- Documentation Link does not work when the "VFX Condition" question mark button is clicked
- Documentation Link does not work when the "Spawn State" question mark button is clicked
- Darker lighting in Build when disabling SSAO at runtime
- Animation glitches when using animation layering with base layer transition interruption
Add comment