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
- Asset preview doesn't update on changing shader's _GlobalColor property when the shader uses global uniforms
- Crash on GetSpriteAtlasDependenciesFromBinary when opening specific project
- Animation Clip with Legacy enabled does not play when Time.timeScale is set to 0 despite Update mode set to "Unscaled time"
- Rename is enabled on subfolder empty space - "Can't rename to empty name" warning
- SamplerState Property Missing Anisotropic Filtering
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