Search Issue Tracker
Duplicate
Votes
0
Found in
5.3.6f1
Issue ID
824486
Regression
No
Mecanim: OnStateExit method never gets called when next state becomes active
Steps to reproduce(or just watch attached gif):
1. Open users attached project.
2. Open "Scene" scene located in "Assets>Scenes" folder.
3. Enter play mode.
4. In animator window check parameter values in this order: "Flag2" then "Flag1"
--- By doing this states will change in this order: StateA > StateB > StateC .
--- Check console window.
Expected results: Mecanim should execute "OnStateEnter" and "OnStateExit" method when state B starts and finishes.
Actual results: Mecanim only executes "OnStateEnter" method when state B starts and finishes.
Reproduced with: 5.5.0a6, 5.4.0p2, 5.3.6f1, 5.2.0f3
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
- [Dragon Crashers] Build fails in U6
- [Dragon Crashers] 4 Shader error messages on import
- [Dragon Crashers] Readme text is white on light grey
- Cursor stays in front of the first character when entering text in the TextMeshPro field
- Searching in Hierarchy causes unwanted component calls
This is a duplicate of issue #826180