Search Issue Tracker
By Design
Votes
0
Found in
5.5.2p1
Issue ID
893600
Regression
No
Any State transitions to Sub State Machines ignore Interruption Source
To reproduce:
1. Open 'Simpler AnyState Interrupt Bug' project
2. Play the scene.
3. Select the gameobject and open the Animator window
4. Set Reset true to trigger the Any State transition.
Expected vs Actual: Any State transition does not get interrupted even though the conditions for the State1 to State2 transition are set and the Interruption Source is set to include the next state.
6. Set Reset true to trigger the Any State transition.
7. While the Any State transition is occurring set Reset true again.
Expected vs Actual: Any State transition does not interrupt itself to trigger another Any State to State1 transition event though it's conditions are set and the Interruption Source is set to include both the next and current states.
Reproduced on: 5.4.5p2, 5.5.3p4, 5.6.1p2, 2017.1.0b7, 2017.2.0a2
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