Animation Won't Stop Looping

Aggressor

I have an animation set and I have the loop flag turned off. I have verified that the animation is only being set to the state once.

Can you advise why the animation won't stop looping even with the loop flag set to false?

Toggling the value in the inspector also won't stop it.

Found the source of the bug. Will report.

(If you set looping BEFORE the animation it works, but if you set looping AFTER the animation is doesnt).

Mitch

Don't trust that property. Use SetAnimation

Aggressor

I switched to that and its working fine now. I guess _animator.AnimationName is unsafe

Pharan

@[gelöscht]
I feel like this is a good place to tidy up some time soon.

SkeletonAnimation.AnimationName is weird. I vaguely recall it was designed this way because it was trying to be friendly to certain 3rd party Unity plugins? Was it some old version of PlayMaker or something?

I think it's handy as an editor thing and can be handy for previewing animations but its functionality could probably be moved to a separate, tiny component and we could just leave an Inspector label field to show the current animation on Track 0. Or maybe still a dropdown but have its functionality live exclusively in the Editor script, if that's possible.

I've actually had AnimationName's functionality disrupt some things I was trying to do before. I think it had something to do with AnimationName being used on Reset, and Reset being called on Awake, but I had some initial-animation stuff that wasn't working because of it so I just ripped the damned thing out of the runtime.

My current idea is:
If users need to switch animations through the inspector: we'll have a small script for that.
If users need to set the initial animation for the SkeletonAnimation: we'll also have a small script for that.

And we could have an Instantiate (Beginner) menu item for it that automatically adds it so it's discoverable.

One thing's for sure: at actual, normal, release-build runtime, SkeletonAnimation should work normally without it.

The loop bool is just obviously broken as an editor thing.

Nate

Pharan schrieb
I vaguely recall it was designed this way because it was trying to be friendly to certain 3rd party Unity plugins? Was it some old version of PlayMaker or something?

I think it only exists to allow setting an animation via the inspector.

Mitch

Nate schrieb
Pharan schrieb
I vaguely recall it was designed this way because it was trying to be friendly to certain 3rd party Unity plugins? Was it some old version of PlayMaker or something?

I think it only exists to allow setting an animation via the inspector.

Well... someone made it a public getter/setter that did things.

Nate

Doesn't Unity require things to be public? I'm fine with ditching it.

Aggressor

You can have a public getter and private setter if you prefer.

P.S. Is there like a PDF or doc for using the Unity runtime. The videos were EXTREMELY helpful but I can't seem to find written docs dedicated to Unity?

Nate

Aggressor schrieb
You can have a public getter and private setter if you prefer.

I think fields need to be used for Unity serialization.

Pharan

@[gelöscht]
There are no docs dedicated to any specific runtime, just general runtime docs where the runtimes are similar.

We try to post explanation topics here in the forums where Unity differs from other runtimes, but Unity is always changing and the Unity Runtime is always changing to make things easier. The most helpful and up-to-date Spine-Unity-specific docs are the videos and the sample projects and assets that come with the Spine-Unity runtime/.unitypackage.

Outside of those examples, advanced stuff live in Spine-C# (which official Spine documentation covers) and how you interface it with Unity's API (which will depend on your knowledge of how Unity works). You're always welcome to post what things you're trying to achieve with Spine-Unity in the forums. People do that a lot.

It helps act as feedback about how people are using Spine-Unity which helps inform further development of the runtimes and Spine editor, even if, for architectural reasons, things aren't implemented perfectly according to what your own project needs.