Search Issue Tracker
Won't Fix
Votes
0
Found in
6000.0.0b15
Issue ID
UUM-69650
Regression
No
Reflection Probe Importance Setting validation acts differently depending on the number of symbols entered
Steps to reproduce:
1. In an HDRP Project create a Reflection Probe gameObject
2. In it's Importance Setting value enter "3333333" and press Enter
3. Now try entering "33333333333333333333333" and pressing Enter
Actual results: When entering "3333333" it defaults to 32767, when entering "33333333333333333333333" it defaults to 0
Expected results: When the maximum value is exceeded it should always default to the maximum value
Reproducible with versions: 6000.0.0b15
Not reproducible with versions: 2021.3.37f1, 2022.3.25f1, 2023.2.18f1 (New Feature)
Tested on (OS): Windows 11
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
- Crash on keywords::LocalKeywordState::operator when calling ShaderUtil.GetPasskeywords with ShaderType.RayTracing set as the third parameter
- Inconsistent “Remove property” behavior when removing child properties in Animator window
- Scene View Camera overlay preview goes out of Scene View bounds when the Scene View is resized vertically
- UI GameObjects are not positioned at 0,0,0 when creating them while Scene view is active
- Mesh Filter and Mesh Renderer property icons are difficult to see on blue highlight when selected in Animator window
Resolution Note:
Thanks for reporting this issue. This is high likely not related to Graphics field, but in particular we are too low in resources to look at this issue and it is not harmful as the value causing the behavior are unexpected anyway.