Search Issue Tracker
Won't Fix
Votes
0
Found in
2022.3.62f1
6000.0.50f1
6000.1.5f1
6000.2.0b4
Issue ID
UUM-107885
Regression
No
Bool or Trigger Parameters can be selected via right clicking to the right of a Parameter control in the Animator Window
Steps to reproduce:
- Create a Project and an Animator in it and double click it to open it
- Select "Parameters" at the top left of the Window so they are visible
- Create a couple Bool or Trigger Parameters
- Right click to the right of their controls (circle, checkmark)
- Try the same with float or int Parameters
Actual results: The Bool or Trigger Parameters are selected
Expected results: Either the Bool or Trigger Parameters cannot be selected in this way or all Parameter types (int, float) can be selected this way
Reproducible with versions: 2022.3.62f1, 6000.0.50f1, 6000.1.5f1, 6000.2.0b4
Tested on (OS): Windows 11
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
- var VisionOSEDRHeadromm has a comma instead of a dot when building with Metal Rendering App Mode and local OS localization is set to German
- IAP Catalog remove product “x” and add product “+” buttons are not consistent with other remove and add buttons in the Editor
- Performance issues in Play Mode when quickly hovering the mouse cursor over Hierarchy GameObjects
- Frame Debugger displays incorrect output when FidelityFX Super Resolution or Spatial-Temporal Upscaler is used with Temporal Anti-aliasing or Subpixel Morphological Anti-aliasing
- The layout system is failing to correctly calculate or apply the height of the Japanese fallback font when the primary English font's metrics are used
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.