Transition Settings in StateMachineBehaviour

I know that issue was brought up quite a while ago and I cant find the thread anymore...
So heres the deal:
Is it possible to access the transition settings of the next transition from within the StateMachineBehaviour?

 

Are you looking to do this?

http://docs.unity3d.com/ScriptReference/AnimatorTransitionInfo.html

 

I found the Settings in AnimatorStateTransition.
Is it even possible to reference AnimatorStateTransition in StateMachineBehaviour?

Or is there some easier way to start "SwingTree" at any point in "PrepTree".
But if PrepTree is at 100%, SwingTree must start at 0%
if PrepTree is at 0%, SwingTree must start at 50% (or 100% if I split it up)
So it has to be kinda inversely proportional.
Any suggestions?

 

No, AnimatorStateTransition is an editor only class.

If you want some kind of dynamic transition between two state you should use a StateMachineBehaviour and
Animator.CrossFade
http://docs.unity3d.com/ScriptReference/Animator.CrossFade.html

This function allow you to create a one time dynamic transition. you could use the AnimatorStateInfo from the StateMachineBehaviour to compute your start time.

Code (CSharp):

1. public class PreTree : StateMachineBehaviour {
2.  
3.     int swingTreeHash = Animator.StringToHash("SwingTree");
4.     // OnStateUpdate is called on each Update frame between OnStateEnter and OnStateExit callbacks
5.     override public void OnStateUpdate(Animator animator, AnimatorStateInfo stateInfo, int layerIndex) {
6.         if (myConditionToStartATransition)
7.         {
8.             animator.CrossFade(swingTreeHash, 0.05f, layerIndex, 1.0f - stateInfo.normalizedTime);
9.         }
10.     }
11. }

 

Wow, a developer is helping me!
Using CrossFade seems to work. Thanks a lot! My animations are much clearer.
It gets stuck sometimes for a moment as if there was an "ExitTime" somewhere...
And another thing, is it possible to assign speed to different States or even StateMachines in scripts?

 

Of course we are, Unity would not be what it is today without our commUnity

This is a new feature in 5.1 which is in beta stage right now, stay tune

What exactly is getting stuck?

 

I found my mistake...
It CrossFade should be fired only once, or else...
But now I have some State that isn't connected to its next State and transits thrugh magic.

Thanks again anyway, at least its working

 

I noticed some other odd behaviour...
I have a simple timed transition (animA -> animB via hasExitTime).
When I increase the Animator.speed, my animation animA stays some time in its last frame till it finally transits to animB.
How can I start a transition when animA is finished, independently from the animator.speed?

 

The only thing that animator.speed does is to scale delta time that we get from the engine when we get tick.

We never heard of any issue with transition and changing animator.speed, if you can't figure out what is going on you can log a bug with your project and some repro step.

 

Its probably because of the CrossFades normalized time.
hasExitTime=1 waits till animation is played out, but if animation starts with an offset and has no loop time, it simply waits in its last frame.

 

I used to start an AnimationEvent that played a sound in the first frame of "SwingTree".
But with CrossFade the AnimationEvent starts only if stateInfo.normalizedTime = 1.
How is it possible to play a sound with the start of animation?

 

Animation Events should always be fired if they are in the playback range.
You should log a bug.

The only other reliable way is to use StateMachineBehaviour.OnStateEnter()

 

Uhm... pardon my icompetence...
AudioSource.PlayClipAtPoint()
Is there a way to acess a static MonoBehaviour variable in StateMachineBehaviour so I can control the volume in all sound playing StateMachineBehaviours?
Or is there a better way to do that?

 

if the monobehaviour is on the same game object than your animator then you should be able to retrieve it with something like this

public override void OnStateEnter(Animator animator, ...) {
MyMonoBehaviour behaviour = animator.GetComponent<MyMonoBehaviour>();
}

 

Is it possible to start next State with an offset via the new Cycle offset parameter instead of crossfade?
Or is it only meant for looping animations so they only play from the beginning the first cycle?
Is there another cleaner way to accomplish that?