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
- Shader warning in 'Hidden/Core/DebugOccluder' thrown after building High Definition 3D Sample Template
- Audio Mixer “+” buttons overlap with UI when the Audio Mixer window layout is set to Horizontal
- "Clear" button in the "Set project display name" closes all the pop-up instead of clearing just a name from the field
- Video Player renders no video on specific devices when using Vulkan
- The Editor slows itself down by showing tons of warnings when the majority of TransformAccessArrays content are NullRefs
This is a duplicate of issue #826180