• Bugs
  • Exporting shifts placement in animation

  • Изменено
Related Discussions
...

I have been using the latest beta versions of Spine as they come and when trying to export now, it shifts the placement of a character's eyes. It's especially odd not only because it moves them when I click export (and does show up in the resulting gif, unsure about the json, but it's likely there as well) but also because if I cancel the export and hit undo, it stays in place but if I move it myself and then hit undo it then moves back into the correct original placement. I've noticed later that this is also affecting the sword which should not have been moved at all this current animation.

https://i.gyazo.com/0ac06f4d7520c52303439a6bc31406bd.mp4

This same shifted placement has started happening when making my fourth animation with this figure and is there at the creation of a new animation despite that is not the placement of the eyes or sword in the setup mode. These oddities are not present in Spine's animation preview view window.

Separately, also on the eyes, it seems to occasionally force-add a sheer keyframe when making other edits with the other tools when on auto-key but even with it off, it shows the sheer icon orange saying that a keyframe for sheer should be added when, again, the sheer tool has not been used.

It looks like you've encountered some pretty serious bugs. Is it possible to send us your Spine project and images so we can see the problems? contact@esotericsoftware.com We'd love to fix them ASAP!

Sure! This is a test project for practice so it isn't important itself but I know fixing bugs certainly is and if it's something that I did, I would like to know so I can avoid it in the future. I was toying around with it for a while trying to figure it out but considering it only started messing up after three complete animations and didn't affect the previous ones or the setup, I'm at a loss. Thanks for always being so willing to help!

Wow, this ended up being a major problem. Super glad that we found it, thanks for your help! It's been fixed in 4.0.39-beta which we'll release today.

Thanks! I'm glad I was able to help you guys find and fix it!