Search Issue Tracker
Fixed
Fixed in 2022.3.63f1, 6000.0.51f1, 6000.1.5f1, 6000.2.0b4, 6000.3.0a1
Votes
0
Found in
2022.3.60f1
6000.0.42f1
6000.1.0b10
6000.2.0a6
Issue ID
UUM-99493
Regression
No
When evaluating an interrupted transition, the Animator writes the last evaluated values for all values instead of correctly defaulting to the state's current configuration
How to reproduce:
1. Open the “Animator-CrossFade-Bug.zip“ proect
2. Open the “SampleScene“
3. Open the Game view, hierarchy, and the Animator windows
4. Enter Play Mode
5. Observe the Hierarchy and the Game view
Expected results: All Animator children get activated one at a time
Actual result: At one moment, all children get activated at once
Reproducible in: 2022.3.60f1, 6000.0.42f1, 6000.1.0b10, 6000.2.0a6
Reproduced on: Windows 11 Pro (24H2)
Not reproduced on: No other environment tested
Notes:
- One split-off crossfade starts a few milliseconds later than the other one. This makes the second crossfade override the first crossfade and, in the process, causes the bug
- All the animations get activated until the transition finishes
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Reflection Probe “Probe Scene Editing Mode:” text is barely visible
- [HDRP] Game view doesn’t refresh after changing Camera Background Type until mouse moves over it
- Some Shaders appear twice in Material Shader selection menu
- Editor freezes with a StackOverflowException when certain asset types are assigned to a managed component in a SubScene via AddComponentObject
- Scale Snapping with Gizmos does not work in the Scene view when Snapping and Absolute Grid Snapping are toggled off
Add comment