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
- Some UXML Template Asset foldouts appear enabled when all fields inside are disabled
- URP Terrain Demo crash on burst_signal_handler after Generating lighting
- Project window button icons are poorly visible and their shades differ in Light theme
- GC.Alloc called by HDRenderPipeline.LensFlareMergeOcclusionDataDrivenPass() when playing the default HDRP Sample Template project
- Automatic LOD fails and SRP Batcher incompatibility occurs when using spline-based quad-topology meshes
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.