Search Issue Tracker
By Design
Votes
0
Found in
6000.0.46f1
6000.1.0b15
6000.2.0a9
6000.3.0a1
Issue ID
UUM-103213
Regression
No
"Maximum Shadows on Screen" can be set to a negative number
How to reproduce:
1. Create a new HDRP Project
2. Go to Edit -> Project Settings -> Quality -> HDRP -> Lighting -> Shadows
3. Drag the "Maximum Shadows on Screen" value or manually enter any negative number
4. Observe the results
Expected results: Negative number can't be entered
Actual results: Negative number can be entered and then reset to "1" on confirm with throwing "Max shadow requests count reached, dropping all exceeding requests. You can increase this limit by changing the Maximum Shadows on Screen property in the HDRP asset." warning
Reproducible with: 6000.0.46f1, 6000.1.0b15, 6000.2.0a9
Reproducible on: macOS Sequoia 15.3 (M1)
Not reproducible on: No other environment tested
Notes:
- Even though the value is reset, it shouldn't be possible to go into the negative values
- No warning is thrown in 6000.0.46f1
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:
This is by design. This field, along with many other integer fields in the same UI, is a 'delayed field'. The value isn't changed at all until you commit, usually by pressing return. The value is never set negative - the warning appears because the value is set to 1, which is too low for the scene.
The field is delayed so changes don't immediately take effect. Doing so can cause performance issues when dragging or editing the value.
You can type much more than just negative numbers. These types of field support arbitrary mathematical expressions. For example you could type `5-2`. You don't know that the actual value is 3 until you commit and evaluate the expression.