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
- "Shader error redefinition of 'Varyings'" error appears when selecting the shader
- Crash after the “State comes from an incompatible keyword space“ log when opening the project
- [Android] GameObject are not rendered at all or rendered black when in the custom shader “multi_compile_instancing“ is enabled with two “float4” instance properties are present on older devices
- LineRenderer.BakeMesh generates a box-shaped MeshCollider when the camera's Y-axis rotation is in a specific range
- Different build sizes between Editor build and command-line build when "Static Batching" is enabled
Add comment