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
- Non-multisampled texture binding errors are logged when running the DepthBlit URP scene with MSAA enabled on Vulkan
- The Editor does not recognize code errors in generic classes when using C# Source Generator to generate serialization code
- NullReferenceException is logged when undoing Deletion of a Visual Query Block of a Search Expression
- “Unsupported type MinMaxCurve” error and “Could not register property modification for animation binding…” warnings are thrown after moving playhead when Particle System Property is added to Animation window
- Nested LocalizedStrings can not query local variables
Add comment