Ce site est optimisé pour être consulté depuis un navigateur moderne dans lequel JavaScript est activé.

[Cocos2d-x] Difficulties in using meshes

PixelPaul

Hello Spine team,

We have a strange problem about using meshes in our cocos2d-x v3 project.
We started with the creation of simple animations (moves, rotations and scales) on our main character and everything was fine.
Then, we added some meshes on the main character and animated the meshes on existing animations.

But by doing like this, it seems that there are conflicts between the mesh animations and the bone animations. Sometimes our animations are correctly played (mesh + bone animations together), but sometimes only the bone animations‏ are played. This is a weird behaviour.

For your information, we currently have the 1.9.01 version of Spine, and the spine runtimes are up to date.

Thank you in advance for your advice about this problem and do not hesitate if you have some questions.

PixelPaul

Søren

We haven't been able to do a large amount of testing on meshes for the runtimes yet. Nate is currently on vacation and will be back in a week, once he is back any lingering bugs in the runtimes should be fixed. Sorry for the trouble.

PixelPaul

OK Shiu, thank you for your prompt feedback.

Please let us know when you will be able to give us further information on that trouble 😉

Hello Shiu,

Do you know if Nate is back ?

Thanks

Søren

Nate just got back and will be going through forum threads as fast as possible. Hopefully it won't take long but there is a bit of catching up to do.

kingbeful

@[supprimé]
I'm using cocos2d-x 2.2.2, mesh and other features work fine for me.

And I'm running cocos on iOS device.

Nicolas Gaudin

Hello everyone,

I'm part of the PixelPaul's development team and I'm in charge of animations with Spine2D.
We tried to correct that problem by recreating animations at the origin of the conflicts.
However, we are still having the same issue and we are currently stuck.

Could you please give me a hand on that problem.

Thanks

Nate

We will need more information about the problem. I guess you are seeing different behavior in Spine than you do in cocos2d-x? Maybe show some screenshots? Does it work correctly sometimes? Have you tried to narrow down when it does or doesn't work?

PixelPaul

Hello Nate,

Here is some additional information about our issue.

The following screenshots show the simple animation without mesh like it was created in spine at the beginning :

Loading Image

The two next screenshots show the same animation in spine but with a mesh in addition :

Loading Image

Sometimes the animation with the mesh is correctly played in cocos2d-x like we can see in the following screenshot :

Loading Image

But sometimes it is the animation without the mesh that is displayed in cocos2d-x like in this screenshot :

Loading Image

After some investigations on this problem, it seems that it occurs when we play some other animations before, like the second one on the next screenshot.

Loading Image

To summarise the issue, here is a scenario of our problem:

First we play the animation at the start of the game, it is correctly displayed with the mesh like we can see in the fifth screenshot
Then we play another animation (for example the one named PA02 in the previous screenshot), these animation is correctly displayed
Finally we play again the animation, it is not correctly displayed (without the mesh), like we can see in the sixth screenshot.

Hope all these elements will help you to diagnostic our problem.
Do not hesitate if you need further information.

Thank you.

Hello Nate,

Could you please give us some feedback about our issue.

Thank you

Nate

Sorry I haven't had much bandwidth to service forum threads. 🙁 Thanks for the extra info. Is the issue that the first animation applies FFD, then when the second animation plays, the FFD from the first animation is still applied and looks incorrect? This is actually the expected behavior, see here:
http://esotericsoftware.com/spine-using ... on-changes
If this is the issue, you can call Slot_setToSetupPose when the animation changes to clear the FFD that was applied. Except looking at my pretty code, it seems Slot_setAttachment is not clearing the FFD as it should! Fixed in Git. If you just want to clear the FFD without affecting the slot attachment or color, you can just set attachmentVerticesCount to zero for every slot.

PixelPaul

Hello Nate,

Thank you very much for your answer and sorry for the late feedback.

In fact a call to the SetSlotsToSetupPose method is not a good solution for us as the setup pose is a totally different pose (the first frame of the idle animation) and so this frame appears between two animations.
But thanks to your answer I tested the solution to set attachmentVerticesCount to zero for every slot before changing the character animation, and it solves almost all our issues.

But unfortunately, we have still a problem with an animation transition. 🙁
Sometimes, some sprites of the animation are not at the correct positions like you can see in the following screenshot, but some other times the transition is OK.

Loading Image

More precisely it happens during transition of PA01 and PA02 animations that you can see in my previous post.

I suppose this problem is the same kind of problem than our previous ones but I can't figure it out, and I don't manage to find a proper solution to it despite of the clues you gave me.
So maybe would you have some others clues or advices to give us to resolve it.

Thank you

Hi Nate,

Just a kind reminder to be sure you will see my post 😉

Thank you !

Nicolas Gaudin

We still have not found the solution to our problem.

Can you please help us ? 🙁

Thank you !

Nate, we need your help please 🙁

Nate

Very sorry for the delay guys. 🙁

I tested the solution to set attachmentVerticesCount to zero for every slot before changing the character animation, and it solves almost all our issues.

This will reset the FFD for all slots. Normally this is done when an attachment is set for a slot or when setSlotsToSetupPose is called. If your animation is manipulating meshes with FFD and you change to a new animation in the middle of the first, it may make sense to reset the FFD for the slots.

Sometimes, some sprites of the animation are not at the correct positions like you can see in the following screenshot, but some other times the transition is OK.

Are you interrupting an animation before it ends? If so, maybe your first animation changes to attachment B, then at the end of the animation changes back to attachment A. If you switch to a different animation between those attachment changes, the skeleton will continue to have attachment B during second animation. Could that be the case?
http://esotericsoftware.com/spine-using ... on-changes

Are you mixing (crossfading) between animations? If so, does removing the mixing cause the problem to disappear? When crossfading bone rotation, the runtime needs to choose which direction the bone rotates to go from the first animation pose to the second animation pose. It chooses the direction with the smallest difference in angle. This is correct most of the time, but can be a problem for some animations. Eg, imagine an animation (maybe a jump or fall animation) where the arm is rotated to the 10 o'clock position (the character is facing right). If you mix from this to an animation where the arm is at the 6 o'clock position, the arm rotates the short distance which is physically impossible for a shoulder joint, so will look wrong. Because bones rotate often, this problem may only be visible when mixing to a specific animation from a specific pose.

You are using many animations for a jump? Maybe there is another way to handle it?

It's pretty hard to tell what I'm seeing in the screenshot. Can you do more digging to find exactly when it happens? It would be ideal to create a minimal test case, similar to the spineboy or other cocos2d-x examples, which you could provide to us so we can reproduce the problem.

PixelPaul

Hi Nate,

Thank you for your answer but unfortunately we do not manage to solve our issue 🙁

I will try to explain it more precisely.

First, we do not let the animation play over time but we update its time each frame based of the position of our character.
These two animations take place when we drag the character and we need to update its animation depending of its position and not depending of time. And when the character position changes a lot, we need to switch between two animations.
In consequence, the first animation is never finished when we switch to the second one.

I have tried to apply the methods SetToSetupPose(), SetBonesToSetupPose() and SetSlotsToSetupPose() but it does not solve our issue. As I said before, our setup pose for this character is a totally different position, and so if we apply it we can see a lot of artefacts due to this pose during one frame.

In addition, we do not mix the animations, we just use the SetAnimation method on our skeleton node to apply/change the animation.

Also, a strange thing is that the solution of setting attachmentVerticesCount to zero almost solve all this kind of issues (which was the same kind of issues with little artefacts displayed during one frame when switching between animations) but not that one.

Hope this information could help you a little to figure out our problem.
If not we can try to create a sample project to reproduce this particular problem but it won't be an easy task...

Anyway thank you for your help!

Paul

Hi Nate,

Do you have any leads for our issue please?

Also, we will send you our Spine project in case you detect some problems in the animations conception.

Thanks.

Paul