State machine behavior, OnStateEnter and OnStateExit problem?

Hello, I have two animations with transition between them. The OnStateEnter of the second animation calls before OnStateExit of the first animation but I need events of the first animation to be called before events of the second animation. I have noticed if I remove transition between animations then it works A1 enter -> A1 exit -> A2 enter -> A2 exit.
How do I solve this with having transition between animations but still have right order of state events?

Thank You

 

Replying to let folks know I have also experienced this issue.

 

I think the order is correct. The transition crossfades from A1 to A2. So A2 starts fading in while A1 is fading out.

What about this: Only use OnStateEnter. In A1.OnStateEnter, record that you're in A1. On A2.OnStateEnter, look up the recorded previous state and call a finish-up method on it.

 

I think part of the problem is that while we understand that in theory the code is behaving as it should (crossfading) the whole point of using StateMachineBehaviors was to get away from that kind of logic where you program against hardcoded state machine strings thus making them reusable

If we took that approach we'd have to add new code to the behavior each time you decided to throw it onto a new State on your State Machine. IMHO not really a very useful solution and may as well go back to the more reliable method of hardcoding string states in a normal monobehavior attached to the Animator

 

The logic is different, but it's just as generic. The logic handles the concept that a state machine can be in two states at the same time while it's transitioning. How you handle that logic at a higher level is of course up to you, but there's no reason at all that anything needs to be hardcoded.