- Home /
Mecanim empty state has unwanted delay
I create a couple of empty mecanim states to better manage my states.
So I have like 3 empty states between 2 animation states.
The problem is that every one of those empty states plays for a short duration, which causes my animation to twitch a lot.
I set all transitions to bool so shouldn't those empty states exit immediately?
Another question: are mecanim states limited to one change of state per update?
EDIT: I don't have any 'Exit Time' conditions.
Answer by meat5000 · Sep 15, 2013 at 09:54 AM
Click the transition arrows and in each one remove the Exit Time parameter if you need to. Add other parameters instead.
I tried that already, right now I have only bools which should instantly change state.
Why do you add Empty states? That will be a time period where no animation is playing, so you will create twitchy behaviour. I suggest you simply manage your transition better. Don't forget you can define when the transitions occur between each animation by the sliders in inspector. Adding an empty state between animations means that you can no longer set the transition ti$$anonymous$$gs in the animations.
Unfortunately (even in 2019) you still need empty states for certain branching situations that need to run code.
Yeah it makes sense about no animations playing now... Thanks
Your answer
Follow this Question
Related Questions
Animation when the key is down and second animation when the key is up 0 Answers
Mecanim transition condition can't have both bool and trigger? 0 Answers
Why, when I delete transitions from the Animator State Machine, do I get a null reference exception? 3 Answers
mecanim move and root animation 0 Answers
Mecanim blend-tree transitions problem 0 Answers