• Unity

  • Need Hlp！2 Skins on 1 png file with "Skin not found"

    anglais

Hello, everyone!

The previous artist left me several artworks with 1 .png file + 1.altas.txt +1 .skel + 1.json file (spine run-time version 3.3.05)

I imported asset .png+.altas.txt+.json files one by one and create new SkeletonAnimation for each and successfully played most of them.

However, which the .png file containts 2 skins is unsuccessful in totally the same importing way.

The Scene only shows the skeleton with no skins, and 'Materials' on Inspector of SkeletonAnimation retains 'Size 0' which cannot be changed. The 'Inital Skin' has a right list with 2 skins named 'Boy' and 'Girls' but nothing happened with any selection.

The Error Console shows "ArgumentException :Skin not found:Boy | Parameter name:skinName".

I tried to compare all these artworks with the example 'Goblins' but still get no answer. 'Goblins' presents well in same import ing method. I also tried to change spine run-time version(3.4, 3.5 etc.) and Unity versions, but still the same issue.

So is there everyone could help me with this error? Or the .Json, the Material, the altas, the SkeletonData which part may goes wrong?

Many thanks!

Related Discussions
...

Which version of the Spine-Unity runtime are you using, was it 3.3? Which Unity version did you use?

In general it sounds as if your exported assets and Spine-Unity runtime are of different version, could you open the .json file in a text editor and look at what it lists as version number?

One way to resolve some problems could be to use the "Texture Unpacker" functionality in Spine to extract the atlas to its single source files and directories, then you could test if some thing need to be re-arranged and re-export it with the desired Spine Editor version.

Also note that you could change the Spine Editor version to 3.3 via Spine -> Settings -> Version and then import the asset data via Spine -> ImportData.. to re-create the Spine project.

Harald a écrit

Hi Harald, thx for ur reply 🙂

The version number in .json file is 3.305

However, I couldn’t find the unity spine-runtime exactly version 3.305 on Github or anywhere. So I tried v3.402, v3.5 or other spine versions which Github supported. And I tried each spine-runtime on Unity5 and Unity 2017.

As you said it could be a version conflict between Json v3.305 and Spine-Unity Runtime v3.402.

Unfortunately, that’s the worst situation for me because I got a large number of previous artworks need to be re-exported.

If the version issue is confirmed, I will get two extra work to do:

  1. Find out the difference between v3.305 Json and v3.402 Json. Write a batch re-exported command or code to convert all json files to v.3.402
    2.Check the change log In Github, downgrade the spine run-time from v3.402 to v3.305 manually...

Either of them will be a hard job and a lot of work need to be done… So if there is any other easier way, please don’t hesitate to let me know.

Thanks!

Harald a écrit
sweven a écrit

However, I couldn’t find the unity spine-runtime exactly version 3.305 on Github or anywhere. So I tried v3.402, v3.5 or other spine versions which Github supported.

I just had a search through the legacy packages on our ftp and found this one:
http://esotericsoftware.com/files/runtimes/unity/legacy/2016/spine-unity-2016-07-01-lastSpine3_3.unitypackage

Thx for ur help again, Harald!

I tried setup the v3.3 unitypackage on Unity 5, but it also presented nothing on the scene with the same issue.
I tried setup the v3.3 unitypackage on Unity 2017, the 'Materials' can be changed to 1 somehow with a waring, but still so.

So next step I will try to find someone who can contact with the orignal designer to ask the exactly work environment, or ask for exporting again.

Anyway Harald u save me plenty of time on writing version-converting code or downgradiing check, thanks a lot 🙂 !

I tried setup the v3.3 unitypackage on Unity 5, but it also presented nothing on the scene with the same issue.
I tried setup the v3.3 unitypackage on Unity 2017, the 'Materials' can be changed to 1 somehow with a waring, but still so.

Hm, that's unfortunate. :/
It should work with Unity 5 rather than Unity 2017.

Did you test this in a clean setup (new Unity project with only the single spine-unity runtime imported) with no open scene? An open scene with SkeletonAnimation GameObjects in it could cause problems.

Just in case the version is the problem, here are some older packages, perhaps they are of help:
http://esotericsoftware.com/files/runtimes/unity/legacy/2016/spine-unity-2016-01-04.unitypackage
http://esotericsoftware.com/files/runtimes/unity/legacy/2016/spine-unity-2016-03-04.unitypackage
http://esotericsoftware.com/files/runtimes/unity/legacy/2016/spine-unity-2016-06-24.unitypackage