Этот сайт лучше всего просматривать в современном браузере с включённым JavaScript.

[Unity]Shared Atlas between Skeletons

Mitch

kirie написал
Hi~
I have a same issue. May i ask some questions?

Our team are creating prototype of 2D RPG, and researching 2D tools.

We want to change weapon texture when equipped, and we can using skin & attachments.
But when we make another skeleton and export, weapon textures are included each skeleton atlas.

With different gender and races, we want make different bone for characteristic but use same weapon textures.
(e.g human male/female, angel with wings male/female)

We will have 150+ weapons and some common items.
If all item textures included in each skeleton atlas, resource size is too big.
Is there a better way in spine?

Sorry for my poor English.
Thanks.

I've wanted to address this directly for a while - finally made a video.

https://www.youtube.com/watch?v=Im0RB6musvA
(Don't know why its unavailable for embedded... here's the link)

PS:
Dear Nate,
Please make TexturePacker smarter.
Signed,
Everyone who makes games with Spine.

Nate

Seems like an odd way to do it. Why not use a single images directory that has the images organized in a way that the texture packer can use directly?

1) Organize images this way:

images/White
images/Skeleton
images/Equipment

2) Run the texture packer using "images" for the input directory.
3) Result: 1 atlas with 3 pages.

Mitch

Because then if I want to add a new character I need to re-export every single texture I've ever used in my project.

If I have subdirectories..

Apple
Orange
Zebra

I get Atlas.png Atlas1.png Atlas2.png
(Apple, Orange, Zebra, respectively)

and I add a new one called TexturePackerIsDumb

I get Atlas.png Atlas1.png Atlas2.png Atlas3.png
(Apple, Orange, TexturePackerIsDumb, Zebra, respectively)

and all my assets that are already packed in my deployed projects are now questionably linked to their original texture if I ever need to delta patch anything.

Pharan

One point of the shared (Equipment) atlas is so that you don't have to repack everything every time you add a new character.

That atlas could then also stand on its own for you to pull regions from in case you need to use it for an equip screen or something, where it might not make sense to load all the other characters' textures.

kirie

Thanks all : )