Search Issue Tracker
Fixed in 2022.3.1f1
Fixed in 2022.3.X, 2023.1.X, 2023.2.X, 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
- 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 (fix version 2023.2):
Verified in build 2023.2.0a2.03842
Resolution Note (fix version 2023.1):
Verified in version 2023.1.0b11
Resolution Note (fix version 2022.3):
Verified on build 2022.3.1f1