• RuntimesBugs
  • Spine 2.1.27 shows wrong animation

I am trying to use spine in pygame with the repo https://github.com/Hook25/spine-python3
The example works but my file was in version 2.1.27, it doesn't show the right animation, so I guess it's about the version. I first used Skeleton Viewer 2.1.27, which gives the right animation. And then use Spine 2.1.27 (I have to unpack the atla with a newer spine version to load the images), but it gives wrong animation.

Related Discussions
...
textasset.zip
196kB

Here are the json, atla and png files. :

That's GitHub repo doesn't use our Spine Runtimes code, so it's hard for us to say what is going. You'd need to know what version of the Spine data that runtime expects. You'll need to use the matching version of Spine to export your data.

    Nate According to the information in the json file ""spine":"2.1.27"", it should be 2.1.27, the thing is that Skeleton Viewer 2.1.27 gives correct result while spine 2.1.27 doesn't.

    • mwhite hat auf diesen Beitrag geantwortet.

      mwhite I feel that its bone animation look right but the sprites have a offset from where they are supposed to be.

      I find that using a proper scale and translation make the animation look right, but when i translate and scale the regions, the inactive ones aren't affected. So can I just scale and translate the bones without affecting the regions or make scale and translation affect inactive ones ?

      • Nate hat auf diesen Beitrag geantwortet.

        As Nate said, the runtime you are using doesn't state what Spine version it supports, and it's not maintained by us. I had a look at its code and its impossible to say. I suggest you ask the author fo the runtime via an issue on his repository on GitHub.

        The examples here:
        https://github.com/Hook25/spine-python3/tree/master/spine3/pygame_examples/data
        They are so old the JSON doesn't include the Spine version. It's anyone's guess what version the runtime supports. We can only say it's old.

        mwhite I find that using a proper scale and translation make the animation look right, but when i translate and scale the regions, the inactive ones aren't affected. So can I just scale and translate the bones without affecting the regions or make scale and translation affect inactive ones ?

        I'm not sure what you mean by this. You may need to set a scale when you do Import Data:
        http://esotericsoftware.com/spine-import#Scale
        The scale needs to match the scale used to create the atlas. If you don't know, you'll have to guess: 0.25, 0.33, etc.