Search Issue Tracker
Active
Under Consideration for 6000.0.X, 6000.2.X, 6000.3.X, 6000.4.X
Votes
0
Found in
2022.3.66f1
6000.0.59f1
6000.1.17f1
6000.2.7f1
6000.3.0b4
6000.4.0a1
Issue ID
UUM-120753
Regression
No
[Usability] Selecting Animations Clips in a Blend Tree's Motion List does not Visualize their Weight if all Weights have been enabled previously
Steps to reproduce:
1. Open the attached Project
2. Open the "AC_Mage" Animator Controller
3. Double click the Blend Tree "Locomotion Walk" and select the "Blend Tree WALK" Blend Tree State
4. Click on the (═) icon for any of the Motions in the Motions List and observe how the Weight Blue field changes when selecting each Motion
5. Click anywhere where there is free space in the Visualization and observe that all Weights for Motions are visible
6. Repeat step 5 and see that the Weight Blue field is no longer impacted
Actual results: After clicking in the Visualization field where there is no Motion and all Weights become visible selecting any of the Motions with the (═) icon no longer shows their weight, the workaround is to click on the Blue Dots in the Visualization itself, but that might mean that the PosX and PosY fields could be changed by accident
Expected results: Selecting Motions with the (═) icon in the Motions List and selecting Motions with the Blue Dots acts the same no matter if all the Weights have been enabled in the Visualization previously
Reproducible with versions: 2022.3.66f1, 6000.0.59f1, 6000.1.17f1, 6000.2.7f1, 6000.3.0b4, 6000.4.0a1
Tested on (OS): Windows 11
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
Add comment