Unable to export different pages

Sscardario · 12 жовт 2016 р.

Hi, according to this page from Spine documentation:

http://esotericsoftware.com/spine-texture-packer#Folder-structure

you can export your images in different pages if you have them in different subfolders and if you have the "Combine subdirectories" option unchecked. But I haven't been able to do this from the export option.

The funny thing is that when I create the atlas from the Texture Packer option instead of the export option, it creates the pages according to the subfolders, even with the same options. It looks to me that is a bug, but I may have been doing something wrong.

I tried to run the export option to create just the json and the texture Packer to create the atlas and the images, but when I try to import to unity it's unable to find the regions that were in other pages. When I create both the json and the atlas+images, I can import them in unity withouth a problem.

I'm using Spine pro 3.4.02

I had posted this under the Editor threads but I think it belongs to bugs

Nate · 13 жовт 2016 р.

There are 2 ways to run the packer. The first, packing as part of data export, packs only the images that are used in the skeleton and does not use the folder structure or JSON configuration files. You'll need to use the second method, running the packer separately. I've added a note to the folder structure and JSON configuration sections to make this more clear.

Crocodilum · 17 січ 2018 р.

It's been a while for this topic, but my question is related.
I'm under Spine 3.6.50 on Windows.

I have a spine, for which the image path with 2 subfolders is as described in the folder structure link

Зображення видалено через відсутність підтримки HTTPS. | Показати в будь-якому випадку

So I wanted to have 2 big atlas textures in the end.

I tried to export with Data JSON, but as you mentioned, it won't work.

Note when packing is done as part of JSON or binary export, the folder structure is not used.

So the only way to obtain 2 atlas texture is with your texture packer. But it's not very useful because it takes everything inside the folders. On the project I'm working on, we often have placeholders into our spine, for which we just uncheck the 'export' option.

Зображення видалено через відсутність підтримки HTTPS. | Показати в будь-якому випадку

But texture packer doesn't care and takes everything, mixing unused image in the texture atlas. Making the process pointless for me.

If you can do it (having 2 texture atlas) with texture packer, why can't we have it with the JSON export? It would be soooo useful.

Nate · 17 січ 2018 р.

Crocodilum написав
If you can do it (having 2 texture atlas) with texture packer, why can't we have it with the JSON export? It would be soooo useful.

It would become complicated with how to configure the packer. When running on a directory, it uses pack.json files for configuration. When run as part of data export, it only packs the images needed. When run as part of export we could just run the packer on the skeleton's images folder, but this wouldn't really improve things

you'd have the same problem.

I suggest putting the images you don't want packed into a folder, then place a pack.json file in that folder containing:

{ ignore: true }

Now that whole folder and any subfolders won't be packed.

If packing more than one atlas, you could use the command line to make it easier. Note however that a single atlas could have multiple pages. You'd only need 2 separate atlases if you want to load one but not the other.