• Editor

  • [AS3 Starling] Skin attachment .json export problem

    İngilizce
Related Discussions
...

Hi !

I'm an animator who uses spine since just a few week, and i have met my first problem today.

My character had to be transformable, so i use the skins to do that. I've created 3 (default, amphibian and sasquatch). In the same time, i had created skins attachments for each part of the body. I assigned correct images in those skins attachment for each skin.

For the eyes, i created 2 skins attachment (eyes open and eyes closed) to make them blinks. So, i started to create my first animation. Everything works well, my character's eyes are blinking during the animation, that in every skin.

My problem is : when i export the skeleton (in .json) and test it, the keyframes i put on eyes's skins attachment visibility (to create the blinks) seems to be not working, only the keyframes on the bones are working… If someone could help me, i would really appreciate cause I really don't know where is the problem.

Thanks

  • Nate

  • Gönderi #3
  • Bu yayın İngilizce içinde

spine-starling has had a few issues lately, with whitespace stripped atlases, setting color, and possibly changing images. I hope we can work these out soon. After that I expect your animations will work correctly.

Ok,

Bali33, the developer i work with, added this to the issue list and we'll wait untill you could work on it.

Thanks for your answer Nate

Hi,

I have posted the issue on GitHub, but is it possible to know when it will be handle ?

I don't want a special treatment but not having SkinAttachment working in the AS3/Starling runtime make Spine really less useful. Is kind of the "basic feature" that make Spine really above other solution for us. It completely fit our needs. We at first really counted on this feature, but the demo version doesn't allow to export so we had not the possibility to test it before.

Thank you

It's a really tricky problem to fix, I did some digging into it yesterday to fix it. We'll try to have to fix it ASAP, but without knowing exactly where the root of the problem lies, we can't give you an estimate. Sorry 🙁

Hi,

That's cool that you guys are already working on it. But to be honest I'm a bit worried right now because really count on that feature for our next production. I hope you will find a solution soon.

Thank you Shiu !

  • Nate

  • Gönderi #8
  • Bu yayın İngilizce içinde

We posted on the Starling forums and did not receive support. Having Starling work correctly is very important to us, it is unfortunate we have to blunder around by ourselves to try to figure out an optimal low level solution. Doing that is quite time consuming which is why I've prioritized it after a number of other tasks (fixing crashes, etc). If someone from the Starling community would provide support and I had some idea of how to fix it in a reasonable amount of time, I would prioritize it higher. As it is, I will still get to it soon. I'm sure we will fix it, don't worry.

Hey Nate,
sorry for not replying earlier

I didn't see your post in the Starling forum when it was on the front page. Bali made me aware of it and I've just replied. I'm sure we'll be able to get this working. =)

  • Nate

  • Gönderi #10
  • Bu yayın İngilizce içinde

Hi Daniel! No worries, I appreciate that you support your OSS lib. I planned to escalate to you if I couldn't figure it out after another go, I'm just swamped and doing everything at once. 5 minutes after reading your response on the Starling forums everything was fixed, so we're good to go again! :party: I had a hunch there was an easy way to make it work, I just needed a little nudge in the right direction. 🙂

That's great !

Thank you both of you Nate and Daniel !