Search Issue Tracker
Won't Fix
Won't Fix in 6000.5.X
Votes
0
Found in
6000.0.67f1
6000.3.9f1
6000.4.0b9
6000.5.0a7
Issue ID
UUM-134405
Regression
No
"Constant Force" Component numeric fields drift out of view while entering a really big value in the Inspector
Steps to reproduce:
- Create a new project using Universal 3D template
- Create a Cube in the Hierarchy
- In the Inspector, add the "Constant Force" Component
- In any of the field (e.g. Force X value) enter any number and keep on pressing to input a very large value
- Observe the field as more numbers are added
Actual results: As more digits are entered, the numeric field shifts to the right and eventually drifts out of view
Expected results: The value remains visible inside the field without shifting the whole field out of view
Reproducible with versions: 6000.0.67f1, 6000.3.9f1, 6000.4.0b9, 6000.5.0a7
Tested on (OS): Windows 11
Notes:
- Reproduces with both "Constant Force" and "Constant Force 2D"
- The field goes back to place once unfocused
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
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Resolution Note:
Thank you for reporting a bug to Unity.
We have reviewed the issue carefully, and in this case, the team is unable to prioritize fixing this bug. There are a number of reasons we make this decision, including the impact and severity of the issue across our user and customer base, and the possibility that future plans may solve the problem in a different way, or that a workaround for the bug may be available.
Today we will be closing this case. Thank you again for taking the time to report this issue, and please let us know if there is anything else that changes the impact or severity of this issue.
Resolution Note (6000.5.X):
Thank you for reporting a bug to Unity.
We have reviewed the issue carefully, and in this case, the team is unable to prioritize fixing this bug. There are a number of reasons we make this decision, including the impact and severity of the issue across our user and customer base, and the possibility that future plans may solve the problem in a different way, or that a workaround for the bug may be available.
Today we will be closing this case. Thank you again for taking the time to report this issue, and please let us know if there is anything else that changes the impact or severity of this issue.