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

[Unity] draw Order Export issue

applemuesli

Hi,
We're running in an issue while exporting one of our characters. the draw order doesn't work, or unity does not recognize the changes in the latest export data. Anyway on another character everything still works fine.

example:
character 1
old export = works
new export = doesn't work

character 2
old export = works
new export = works

what leaves us with the result that the character 1 must be corrupted. However everything seems fine. When playing the Animation in Spine 2D you can see the draw order changing - also the export of the json seems ok..at least there are entries which seem to change it.
The draw order is not hidden or anything, it is keyed and also are the different attachments.

I've just wanted to ask if anybody has an idea what can cause this problem. To start from zero isn't an option. the animations are already set to music.

thanks :/

Søren

I've added [Unity] to the thread title here so Mitch will notice it. However he will probably need an example project if it is indeed a problem with the Unity runtime.

applemuesli

Hi,
found a solution - it seems that the export works when downgrading to Spine 2.0...so it's more a Spine problem than an Unity roblem I think.
but thx 🙂

jk12782187

Hi,

Is this a known issue? Has it been fixed in the latest Unity runtime?

(I'm using the latest Spine Editor but not the latest Unity runtimes yet (because I made some adjustments to the C# code)).

Søren

I'll notify Nate and hopefully we can have a fix real quick.

Nate

Can you post the old export JSON and new export JSON? If it is a problem with the data, a diff of those files should show what doesn't work.

mahart

I'm having the same problem with the exported drawOrder being incorrect. (I don't have any before an after JSON files to share unfortunately.)

Many thanks
Mahart

Mitch

http://esotericsoftware.com/spine-skeleton-viewer

^ test it against Skeleton Viewer and see if its still broken.

mahart

It's still broken in Skeleton Viewer, so looks like it is the Spine exporting process not picking up on keyed drawOrders.

p.s, We're seeing this in the Cocos2d-x runtime and it is present in Skeleton Viewer, so our thoughts are that there is an issue with the exporting process

Mitch

mahart a écrit
It's still broken in Skeleton Viewer, so looks like it is the Spine exporting process not picking up on keyed drawOrders.

p.s, We're seeing this in the Cocos2d-x runtime and it is present in Skeleton Viewer, so our thoughts are that there is an issue with the exporting process

"Sweet", I love things that aren't my fault heh. Nate.

Nate

I'll need something that shows the problem. Can you post or email a .spine file? contact@esotericsoftware.com

Pharan

May be relevant:
I opened an old skeleton json (exported 29 October 2014) and the Skeleton Viewer is not showing draw order properly.
Strange thing is that it the same skeleton is rendering correctly in the current version of Spine-Unity.

So, Skeleton Viewer might not be a reliable gauge, or something is really inconsistent among the runtimes? Or maybe it's just that the viewer download isn't as new?

Nate

Someone sent a project to show this problem and this is what I found:

The problem is the arm moves very quickly from frame 19 to 20. When you scrub the timeline, it snaps to whole frames so you don't see the interpolated frames between 19 and 20. If you hold shift while scrubbing, snapping is disabled (as it is at runtime) and you will see the problem in Spine. The fix is to move the draw order key to frame 19, so the hand is behind the head sooner. Note you can also hold shift while dragging a key to place it between frames.