Search Issue Tracker
Fixed
Fixed in 3.1.5
Votes
0
Found in [Package]
3.1.4
Issue ID
CMCL-1708
Regression
No
[Usability] Cinemachine Component fields that cannot be less than .01 should not enforce the correction before Users enter their desired input
How to reproduce:
- Open any Project with Cinemachine installed
- Select any Game Object in a Scene and add Component "Cinemachine Decollider" or "Cinemachine Deoccluder"
- Either in the field for "Camera Radius" in the Decollider or "Minimum Distance From Target" in the Deoccluder Components select the whole field entry
- Start typing "0" and other digits or dots after the 0
Actual result: Immediately after typing a 0 in the field a ".01" while the User is still typing, pressing Enter after the needed digits have been typed defaults the field to "0.01" as the entry is invalid, user has to manually select the addition of ".01" and delete it
Expected result: Since the fields cannot be less than "0.01", the correction should not be added until an invalid input has been entered and the field unfocused
Reproducible with: 3.1.4 (6000.0.54f1, 6000.3.0a3)
Cannot test with: 2.10.4 (No such Components)
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- StackOverflowException occurs and tests fail to load when the Test Runner window is opened while System.Windows.Forms.dll and System.Deployment.dll are present in the project
- Some UXML Template Asset foldouts appear enabled when all fields inside are disabled
- URP Terrain Demo crash on burst_signal_handler after Generating lighting
- Project window button icons are poorly visible and their shades differ in Light theme
- Automatic LOD fails and SRP Batcher incompatibility occurs when using spline-based quad-topology meshes
Add comment