- Edited
Issue with spine-unity runtime package from Feb 15
Hey everyone,
I'm brand new to spine-unity implementation, so I apologize if this is old news or I'm just doing something silly! I should also note that we're specifically using Spine in combination with tk2d.
Today we did our first test importing animations from Spine into Unity. Our artist and I followed all of the documentation on exporting from Spine, importing the unity-spine runtime package into Unity, importing the exported data from Spine, etc. But no matter what we tried, we were getting a "Couldn't load SkeletonData" error in the inspector of the SkeletonData object that gets created from the json. This error persisted after dragging and dropping the tk2d atlas data into the specified slot in the inspector, and added the warning "Some sprites may be missing". We double and triple checked export settings, version number and compatibility of Spine and the spine-unity package, Unity version number even. I even grabbed animation data from a friend at another studio, which is working fine for him in his Unity project, and imported it into mine - still no dice.
FINALLY I realized that the spine-unity runtime package was just updated 2 days ago, so I had that same friend package up and send me his version of the package (which he said he updated a month or so ago). It worked like a charm! All is well now.
All that to say - I don't know if the latest version introduced a new issue with tk2d compatibility, or if I just somehow goofed something up, but just thought I'd let you guys know! I'd be happy to provide more detail if it helps.
Cheers,
Chris
Thanks for reporting! We'll check it out.
18 Feb 2017 3:06 pm
The updated version should be up soon, albeit it'll have a slightly messier console log like it used to (but still report accurate errors).
We'll clean it up again as we go.