Этот сайт лучше всего просматривать в современном браузере с включённым JavaScript.

Mecanim state loses script references?

rentheunclean

Hi!

I am using Spine in Unity3d, and often when I make changes to a script attached to a state in an animator that is being run by Spine, it causes Unity to lose all its references to scripts for that entire animator. For each state on the animator, the script reference is replaced with null.

What this usually means is that I have to revert to an older version and redo all of the changes I have made to the animator, causing me to lose hours of work. If I wasn't working with source control, this would be even worse, since I would have to redo the entire state machine every time.

Is this a known issue with a work around or some cause I can avoid?
Is there a fix for this on the roadmap for Spine?

Thanks,
Ren the Unclean.

Pharan

That doesn't sound right.
Spine-Unity doesn't have any code that handles, much less modify, anything in Unity animation state machines.

At runtime, it just reads the active state machine's state through the Animator component (it doesn't touch the serialized asset) and applies the correct Spine.Animation accordingly.

How do you know Spine is the cause?

rentheunclean

Hi Pharan, thanks for the response!

I am assuming it is Spine related because I haven't seen it happen on other projects I have worked on using Mecanim.
I guess it could be some sort of Unity metadata issue if you haven't seen it before or had any reports similar to mine.

I will try to look into it further and hit you back up if I have more information!

Thanks!

Shekill

I also have the same problem with animation state behaviors. Sometimes all Behaviors of a animator are unlinked or disappear and I have to use my source control.
I haven't seen this problem without spine, but as it's mecanim related, so i'm not 100% sure it's because of spine.

rentheunclean

So I looked around a bit more and found this!
http://forum.unity3d.com/threads/statemachinebehaviour-scripts-go-missing-after-reimport-all.337750/

Looks like it is a Unity issue they introduced with 5.0 (which makes sense, since other projects I have worked on without spine were not using Unity5). Apparently caused randomly when compilation of a script fails.
Good to know it isn't a problem with Spine, but unfortunately it doesn't look like there is a concrete answer from Unity on a fix.

Thanks again Pharan! Sorry for the false alarm, but hopefully you can at least direct others to that thread if they think this problem is Spine related!

Ren the Unclean.

Pharan

That's bizarre.
I'm aware of StateMachineBehaviours but I never use them so I've never seen this happen.

Thanks for sharing what you found! I hope the problem gets fixed too.