Ok that explains it. This is an older test project that I just wanted to play around with in Unity (before it was running in another engine).

Thanks!

28 Jun 2017, 19:39

Awesome support btw, you guys rock!

Was this information added "recently"? This export might be a year old or more. But it feels to me like this information should always have been part of the format?

Thanks for the tip! I'll try that out.

Another few pieces of the puzzle:

1. I unified line ending symbols in windows / mac / linux versions to rule that out and none of them work
2. Other spine animations work fine, the multi-texture ones are currently the only ones failing but it might be a coincidence that they are using multiple textures
3. I didn't do any special configuration of the plugin, just installed it in a clean unity project and copied the dragon files into a subfolder, went back to unity and it imported the atlas, created materials, etc. Just the skeleton data file is missing.

26 Jun 2017, 06:49

Hi! So doing it the way you described fixed the problem for me. I noticed that in my json file (a very old export), the entire ""skeleton": { "hash": "n52V4NfwL79zUxGmWJVMWUJgUhw", "spine": "2.1.27", "width": 519, "height": 497, "images": "" }," line was missing btw so doing it this way told me the json file was invalid (a line that is not printed to the console when auto imported).

Thanks!

There is no error in the console, I also tried reimporting like you said.
Oh and this is on a mac. A friend of mine could not reproduce it in Windows.
Is there a log saved anywhere that could tell me why it did not generate the skeleton data?

Oh and I reproduced this in a clean new project with only the unity plugin installed.

Cheers,
Daniel

Hi, I've found what appears to be a bug in the latest version of Unity and the Spine unitypackage version.

I copied the dragon.png dragon2.png dragon.json and dragon.atlas.txt file into another folder from the examples folder. It generates the atlas and material files correctly but no SkeletonData file.

Is this a known issue? Is it because of it using multiple textures in a single atlas?

I found this bug while trying to import my own animation which also failed silently so I tried it with the dragon example and found the same issue.

Unity 5.6.2f1
spine-unity-3_6-2017-06-24.unitypackage

Cheers,
Daniel

EDIT2: I found another issue related to the FFD implementation. In _spFFDTimeline_apply you memcpy too few bytes
memcpy(slot->attachmentVertices, lastVertices, self->frameVerticesCount);
should be:
memcpy(slot->attachmentVertices, lastVertices, self->frameVerticesCount*sizeof(float));

EDIT: It seems the old ffd example file doesn't work anymore, I replaced it with the latest one in the sfml folder and it now works!
I did find another big bug (memory overwrite) in there. It seems you create spFFDTimeline by casting from a base timeline struct which is smaller in size. I added some reserved space in the spBaseTimeline struct and the guard malloc now do not give an exception there. I found it by trying to debug some random crashes in spine so I debugged it with malloc guards to find this issue. Hope this helps!

Hi Nate, I integrated the latest changes in spine-c into our engine from github but now skinned meshes do not work. It seems this line:
i += 1 + boneCount * 4;
in spSkeletonJson_readSkeletonData function breaks it.

If I revert back to something like this:
i += 1;
It works fine again.

Am I missing something, I haven't had the time to really go through the code within spine to know if your change is correct and maybe something else breaks it or if you were too drunk to submit
J/K, thanks a lot for your hard work! I am looking forward to start using FFD, meshes and skinning!

Is there a better way to report bugs like this, email directly to you instead or forum is fine? I have found a few more issues of less importance that I would like to report!

Cheers,
Daniel