Search Issue Tracker
Won't Fix
Votes
0
Found in
2017.3.0a1
2018.2.0a1
2018.2.0f2
2018.3.0a1
2019.1.0a1
Issue ID
1089973
Regression
No
Handles.ScaleValueHandle does not work if startvalue is set to 0
Steps to reproduce:
1. Open attached project "Case_1089973-HandlesScaleValue.zip"
2. Press on "SomeValueNotZero" GameObject
3. Try to move the white dot which changes "Some value" float and Observe that value changes in the Inspector window
4. Now press on "SomeValueIsZero" GameObject (which has its start value set to 0)
5. Try to move the white dot again
Expected result: White dot moves and "Some Value" float changes.
Actual result: White dot doesn't move and value does not change.
Reproduced in 2017.4.16f1, 2018.1.9f2, 2018.2.18f1, 2018.3.0b12, 2019.1.0a10
Note: It looks like it's scaling the handle speed by its current value. It will make the handle go faster the higher the value is and slower the lower the value is. At minus described bug occurs and on the minus value, handle starts moving in the opposite direction than your mouse.
Comments (1)
-
samana1407
Jan 06, 2024 12:31
Unity 2022.3.13f1 the problem is not solved, same bug.
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
- “Remove Unused Overrides” available on not loaded Scene and throws “ArgumentException: The scene is not loaded” warning
- Adaptive Probe Volume occlusion edge is calculated incorrectly when viewing probes near geometry edges
- Sampling a texture using an HLSL file throws shader errors and the code does not compile
- "Graphics.CopyTexture called with null source texture" error when Base Camera of an Overlay Camera is removed with DX11 Graphics API and Compatibility Mode enabled
- WebGL sends wrong value with large numbers when SendMessage function is used
Resolution Note:
minor issue and only affects a few will close untli said otherwise