Multiple use of same skeletonData breaks Z order

RemDust

Hi guys !
🙂

The game is running in Unity, it's local multiplayer and every "player gameobject" has its own skeleton though they share the same skeletonData exported from Spine.

With a single player there is no problem but with multiple players the draw order of the different players is messed up. 🙁

I should also say that every character subscribes to skeletonAnimation.UpdateLocal, I don't know if that's relevant. :wait:

I guess the easy workaround would be to export multiple skeletonData but it doesn't sound satisfying :/

RemDust

Pharan

Are you aware of the Unity 5.6+ bug where sorting breaks if you have multi-material MeshRenderers that share materials?
It tries to batch draw calls, but breaks sorting in the process.

If that's your case, you need to either add Sorting Group component, or make sure each skeleton only uses one Material.

RemDust

Thanks for your answer Pharan 🙂

I'm running Unity 5.5 but maybe the issue is the same :wonder:

I read a little about sorting group but they seem to be helpful when the order break if characters are positioned on top of each others, it's not my case, it breaks even if players are far from each others. 😢
Having one material per skeleton involves re-exporte multiple json from Spine for every modification I would operate in Spine editor right ? It seems like a pain in the neck and not really satisfying to have like 4 exactly identical materials and atlases. :S

Pharan

No, they don't need one unique material per skeleton instance.
Each skeleton just needs to use 1 material instead of 2 or more. It doesn't matter if it's shared.

Sorting Groups are only in 5.6. I'm not sure about the bug existing in 5.5.
But people had that problem, and Sorting Groups helped them.
Submeshes render in random order with orthographic camera
Sorting Error on Start
z fighting with multiple prefabs

Again, not sure if that's the same problem you have.
You'll have to describe your setup more if it's not.

RemDust

This was a FastAsLight Pharan's answer ! 😃

Thanks man, exporting a single material from Spine solved the problem :beer: