Search Issue Tracker
By Design
Votes
0
Found in
2018.1.0f2
Issue ID
1056168
Regression
No
Animator StatemachineBehaviour does not change active states when transition is interrupted by 'next state'
Steps to reproduce:
1. Download and open the attached project
2. Enter Play Mode
3. Step through Play mode until interruption occurs
4. Observe logs and animator window
Expected result: B state is active for a frame
Actual result: A state remains active throughout
Reproduced on 2017.2.3f1, 2017.4.6f1, 2018.1.7f1, 2018.2.0b11, 2018.3.0a4
By Design: "Transitions stay in the original state (A) until the transition has completed. This is by design"
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- [Android] Stage information is not logged when Log Shader Compilation is enabled
- [Vulkan] The memory allocation increases rapidly when there are multiple (three or more) Real-Time Reflection Probes in the Scene
- [macOS] Library folder of the opened project can be deleted which leads to the crash
- “Default Scene” dropdown field contains a spelling mistake “Default Builtin”
- Editor crashes on PPtr<Mesh> after adding Text Mesh and Cloth Components to the same GameObject
Add comment