Search Issue Tracker
Fixed in 11
Fixed in 10.2.1
Votes
0
Found in [Package]
10.1.0
Issue ID
1290357
Regression
No
[HDRP]Console error and freeze/crash when setting Maximum Shadows to 0
How to reproduce:
1. Create a new project with HDRP template
2. In Project window -> Settings -> click on "HDRP Medium Quality"
3. In Inspector window -> Lighting -> Shadows -> Maximum Shadows
4. Set Maximum Shadows to 0
Expected results: The project is stable and no shadows are shown
Actual results: Console error about zero-length compute buffer, increasing memory usage and after some time, a freeze of computer and crash
Reproducible with: 4.10.0-preview (2018.4.29f1), 7.31 (2019.4.15f1), 8.20 (2020.1.14f1), 9.0.0-preview.71 (2020.1.14f1), 10.1.0 (2020.2.0b11,2021.1.0a6)
Note: If you want to avoid crashing and freezing, quickly after setting Maximum Shadows to 0, set Maximum Shadows back to a value higher than 0
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
- 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
- GameObject becomes gray when using HDRP and STP together on macOS
Resolution Note (fix version 11):
Fix available in 2021.1.0b1 and newer