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
- CurveTexture is not being released when unloading AssetBundle containing a Scene with ColorCurves post-processing component in Global Volume
- Crash on ExtractActiveCasterInfo when navigating the scene view in a project with specific lighting data
- Build Profile name increments when numeric suffix is removed from duplicate Profile name
- "Unrecognized block header in profiler data file, stopping deserialization" error is shown and no more profiler data is recorded when the Player is connected and profiler recording is enabled/disabled few times
- Shader error and warnings thrown when setting HDRP as an Active Target in Blank Shader Graph
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