- Đã chỉnh sửa
Inconsistency in texture packing
Hello,
I am looking for a way to pack my atlas from the shell.
The issue I'm having is that the atlases generated by the Export panel are different respect those generated from Texture packing panel and from the shell.
From the Export panel: there is a "Attachments to Atlas per skeleton" option from a dropdown menu,
From the Texture Packing: there is just an Input / Output folder textbox
From the Texture Packing: in the Option box there is a Combine subdirectiories checkbox
From the Export panel: in the Option box there isn't
The shell works the same way as Texture Packing does.
My question is: is there any way to generate an atlas from the shell the same way it is generated by the Export panel?
It seems that texture packing doesn't care about any info given by the skelethon.
What I want to achieve is:
- Generate an atlas from the shell.
- Save an atlas with only the images actually attached to the skeleton, and not all those present in the folder.
- Polygon packing must work correctly.
Thanks in advance for any help!
What Spine Editor version are you using? I'd recommend having a look at the texture packer documentation Texture packing - Spine User Guide: JSON Configuration
You can export a pack.json file from the Export texture packer settings dialog that you can then feed into the command line export parameters:
Command line interface - Spine User Guide: Export
Mario đã viếtWhat Spine Editor version are you using?
I'm using latest Spine launcher and latest stable Version 4.0.58 but it works that way even in older version.
I saved the json with settings but acutally the problem persists:
Different outputs from editor and from embedded texture packer or shell.
There are multiple ways to run the texture packer. When packing as part of export, there are additional options and the Current project setting is not shown, because the current project is always used.
It is not currently possible to make use of the additional options when running the texture packer without doing data export. You can do data export with texture packing and then discard the data.
The general texture packer has no information about attachments in a skeleton, it only sees folder contents. As such, it's results will differ from exporting an atlas via the skeleton export dialog. However, the skeleton export packing and command line packing are the same if you supply the skeleton and pack.json file on the command line. What won't work is just passing the pack.json file on the CLI, as again, Spine wouldn't know about the skeleton's attachments.