Nate wrote

Your 2D Toolkit runtime looks nice! You obviously are more knowledgeable about 2D Toolkit than I am. I hesitate to go off in the weeds and try to roll my own. Maybe your runtime could be the official runtime?

That'd be really great!

Nate wrote

If you'd like I can commit it to github, but then you'd need to fork it and submit pull requests to keep it up to date. Do you feel like doing that? This way I could also keep it up to date if something changes in spine-csharp, fix bugs, etc.

Lets do that way. I also thought about making that runtime as a part of spine-unity runtime as they have similar code.

For example, we can unify mesh generation or animation state for both spine-unity and spine-tk2d runtimes.

Nate wrote

Sweet! I'm all for working together to improve both spine-unity and spine-tk2d. I can commit your latest zip to git. Or, if you have a newer version maybe you want to fork the official runtimes and do a pull request to put in spine-tk2d? Improving on spine-unity would be great too, especially to support multiple material atlases.

I've added pull request to your repository. You can now merge it. So, when I need to release a new version I should do another pull request, right?

Hey guys!

Just added another pull request to main repo.

Spine-tk2d changelog:

• Multi-atlas support (yay! see the example)
• Better performance (submeshes generated only when needed)
• Extracted animation related code from tk2dSpineSkeleton to tk2dSpineAnimation component

Important note: you can notice that in multi-atlas mode there might be bigger number of draw calls than number of atlases. That's ok, it's needed for proper draw order as transparent geometry is sorted in submeshes, not in whole mesh.