Цей сайт найкраще переглядати в сучасному браузері з включеним JavaScript.

GameObject with multiple child skeletons

Abelius

Hi there,

I need to change the assigned skeleton of a character in-game, so it completely changes its appearance and behavior.

I know I could do that by assigning another one to the Skeleton Animation component in that object, but I also have a complex render separator implemented that has a different configuration for each skeleton, so I also would need to change its configuration and even worst, the config for each part renderer as well.

As I don't see that reasonable, I'm thinking about instantiating each skeleton as a separate gameobject under the character gameobject itself, along with all its necessary extra components. Then I'd enable and disable them so only one of them is active at all times for that character.

The final result would be a character object with around five child instantiated Spine skeleton animation, utility, render separator (etc.) components in each of them.

What's your opinion on that? Is that performance wise and feasible? :think:

Thank you for your time.

Abelius

Pharan

Yeah, if those different skeletons are just too different, just add multiple Spine GameObjects to that parent/main GameObject.
The disabled Spine GameObjects would not do anything so they don't cost anything performance-wise.

It's better than instantiating/destroying different skeletons as needed since that would do a lot of alloc stuff.
Not sure what you intend to do with SkeletonUtility though. You may have to do some juggling reparenting Transforms. Probably not too bad.

Abelius

Pharan написав
Yeah, if those different skeletons are just too different, just add multiple Spine GameObjects to that parent/main GameObject.
The disabled Spine GameObjects would not do anything so they don't cost anything performance-wise.

It's better than instantiating/destroying different skeletons as needed since that would do a lot of alloc stuff.

Thank you Pharan. 🙂

Pharan написав
Not sure what you intend to do with SkeletonUtility though. You may have to do some juggling reparenting Transforms. Probably not too bad.

I'm using SkelUtil for the sole purpose of being able to access "Flip X" property from the PlayMaker editor. It works in the way that you need to drag&drop the whole component from the Inspector to the PM editor.

It's a very messy way to make a game I know, but I'm being able to do it without a single line of code... for the time being at least. 😉

Pharan

I don't think you can rely on using SkeletonUtility for FlipX. What you see in the inspector is just a preview-only field.
I don't know if it would work in a build.

You should add a separate component that actually accesses SkeletonAnimation.Skeleton.FlipX
I'm not sure what PlayMaker requires but you could easily make it a method or a watched field/property.

Abelius

Pharan написав
I don't think you can rely on using SkeletonUtility for FlipX. What you see in the inspector is just a preview-only field.
I don't know if it would work in a build.

You're right. I didn't realize this until now. :p

Mostly because the PlayMaker action seems to work when I point it to the component, as you can see here:

Strange...

Pharan написав
You should add a separate component that actually accesses SkeletonAnimation.Skeleton.FlipX
I'm not sure what PlayMaker requires but you could easily make it a method or a watched field/property.

I've changed the Set Property action to this one...:

...and it seems to work better. In the other case I needed to introduce an unwanted time delay to avoid a 'moonwalker' breakdancing issue when changing directions. 😃 So I suspect that other method, even if it works, must be really inefficient.

Thank you for pointing me in the right direction again.