Search Issue Tracker
Fixed in 2021.2.X
Votes
1
Found in
2018.4
2019.4
2019.4.6f1
2020.2
2021.1
2021.2
Issue ID
1306710
Regression
No
Blend Tree groups Animation Clips by their names and connects them to Blend Tree as one child node
How to reproduce it:
1. Open the user's attached project 'RPGMultiplayer.zip'
2. Load 'GameScene'
3. Notice that in Animator view all Animation Clips are connected to Blend Tree separately
4. Enter Play Mode
5. Observe the Blend Tree's graph in the Animator Window
Expected result: All Animation Clips are connected to Blend Tree separately
Actual result: Animation Clips with the same names are grouped and connected to Blend Tree as one child node
Reproducible with: 2018.4.31f1, 2019.4.19f1, 2020.2.3f1, 2021.1.0b4, 2021.2.0a3
Notes:
- This issue also causes incorrect animation execution order. In the Blending Diagram move the red dot clockwise along the motions dots and observe the Animator view. It's noticeable that Animation Clips are randomly highlighted
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
- NullReferenceExceptions are being thrown when saving a ScriptableObject with an array of a type with a CustomPropertyDrawer that uses TrackPropertyValue
- Applied velocity is inconsistent when using Rigidbody AddForce() with ForceMode.VelocityChange
- Crash on AudioUtil_CUSTOM_HasAudioCallback when exiting Play Mode while the Inspector is displaying a GameObject with an empty script attached
- Scroll offset is framerate-dependent when scrolling with velocity in the Device Simulator
- "Object.FindObjectsOfType<T>() is obsolete" warning is thrown when using "Transitions Plus" asset
Resolution Note (fix version 2021.2):
Fixed in 2021.2.0a17