このサイトを正しく表示するには、最新のブラウザを使用し、Javascriptを有効化してください。

Spine animation not rendered properly with Starling

c3ck1na

Hello,
Recently we started to use Spine in our animation workflow, but unfortunately we can't run the animation properly.
Our devs are using Starling + openfl. Haxe ports to be specific. At first this caused a problem with json files - they couldn't be loaded if exported from Spine v3.8. We found a way to roll back jsons to oder version from this topic: http://esotericsoftware.com/forum/rollback-Json-3-8-72-not-importing-to-3-6-53-12837

This works till the moment we tried more complicated animation: some images are missing, transparent, on wrong position or scaled too much. I am usually working on higher resolution, then scaling down the sprite sheet in pack settings to the desired size and giving the scale factor to the devs. As I said it's working fine for simpler animations and rolling bacj json version.

All animations are playing fine in the SkeletonViewer, except one image moving along path on v3.7 which has be removed, but problem remained.

https://1drv.ms/u/s!Ap4ai_Xu7lqWuEADXUYM6ZBmWWky?e=LE7kwB - inside this folder are uploaded previews of animations played with SkeletonViewer and previews from dev's side. Also 3 zipped exports included - working version from spine, rolled back version and rolled back version re-exported from spine. All scaled to 0.2, but root bone with scale 1.

Thanks in advance to whoever could suggest a solution!

Mario

Your issue most likely stems from the fact that you are rolling back the JSON files. This may cause loss of some data, as later Spine versions have new features you might be using, which can't be translated to older Spine versions. I assume you are using an old spine-starling runtime, which is the reason for the rollback? In general, you have to use the Spine Runtimes version that matches the Spine Editor version you used to export the skeletons. Anything else is sadly not supported. The rollback tool is a last resort, for when an artist accidentially used the wrong Spine Editor version. It is not meant as a production tool.

c3ck1na

Thank you Mario
Your are right, our devs use old version of spine-starling runtime because of lack of starling-spine-hx which supports 3.8.
By now I found a way to work on latest version in the editot, then roll back JSON and open it back in the editor, but in v3.6. Fixing not working animation and exporting it again. It's stupid method, but so far it's working.

Mario

Ah, I'm sorry you have to go through that tedious process 🙁 Going forward, I strongly suggest to fix your Spine Editor and Spine Runtimes versions so a situation like this can be avoided.