Separate Atlas per Skin.

FlyAnim

Would it be possible to have the texture packer to create atlas separated per skin?

I am taking the atlas and creating a normal map for it, but this kind of becomes impossible if everytime I add a new skin, the old atlases are completely rewritten and reshuffled.

Maybe as a checkbox in the exporter?

For now I will have to just create a skeleton with a single skin, and then programatically replace the skin I think.

Or maybe this is possible right now and I am missing something.

Please? :heart:

FlyAnim

duncanperham

What I do is simply swap the image folder with different skins. But then again, I am just exporting the animations as png sequence.

BinaryCats

Yes you can do this by using the texture packer and combine sub directory.

But I wouldn't do it like that if you are making normals. Just make a copy of the images and paint the normals on that image. Then texture pack your normal and defuse textures. So long as the images are the same they will pack the same.

This means if you change the face of your character, you only need to open the face_normal.png and edit it. Much easier workflow imo as during packing images can be rotated

FlyAnim

Will check that option, BinaryCats.

I am mostly unnerved because I will be adding new skins along development, and cannot risk the normals be reshuffled every time I add one. But the idea of just use the texture pack to pack the normals too may work.

Thanks.

BinaryCats

FlyAnim ha scritto
Will check that option, BinaryCats.

I am mostly unnerved because I will be adding new skins along development, and cannot risk the normals be reshuffled every time I add one. But the idea of just use the texture pack to pack the normals too may work.

Thanks.

You will need to use texture packer for both sets of images, as the texture packer exports differently to the standard export (as export ignores some settings)

We have a .bac script which would export our spine stuff and normals from spritelamp.

FlyAnim

Ah, that's a much better workflow.

However, something that got me was that I was sloppy and used the same normal texture for the front and the back of a character, and the Spine Texture Packer noticed and excised one. Obvs, on the diffuse side they were different. So I couldn't get both exports to match, since one group straight up lacked one of the textures. Had to read the .atlas to notice something was missing.

Once that was fixed (and double checked all my images had the same size, something I will make a script for in the near future), it did what I expected and packed both diffuse and normal textures in the exact same order, which I really need, since I will have to use the full texture to bind to the shader and them not matching won't do.

e: tested it, works perfectly.

Simlol

Hello guys, i might be slightly off-topic (and late) but this thread kind of contained the answer to a question i had, and now it seems there might be no easy way out.

My problem is that i am using skins in spine (and after export) in unity to swap through "damage-states" of a character. The plan would be to have each skin on a seperate text-atlas and (which makes it complicated) to generate something what has been reffered to as a "splat-map" to change just certain spots of the textures.

Now i can use texture packer in spine with the right options (set to "grid", "combine sub directories" unchecked!) to have all four texture-atlases align nearly perfect so that all the limbs,head etc are on the same position for each one. However i lose the json-file which i need to import into unity correctly.
But if i use "export data" with the same settings, the "combine sub directories" is ignored by spine and i get a atlas which doesnt provide me with usable positions, meaning all on the same spot.

First question now: is my impression true, that this "combine..." stuff is working differently for the two ways?

Second q.: does anybody understand what i am writing and has a suggestion for a workaround?

Sorry for bothering you all, i hope this makes any sense to you.
Best regards Simon

Nate

Simlol, you can export the JSON data without packing your images, and you can run the texture packer without exporting your JSON. See here about the 2 ways of running the texture packer and how they differ:
Texture Packing - Spine User Guide