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
- Error “Shader error in 'YSCloudCover': call to 'tex3D' is ambiguous at Assets/YSCloudCoverText.shader(606) (on d3d11)“ is present when compiling tex3D shader with DXC
- Placeholder asset is not loaded with Advertisement Legacy sample when using the latest version of the package
- Addressables content build fails but the Player build is successful when building a development build
- Out-of-bounds memory access with multiple CanvasRenderers under a Canvas when using Mesh API
- Inspector tries to access file after it was deleted when the file was locked in Inspector window
Add comment