Search Issue Tracker
By Design
Votes
1
Found in
2021.3.36f1
2022.3.20f1
2023.2.13f1
2023.3.0b10
Issue ID
UUM-65377
Regression
No
Animation Event triggers from the previous Animation when the Animation is already changed
Reproduction steps:
1. Open the “ReproProject“ project
2. Open the “Assets/Scenes/SampleScene“ scene
3. Enter Play Mode
4. Observe the Console window
Expected result: Only “Play go up” and “Play Idle“ logs are printed in the Console window
Actual result: “This method shouldnt play“, “Play go up” and “Play Idle“ logs are printed the Console window
Reproducible with: 2021.3.36f1, 2022.3.20f1, 2023.2.13f1, 2023.3.0b10
Reproducible on: Windows 11 Pro (22H2)
Not reproducible on: No other environment tested
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
- [Tile Palette] Sprites not rendering when brush tool "Paint a filled box with active brush" is used for the first time
- Adding available Nodes with longer names in Fragment Context window overflow Fragment Context window in Shader Graph
- "Layer Palette Profile" Asset is automatically applied to the second Terrain but doesn't load any layers
- "Terrain Tools" shortcut conflicts with the Overlays shortcut by default
- Longer Shader Graph Property Reference names breaks VFX Graph Output Particle Node
Resolution Note:
The way it is designed at the moment is that during the internal animation update, the Fire Animation Events will fire all events that occurred between the time of the last update loop, and the current update loop. There is no special case made that will stop firing events if a state machine structural change is made (for example, by calling animator.play). This means that in the user case, those two events will be called in a single update loop.
While this is not something we're going to change or fix in the current animation system, it is something that we are taking into consideration for the next one, as the use case is a valid one