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
Comments (1)
-
vverma9
Mar 26, 2019 08:33
Is it still an issue? my OnStateExit is never getting called at all.
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
- Mono Windows Builds don't produce full log callstacks when generating logs
- AssetBundles fail to load when running in Built Players for Mobile Devices
- UI elements with text gets bigger and grey when Player window is moved to another screen with different resolution
- System name accepts multiline text but crops it on confirmation, duplicates input, and shrinks the field when empty
- UI element scale and position are wrong in project build when DRS is changed with HDR and Software Dynamic Resolution enabled
This is a duplicate of issue #826180