Hi guys, I've got a issue to found a easy way for Texture Packing using subdirectories :/
Currently, it's very impractical to export a spine with an atlas that doesn't combine images from several subdirectories.
We have to:
1) Export the skeleton as binary (or json) without generating the atlas. (otherwise it will only generate one texture with everything combined as mentionned in the documentation)
2) Export using Texture Packer to export the atlas
3) Edit the resulting atlas because it doesn't reference the images the same way as the .skel
With a folder structure like this:
The resulting atlas will reference images like this:
xy: 0, 3
But the .skle / .json expects them to be referenced like this:
xy: 0, 3
Notice the "images/" folder that's added when using Texture Packer.
The images are referenced properly when using the "create atlas" option during the binary export (But then the atlas only contains one texture)
Are we doing something wrong? We're not sure what's the point of using the Texture Packer export if skeletons can't use the resulting atlases directly.
Page 1 of 1
Hi Calire, I tried exporting the goblins project by placing a pack.json file in each folder and then using texture packer. The resulting atlas file has names like:
goblin/eyes-closedwhich should be what you want according to your description. Could it be that when you choose the folder to pack, you choose the project folder instead of the images folder of the project?
I don't think it's really alright to have it there, as you're only exporting skeleton and images of the current project, so that's why you can specify the atlas export, while with texture packer you can include multiple projects as well as images that don't belong to any Spine project.
Mark topic unread • Page 1 of 1
Return to Runtimes