Adding an existing StateMachineBehaviour to a state

The following documentation implies I can add an existing StateMachineBehaviour class to a state.. just like I would add an existing MonoBehaviour to different game objects:

http://unity3d.com/learn/tutorials/modules/beginner/5-pre-order-beta/state-machine-behaviours

However, when I click the Add Behaviour button, all I see the the 'New Script' option. Dragging an existing script onto the state doesn't work either.

Am I missing something or was that screenshot just a mock?

 

Interesting. I believe my animations are suffering from an identity crisis.. They seem to think they're a MonoBehaviour

Notice the following differences:
- My state behaviour has the Enable/Disable checkbox.
- The settings menu is different.

I just created a brand new project and it does behave correctly. So I believe this problem was introduced when I migrated my animation states from 4.5.4 into Beta and now to 5.0.f4.

I suppose I can work around by switching to debug mode and increasing the array size by hand... although I hope this is just a UI issue that will have no side effects on my animation states :S

 

Well, I figured out the reason for this weird behavior...

A long time ago, in the land of Unity 4.5.4 there was no such thing of StateMachineBehaviour.. so I implemented my own logic in a class called, you bet, StateMachineBehaviour which inherited from MonoBehaviour and also had nice little encapsulation of state transition with methods called, you bet again, OnStateEnter(), OnStateUpdate(), etc.

After importing the project to Unity 5, clicking the button 'Add Behaviour' created a the new class that inherited from StateMachineBehaviour but my StateMachineBehaviour, not Unity's.

This didn't generate any compilation errors and all state transition methods were being called as expected by 'coincidence' due to the same names and that's how things were working here for the last 3 months with the only side effect being the UI misbehaving..

 

Yes, I understand the asset vs scene object life cycle but no, no compilation errors. I would have expected something like "StateMachineBehaviour is ambiguous between namespace so and so.." but it just 'worked'.

Silent errors are tough to debug

Also, after fixing the ambiguous name, one small side effect remained: The enable/disable checkbox next to the script name still remains even though the little icon was updated from white C# to blue unity logo (compare with my previous post).

 

That's true. I was thrown off by your first screenshot that doesn't contain the checkboxes. I get it now, the checkbox will become visible if any of the overrides are present in the code.

Thanks for helping out. Always good see devs around.

 

I have another problem, please do me a favor.
when i builded a 3d-object prefab into an assetbundle which had "StateMachineBehaviour" attached to it's animator states with unity5.0.3,
then i load that assetbundle, but the "StateMachineBehaviour" script was not excuted....