Search Issue Tracker
Won't Fix
Won't Fix in 2023.3.X
Votes
0
Found in
2021.3.30f1
2022.3.9f1
2023.1.13f1
2023.2.0b9
2023.3.0a5
Issue ID
UUM-48609
Regression
No
Graphics API raster states exhausted when adjusting light slope bias or shadow distance in HDRP with High (PCSS) Shadows
Reproduction steps:
1. Install RendecDoc to your device
2. Open the attached “repro-project” with the "-load-renderdoc" command line argument
3. Open the “Assets/Scene.unity“ scene
4. Enter Play Mode and wait
5. Observe the Console
Expected result: The Editor should function without logging any errors or assertions related to graphics API raster states
Actual result: The Console is spammed with “Assertion failed on expression: 'd3dstate'“ and “Assertion failed on expression: 'SUCCEEDED(hr)'“ errors
Reproducible with: 2021.3.30f1, 2022.3.9f1, 2023.1.13f1, 2023.2.0b9, 2023.3.0a5
Reproduced on: Windows 10 Pro
Not reproducible on: No other environment tested
Notes:
1. Issue arises due to the exhaustion of graphics API raster states when many adjustments are made to light slope bias or shadow distance, especially in PCSS shadows (D3D11 specifically has a limitation of approximately 4000 total raster states)
2. Reproducible when using RenderDoc on Windows. Without RenderDoc, errors might be GPU and driver-dependent
3. Not reproducible with DirectX12 Graphics API
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
- Too little validation messages in the "WebAssembly Language Features" Memory settings
- Project Settings Search Highlights are misaligned when using the Bitmap Text Rendering Mode
- "GetControlID at event ValidateCommand returns a controlID different from the one in Layout event" Warning is thrown when undoing the deletion of Sprite Shape Profile
- Memory related fields in the "WebAssembly Language Features" can be set to the negative numbers
- "WebAssembly Language Features" Header in the Player Settings has a smaller indentation
Resolution Note:
This issue has been fixed in RenderDoc nightly 2023-09-19 and versions after that.
Resolution Note (2023.3.X):
This issue has been fixed in RenderDoc nightly 2023-09-19 and versions after that.