Цей сайт найкраще переглядати в сучасному браузері з включеним JavaScript.

Texture Atlas management

jdtec86

I have spine project A. It uses texture pages t1 and t2. I have another Spine project B that uses texture pages t1 and t3.

From Spine I can export a 'combined' texture atlas that would combine t1 and t2, t1 and t3 or all three of those texture pages... but I want to easily be able to unload t2 or t3 (the texture atlases only used by one animation) at runtime.

In the c runtime if I were to unload Spine project B then how would I ensure that texture t1 remains?

Essentially, I don't want a single texture atlas per a project. I want to be able to have projects use multiple texture atlases with some of those atlases shared with other spine animations that might be running.

another example:

Textures.atlas

contains Textures/Shared/ and Textures/OnlyThisProject/

In this situation I'd probably have to unload the OnlyThisProject atlas page manually myself when it's not used I suppose? Probably by using spAtlas_dispose ().

Would be good to get some more thoughts on this before I embark on engineering down a particular path.

Nate

An atlas with multiple pages is just for convenience, so you can ask a single thing (the atlas) for a region, no matter what page it is on. This is dangerous if you aren't careful which images are packed to which page, as it can increase draw calls.

An atlas is loaded and disposed as a single object. It sounds like you want 3 atlases: t1, t2, t3. Then you can control when each is loaded and disposed. Depending on what runtime you use, you will need to customize the attachment loader. See AtlasAttachmentLoader, which fetches each region from an atlas. If you have multiple atlases, you'll need to write a loader that looks in each atlas for the region. An alternative solution might be to load eg 2 atlsaes, then create an empty atlas and populate it with the pages from the atlases you loaded. This way you have a single atlas with the pages you want, so you can still use AtlasAttachmentLoader.

jdtec86

Thanks for the input, Nate. As much as anything I wanted to check my understanding of what Spine can provide and if I had missed anything. I don't think I have on this occasion. I'm using the c runtime. I'll get to work on it.