Difference in effective length between states is too big

[KokodokoGames]

I have a spritesheet animation with transitions, but I don’t actually need a transition between the two animations. That’s why I set all the transition times to 0, and no exit time.
I want the animation to jump straight into the next animation without any interpolation at all.
This works fine, except that Unity complains about it:
Difference in effective length between states is too big. Transition preview will be disabled.
UnityEngine.GUIUtility:ProcessEvent(Int32, IntPtr)

[system]

In this article, the author suggests not using transitions at all in favor of Animator.Play:

Are you wondering where the transitions are in our Mechanim state machine? Then I’m about to blow your mind. You __don’t need them__. And you don’t need any more parameters, either. You can simply use myAnimator.Play(“StateName”) to have the character immediately play that animation. Mechanim transitions are entirely unnecessary in pixel art because we always want the clips to transition in zero frames. Plus, from a clean code perspective I prefer to have all animation logic in the script, not inside mechanim. Using things like exit time (automatic transition) when a clip finishes scatters transition logic between script and mechanim and is just begging for bugs.

[JoeStrout]

I hadn’t seen that article, but it sounds very similar to what I say in mine.

[KokodokoGames]

Thanks, I was actually wondering about that! It seems a LOT easier to just set the state directly — if you’re a coder.

I do like the workflow where the coder just sends a variable to the animator, and then the animator can decide what to do with it. This allows artists / game designers to tweak the game without the coder having to decide everything.

But perhaps the coder could create a global variable where you can set the animations for each state in the Unity editor.