Thank you, Pharan, for your quick answer !

I will try to upgrade to Unity 4.6. Can you share the link to spine-unity runtime which can handle the data exported from Spine editor 3.1, please ?

Thanks again!

06 Oct 2017, 15:25

I checked out GitHub repository of Spine-Runtime and traced back the history. And it seems this is the last commit which states "spine-unity works with data exported from Spine 3.1.08": [Unity] Ragdoll fix (#596)@4b9d1b4.
Next commit (only counted if it touches spine-unity, spine-csharp) states that it's for Spine 3.2.

So, I think that I would try spine-runtime at that commit to check with Unity 4.6 first. Then if new problem appears, I will go back to ask for help. Thank you so much, Pharan.

Hi everyone,

I need to integrate Spine into Unity (used to do it before easily with newest versions), but this is a bit complicated as following:

• Animators need to stick with Spine Editor 3.1.08 (to sync with other projects)
• Unity version is 4.2.2 (code base is from 2012, nothing I could change here )

So, which spine-runtime library should I use to integrate Spine 3.1.08 with Unity 4.2.2 ? I'm so confuse now, since I took a look at official support sites and GitHub but hardly found a thing

Thank you for reading !

@Nate: your code overwrite the arguments in command line, so the input must be "C:/test/CoilGrapple.json" and the output will be "C:/test/CoilGrapple-fixed.json"

Hi ryanm,

I'm facing same problems with you about exporting animations from updated Spine v3.3.03. I know that Spine v3.2 will work but I don't know how to revert my Spine.

So, can you tell me how you do it (both Spine and Spine project files, right?).
Thanks a lot!

I'm using spine-csharp and spine-unity runtime. I have the same problem here, do you have a schedule to update them yet?

ryanm написал

Bump - I'm having this issue as well.

Reproducable with the newest version of Spine, the latest .unitypackage plugin, and Unity 5.3.5 in a fresh project.

---

16 Jun 2016, 12:20

---

I rolled back to Spine 3.2.01 and re-exported. Everything works again.

The problem is in 3.3.03.

How can you rollback Spine ? I would like to know about it to help our animators. Thanks

Our animators have just updated Spine from v3.2.x to 3.3.03 !
After importing new exported files to Unity, there will be errors like following:

IndexOutOfRangeException: Array index is out of range.
Spine.MeshAttachment.ComputeWorldVertices (Spine.Slot slot, System.Single[] worldVertices) (at Assets/spine-csharp/Attachments/MeshAttachment.cs:123)
Spine.Unity.SkeletonRenderer.LateUpdate () (at Assets/spine-unity/SkeletonRenderer.cs:555)
Spine.Unity.SkeletonRenderer.Initialize (Boolean overwrite) (at Assets/spine-unity/SkeletonRenderer.cs:203)
...

I have updated spine-runtime (c-sharp & unity) to the latest version on GitHub, but the errors are still there.
I have compared the JSON files generated by old version (3.2.x) with the new ones (3.3.03), and there're a lot of changes, like: mesh => weightedmesh, deform => ffd...
Personally, I think we need new spine-runtime to parse new JSON files.

Please help me to deal with this. Thanks a lot !

16 Jun 2016, 19:22

After digging deeper into JSON file, I realized that the attribute "type" of each node in the skeleton are swapped (mesh <=> weightedmesh).
So I think the problem comes from the exporting process of Spine, which messed with these values.
After changing values of "type" from "mesh" to "weightedmesh" in JSON files manually and vice versa ("weightedmesh" to "mesh"), everything works now.
But I still think that Esoteric needs to take a look at this issue, because there might be other problems.

At least I found a workaround for this at the moment, phewww!