O
Oogle

  • 28 sept. 2015
  • Inscrit 23 mai 2014
  • Hi Pelle!

    Really sorry for taking so long to reply.

    About your question, the unofficial spritekit runtimes still need a lot of improvements. If you decide to work with spine and sprite kit, you have to consider that you will have a LOT of restrictions when creating the animation on spine editor.

    If you are starting your app from scratch, you may consider using another engine like unity or cocos2d. Their runtimes are way better developed.

    In our case, we already had the app up and running on native iOS, so using cocos2d for example would mean re-coding everything. So we preferred to use the spritekit runtime and deal with the limitations.

    Cheers!
    Hugo

  • Using anything other than Sprite Kit now would cost us too much, since the app is already up and running.

    The 3rd party runtimes were a great start, but they lacked support for some basic stuff. But the biggest problem is that there are more then one. When we started using Spine, both sprite kit runtimes weren't updated for some time. We chose to work with one of them and made some improvements (we will make pull requests soon), but now the other runtime is being updated by the community. I hope an official runtime would encourage everybody to focus on improvements for a single runtime. Besides the contribution of the Spine creator would be great for optimising the runtime. 😉

  • Nate a écrit

    From a brief glance some time ago, the Sprite Kit API is pretty limited. I believe you can only draw rectangles. Without meshes it doesn't really make a great runtime target. UE4 will likely be done first. Sorry, but I wanted to be honest.

    Thanks! I appreciate your honesty! 🙂

    I understand that Sprite Kit doesn't support everything Spine has to offer, but I believe we can still do great things with it. For example, we are using Spine with Sprite Kit on our app (an app for kids, with videos and mini games) and it has helped us improve a lot the quality of animations and interactions. We could do it much more efficiently if we had a more robust runtime. :happy:

    Besides, I believe that an official runtime for Sprite Kit could make Spine more attractive to a broader range of developers and designers. Like the ones developing kids apps like us. These apps are very animation-oriented but don't have complex game mechanics. So using a game engine could be overshooting for most cases.

    Thanks for the attention!

  • Hey Nate! Any news on this? Could the official runtime to Sprite Kit be on your "next up" list? =)

  • Thanks for the quick response, Nate!

    I haven't lost any data, but it is good to know about the backup folder. =)

    Thank you!

  • I've just updated to version 1.8.36, and now whenever I add (or delete) an attachment to slot all the animation data is lost.

    Is anyone else having this problem?