Search Issue Tracker
Fixed in 5.6.0
Votes
0
Found in
5.4.0b22
Issue ID
808387
Regression
No
Any State -> transitions do not work correctly with Ordered Interruption
Steps to reproduce:
1) Download attached projetc "case_808387 repro" and open in Unity.
2) Open scene "mecanim_crossfade_test".
3) Select "GameObject" in Hierarchy tab.
4) Press Play and go to Animator window.
5) You should see the Any State -> scale_some transition constantly being interrupted by the scale_some -> Empty transition. (see attached gif"anim_interrupting").
6) Select the Transition between Any State -> scale_some. Change the Interuption Source to Current State, check the Ordered Interruption box, set the Interruption Source back to Next State. Note that the Ordered Interruption box is greyed out but stays checked.
Note: You should now see the Any State -> scale_some transition reliably finish, with no more interruptions from the scale_some -> Empty transition.(see attached gif"anim_not_interrupting").
Reproduced with: 5.2.4f1, 5.3.5p7, 5.4.0b25, 5.5.0a2.
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- "Draw Additional Lights Shadowmap" calls increase when custom MaterialBlockProperty is used
- Crash on _platform_memmove when importing the "Dragon Crashers - URP 2D Sample Project" to a new 2D project
- "Shader is not supported on this GPU" warnings and and shaders are not loading when building the project for non-Chromium browsers
- [iOS][URP] The screen flickers and the "Execution of the command buffer was aborted due to an error during execution" error is thrown continuously
- Shortcut Manager shows empty conflict filter when resolving runtime conflicts involving different contexts
Add comment