Search Issue Tracker
By Design
Votes
1
Found in
5.6.3p3
Issue ID
986915
Regression
No
Transitioning out of a Mecanim state takes a full second if the state has no animation
Reproduction steps:
1. Download user's project and open in Unity
2. Enter Play mode
Expected: time printed in console should be very small
Actual: time in console is about 1 second
Reproduced on: 5.5.6f1; 5.6.5f1; 2017.1.3f1; 2017.2.1p2; 2017.3.0p2; 2018.1.0b3; 2018.2.0a1
Note: in console the log error prints the time it takes to go from one state entry to the next
Comments (1)
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
- “Remove Unused Overrides” available on not loaded Scene and throws “ArgumentException: The scene is not loaded” warning
- Adaptive Probe Volume occlusion edge is calculated incorrectly when viewing probes near geometry edges
- Sampling a texture using an HLSL file throws shader errors and the code does not compile
- "Graphics.CopyTexture called with null source texture" error when Base Camera of an Overlay Camera is removed with DX11 Graphics API and Compatibility Mode enabled
- WebGL sends wrong value with large numbers when SendMessage function is used
jcox_PlayQ
Jan 17, 2018 20:46
I am the original bug reporter, but I did find a workaround in 5.6.3p3:
The bug occurs if you have a transition out of a state with Has Exit Time = true, Exit Time = 0, and Transition Duration = 0. You'd expect these settings to result in an instant (or rather, 1 frame) transition, but it takes a full second if the origin state has no animation.
The workaround is instead to set Has Exit Time to false, and give it a transition condition that always evaluates to true.