spine-unity has been rewritten. It now supports using an atlas that has multiple pages.
spine-tk2d has been rewritten to match spine-unity. Most of the code is the same, but for simplicity it is duplicated. spine-tk2d now has the optimizations that spine-unity has already had for a while.
Superb 
Cheers Nate
2d toolkit user here, thanks Nate!
Seems to be having problems.
Opening Spineboy does this:
Material material = (Material)((AtlasRegion)regionAttachment.RendererObject).page.rendererObject;throws this exception:
InvalidCastException: Cannot cast from source type to destination type.
SkeletonComponent.Update () (at Assets/Spine/SkeletonComponent.cs:106)
Fixed in spine-csharp.
More broken stuff.
No thrown exceptions.
While making a new scene setup from scratch. (making a scene with a GameObject with SkeletonAnimation/SkeletonComponent from the raw stuff; json, atlas, png)
The material assigned to the skeleton data (and the atlas) isn't getting loaded onto the mesh renderer of the object with the SkeletonAnimation/SkeletonComponent. (and dragging the material into the renderer manually doesn't work either. The change just doesn't get applied.)
So I just get a pink thing with the polygons in the right place.
The example works, I assume you borked setting it up. You set size of Materials to 1 in the inspector? You added a material that matches the name of the atlas image, sans file extension? There should be log messages if something isn't set up correctly.
Yeah. The example does work.
That's why I specifically explained that it was from scratch. xD
Did you try setting up something from scratch?
Pretty sure I didn't bork setting it up.
I set it up two different times times. I have been setting up skeletons from scratch for months. xD
The same thing happens on my friend's setup.
But did the exact same thing on an old version of the runtime, works just fine.
atlas image filename : anino.png
atlas text source filename: anino.atlas.txt
atlas asset filename: atlas_anino.asset
material filename: mat_anino.mat
Is the material filename matching the name of the atlas image a requirement now?
I didn't change the size of the materials array in the inspector.
Trying to change it to any other number also doesn't work. It keeps going back to 1.
Just set up a new scene with the spineboy assets, in both spine-unity and spine-tk2d. Only problem I had was creating the atlas, something is messed up with the script that tries to create the atlas in the same directory as the current selection. Make sure you select something in the right pane of the Project window and it works. FWIW my atlas looks like this:
Image removed due to the lack of support for HTTPS. | Show Anyway
The material name must match the name of the corresponding atlas image, sans extension. It looks through the materials by name. I had no problem setting the number of materials.
I guess explain exactly what steps you are taking to setup a new scene from scratch.
Okay. I can get it to break consistently by setting the name of the material (.mat) asset to anything other than the filename of the image.
It seems to prefer the name of the image rather than the name of the material.
Everything works normally if they're the same. (This wasn't a requirement before. We named our materials mat_%%%%% 'cause it makes it a bit easier to find it in the project folder window, since the filename extensions aren't shown and the icons are kinda vague when you have dozens of them.) :p
(FWIW, the materials array that was acting up in the inspector was of the mesh renderer on the object itself, not the atlas asset.)
I hope other people don't run into the same problem.
Ah, sorry about the mesh/atlas asset confusion, I didn't think to disambiguate. If the atlas has a material with the wrong name, it should give a message like this:
Image removed due to the lack of support for HTTPS. | Show Anyway
The material name is important now that multiple materials (an atlas with multiple pages) are supported. Actually, I don't know why I didn't think about this before
we can look at the material's texture name instead of the material name. Then you can go back to naming your materials how you like. Committed!
I'm having a slightly different problem, I create the spine skeleton animation and not only the material doesn't show on the renderer ( the material array number fixed at 1 and doesn't allow drag-dropping ) but I don't even get to see any mesh at all on the scene tab, I've tried the above and didn't get any results... any ideas?
Also the examples work like a charm, even creating atlas and data assets from the raw goblin assets works... I wonder if it has to do with the exporting from spine... could anyone post pics of their export configurations?
Note you set the materials on the Atlas asset, not the Renderer component. The SkeletonComponent sets the materials on the renderer as needed.
Yeah I know, I've been doing everything "by the book" that's exactly why I guess it has to do with the assets exported from spine, more specificly the 2 text assets ( I doubt the png has to do with it ) and that's why I ask about the export config, maybe it would be good to make the tutorial video again with the last version of spine, cause the export box I see has some extra stuff...
Has anyone else had this kind of problem?
Ok this image is pretty much self-explanatory, have no idea of whats going on.
Image removed due to the lack of support for HTTPS. | Show Anyway
Animations work but the atlas is pretty much messed up. Any ideas?
Ehm, I guess the atlas file isn't right? If you open the atlas file as a text file, do the region coordinates correspond with the PNG? What tool created your atlas?
Is this that thing again where the atlas is over 1024x1024 and Unity is scaling the image down to 1024x1024 by default (thereby causing the atlas coordinates to be incorrect since they were for a larger image)?
'cause if it is, click on the image file in the project panel and override the import settings so Unity doesn't scale it down. This has happened to a few people before. (@[obrisani korisnik], think there's room for it in github? May I edit the readme?)
Ah, yea I forget about all the Unity gotchas. 
Sure, github PRs are most welcome.
