Search Issue Tracker
Active
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
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Dynamic text is rendered in the background when it is inside the <font> tag
- SerializeReference interface does not show CustomPropertyDrawer when it's inherited from another interface
- Rendering artifacts appear in the Editor when modifying the Reflection Probe box size
- [HDRP] XR Multipass calls BeginCameraRendering and EndCameraRendering for each pass of the same camera
- NavMesh Surface is baked too high above the ground, making the NavMesh Agents hover above the ground when the HeightMesh is not built
Add comment