aimajin

So i'm working with the dev team here and giving them exports of mine, json exports. When they import into Unity it is not creating the Skeleton Data file. When they open the file, the skeleton info is in there, but it's not creating the skeleton in unity. Does that make sense? Has anyone else had this happen? We have tried every export setting under the sun...Thanks in advance.

version information
Unity 2018.2.15f1
Spine 3.8.84
aimajin
  • Posts: 2

SquaLLio

Do you know if they have tried instantiating the skeleton? They need to drag the skeleton data file into the scene viewport or the scene hierarchy, then select one of the three options. (SkeletonAnimation, SkeletonGraphic, SkeletonMecanim)
SquaLLio
  • Posts: 8

Harald

We are sorry for the troubles!

I guess it has been related to recent changes in the Hierarchy Panel drop behaviour that allow precisely selecting drop-target GameObjects as parent for the newly instantiated skeleton - however the empty region below the list of GameObjects rejected the drop, unfortunately.

This issue has just been fixed, it has been tracked under this issue ticket:
this issue: https://github.com/EsotericSoftware/spine-runtimes/issues/1614

New unitypackages can be downloaded here as usual:
Spine Unity Download

Thanks for reporting!
User avatar
Harald

Harri
  • Posts: 1485

DarkSlash

I had the same problem, and just created the Skeleton Data object by myself just right-clicking create->Spine->Skeleton Data and filling the object with the json and atlas.
DarkSlash
  • Posts: 6

aimajin

My dev guy said to explain a little more so here it is... we discovered a little workaround but doesn't really fix the core problem.

When we export a spine animation, the json data has an array of skins under the skins property each with a name and attachment property which doesn't properly generate a SkeletonDataAsset on import. However, if we convert skins to an object consisting of layers, the import process generates a SkeletonAssetData as expected

Hopefully that gives a little more insight on what's happening and what exactly seems to be causing the issue.

---

also, thanks for the input so far guys!!
aimajin
  • Posts: 2

Harald

aimajin wrote:When we export a spine animation, the json data has an array of skins under the skins property each with a name and attachment property which doesn't properly generate a SkeletonDataAsset on import. However, if we convert skins to an object consisting of layers, the import process generates a SkeletonAssetData as expected
Thanks for detailling the problem description. Actually it should not happen that an exported json file is not imported correctly in spine-unity. Are you sure you are using the same versions (e.g. both 3.8 ) of the Spine Editor and the spine-unity runtime? Are all extensions set up correctly (.atlas.txt instead of .atlas)?

If everything is set up correctly, could you please send us your project files as a zip package, to contact@esotericsoftware.com, then we will have a look at what's going wrong.
User avatar
Harald

Harri
  • Posts: 1485


Return to Unity