• Unity

  • Unity adding indefinite amount of skeletons. Bug or?

    inglés
Related Discussions
...

Hi.
When I click on SkeletonData asset in Project it starts to create the skeletons in Hierarchy indefinitely while the SkeletonData is chosen. Is it a bug or some weird setting I don't know?

Watch the screenshot attached.

I use 2020.3.20f1, Runtime 4.0 and Spine 4.0.56

All you're doing is selecting the asset and it is doing that? That is definitely not the intended behavior. You should have to drag the SkeletonData asset into the Hierarchy or Scene View to create a new skeleton.

While its possible that its a bug with the Spine runtime, I feel like it's more likely something else interfering - do you have any plugins or 3rd party assets that could be affecting this? Any sort of hotkeys or anything like that?

Are you on Mac or PC? Could you record a video of whats happening?

I'm using Mac. No hotkeys, no dragging, no other plugins, no other actions, just selecting SkeletonDataAsset
This is the video: https://gyazo.com/9863924795b1866103d1747ea50d10a4

Also I realised somehow it's happening only with one bunch of skeletons exported from one file with single atlas. I have other skeletons in project and I can't see this bug while selecting them

I'm attaching the screenshot of export settings just in case.

Done

Cheers, I'll have Harri, our local Unity wizard, have a look at it once he returns from his vacation.

8 días más tarde

Sorry for the delay.

Thanks for sending the reproduction files, I just had a look at it. Unfortunately I could not reproduce the problem you were showing. Which version of the spine-unity runtime (name of the unitypackage, also listed in Assets/Spine/version.txt) are you using? If you are not using the latest unitypackage, could you try upgrading the spine-unity package?

Could you please also show the content of your Console window in Unity when this problem occurs? It most likely shows some error messages there. If you could please copy and paste the first error message that you see in the console here on the forum, we could have a look at it and potentially prevent such problems in the future.