Search Issue Tracker
Fixed
Fixed in 2022.3.1f1, 2023.1.0b11, 2023.2.0a2
Votes
0
Found in
2022.2.0b16
2023.1.0a21
2023.2.0a1
Issue ID
UUM-20616
Regression
Yes
[VFX] Min/Max/Range is not reflected in UI for Numeric properties
Properties with Min/Max/Range defined do not clamp values to the required range in the UI (although it's correct in the generated shader)
{}Steps to reproduce{}:
- Add a Collision with AABox block in Update context
- Use the mouse to drag the Bound or Friction values below zero
Actual result: the displayed value is negative
Expected result: the value is clamped to zero
!Unity_ojVe0DJMzL.gif!
{}Note{}:
Works fine in 2021.3
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
- Mono Windows Builds don't produce full log callstacks when generating logs
- AssetBundles fail to load when running in Built Players for Mobile Devices
- UI elements with text gets bigger and grey when Player window is moved to another screen with different resolution
- System name accepts multiline text but crops it on confirmation, duplicates input, and shrinks the field when empty
- UI element scale and position are wrong in project build when DRS is changed with HDR and Software Dynamic Resolution enabled
Resolution Note (fix version 2023.2.0a2):
Verified in build 2023.2.0a2.03842
Resolution Note (fix version 2023.1.0b11):
Verified in version 2023.1.0b11
Resolution Note (fix version 2022.3.1f1):
Verified on build 2022.3.1f1