"Flipped" bones during runtime (using XNA sample project)

Pikso

Hi,

We are currently trying to render animations (from a custom setup) using your XNA sample project. But we ran into some issues.
Here is the setup (very straightforward):

But here is the result (compared to the animation in Spine):

As you can see most of the bones are "flipped" and/or "mirror" and it is difficult to figure out what is going wrong here.
We displayed some of the bones informations:
in white is the AppliedRotation of a bone
in green is the rotationY
and in red is the rotaionX.

Let me know if you need more infos,
Thanks in advance.

PS: Working on Spine Essential 3.5.46

Pharan

You're using spine-xna?
Are you using the latest runtime downloaded from here? GitHub - EsotericSoftware/spine-runtimes: 2D skeletal animation runtimes for Spine.
What do you mean by "We are currently trying to render animations (from a custom setup)"? Are you implementing a new renderer from scratch?

Nice animation, by the way.

Pikso

Hello,

Yes we used latest runtimes found on GitHub.
We don't create our renderer, we reused the xna sample, just loaded our custom json / atlas file in it.
Sorry, the "from a custom setup" was implying we were using a new skeleton we made, not re-using one from the sample data 🙂

After the first import, it used to work perfectly.
Then we added a few animations (and so we had to edit the skeleton setup a bit in Spine), re-exported and we started to have these issues on all animations from this file.

Thanks

Mario

Are you sure you exported from the latest 3.5.x? The runtime and editor versions must match. If you exported to JSON, you can find the version string from the editor version you exported from in the first line.

Pikso

In the code solution, in the readme, I found this :

"...spine-csharp works with data exported from Spine 3.5.xx"

and in the JSON :

"{"skeleton":{"hash":"vBZClceEcYutWQilj3LgykdsoAA","spine":"3.5.46"..."

So runtime code seems to match exported json file !

Pharan

Yup. Those are correct.

None of this makes sense. Both Unity and XNA share the same core spine-csharp. And spine-xna and spine-unity don't handle the bone transform. The core does.

Why would only specific bones be flipped vertically?

In your rig, is there something about those flipped bones that are different from the rest (the ones that didn't flip)? Do they have specific disabled inheritance?

Just a tip.
In your debug, instead rotationX/rotationY, you should use the internal matrix of each bone.
bone.A and bone.C are the x and y of the X-basis-vector of the bone. (red)
bone.B and bone.D are the x and y of the Y-basis-vector. (green)

Pikso

Hi, here is what I know,

l_arm and r_arm have both disabled (scale/rotation inheritance)
same goes for l_foot and r_foot. Everything else is set by default (both are checked)
From what I can guess, These bones (and only these ones) appears to be flipped (mirrored) and all of their childrens follow the same transformation (feet doesn't have any).

We followed your advice regarding the debug, but everything seems to be the same.
We tried re-enable some of the inheritance attributs and re-export the data to see if the render changes. It doesn't, except that the new inheritances applies correctly (with scale enabled on the feet, they are still flipped but recover the scaling value of their parent and seems to scale correctly during the entire animation).

Let me add how it happened (maybe it will help):
I did a simple setup, one idle animation and exported it so we could see how it looks in your sample project.
Everything seamed fine and I then added a few extra animations (run/jump). To do so, I modified the rig's inheritances (some of them weren't even used in the idle and it didn't change the animation).
Then, once we exported it a second time to integrate the new animations. Everything seemed broken (like on the previous gifs).

Still working on it I'll keep you posted if we find something else.

Any thoughts ?
(still struggling)

Pharan

Can you share your project with us? contact@esotericsoftware.com
You can just black out the images if you need to keep them from being used.

Pikso

Sure,

thx, I am on it (you'll have it by tomorrow).

Hi, It appears that the email you sent us is incorrect in some way,

I got 3 different email failure notifications ... I used this email twice and one found in an other support post, but I got the same result.
Could you send a other adress where we could contact you ?

Thx,

Pharan

We've received your email.

I think it has to do with the Bone.yDown logic not being applied in the situation where inheritance is disabled.

Can you open your Bone.cs and search for this line: spine-runtimes/Bone.cs at master
and instead of

if (skeleton.flipY) {

make it say

if (skeleton.flipY != Bone.yDown) {

That should fix it, but do let us know if it causes any problems for you.

Pikso

Hello,

Sorry for the late response, got busy...

The fix worked perfectly, thanks 🙂
No side effects encountered so far !

Is this fix specific for our issue, or a general issue ?
Will this be in the runtime git repo and iincluded with future update ? Or we need to keep in mind to merge this when we'll update ?

Thanks a lot ! :yes:

Pharan

It's already been applied on git, so no need to worry about this when updating.

Pikso

Awesome, thanks again for the reactivity !
That kind of support conforts us in our choice of animation tech 😃