Images path & Spine Texture Packer

createzone

Hi!

I found strange thing.

When I use spine texture packer with using Images path, file path in atlas is strange. And I can't see images in game.

<1>

<2>

Image <2>
Left : atlas file don't use spine texture packer
Right : atlas file use spine texture packer

And, I upload spine file and export files.
FilePathTest.zip

export/AllInOne : export files don't use spine texture packer
export/ImagePacker : export files use spine texture packer

I think this is because spine texture packer don't use image path in spine.

Thank you.

Nate

It isn't clear how you are creating your atlas. Are you running the Spine texture packer as part of data export or separately? You say you have an atlas that was created without using Spine's texture packer, so how did you create it?

The input directory you choose for the Spine texture packer won't be present in the paths specified in the atlas file.

createzone

Nate wrote
It isn't clear how you are creating your atlas. Are you running the Spine texture packer as part of data export or separately? You say you have an atlas that was created without using Spine's texture packer, so how did you create it?

The input directory you choose for the Spine texture packer won't be present in the paths specified in the atlas file.

Ofcourse I run the Spine texture packer as part of data export or separately.

Left : export json - check 'create atlas'

Right : export json - don't check 'create atlas' - use 'Spine texture packer'

BinaryCats

Spine's export texture packing is different to the texture packer.

That is, if you use the export (ctrl + e) to create the atlas, it will obtain different results to if you use the texture packer (ctrl + p). The reason is the export - for what ever reason - doesn't take certain texture packer settings into account (such as combine subdirectories).

Depending on how you export your textures you will need to use the same .atlas file. I.e. if your textures come from Export use the .atlas generated from the export. If you generate your textures via Texture Packer, you will need to use TP's .atlas file.

I think you may be running into this problem. as clearly have rotation option clicked in one, but not the other. Even though you may have the same settings in both Export and TP, Export will ignore certain setting.

Hope this helps

createzone

BinaryCats wrote
Spine's export texture packing is different to the texture packer.

That is, if you use the export (ctrl + e) to create the atlas, it will obtain different results to if you use the texture packer (ctrl + p). The reason is the export - for what ever reason - doesn't take certain texture packer settings into account (such as combine subdirectories).

Depending on how you export your textures you will need to use the same .atlas file. I.e. if your textures come from Export use the .atlas generated from the export. If you generate your textures via Texture Packer, you will need to use TP's .atlas file.

I think you may be running into this problem. as clearly have rotation option clicked in one, but not the other. Even though you may have the same settings in both Export and TP, Export will ignore certain setting.

Hope this helps

BinaryCats, thanks for your reply.
But It is not the problem about rotation. It's about image file path.

When I use Images path in Spine,

the result of export (ctrl + e) is different from that of the texture packer (ctrl + p).

Like this.

BinaryCats

What is your full input path. it should be something like

c:/.../YOUR PROJECT FOLDER

This is strange if yours is also this as I have just tested it, and my ouput would be (from the TP): A/logo_rolling_Stones

my settings are:
Loading Image

Nate

Your screenshots don't show the full path, but I guarantee you are not specifying the images directory as the input directory when you run the packer separately. You are specifying the parent of the images directory, which is why you see the images prefix in your atlas.

Nate wrote
The input directory you choose for the Spine texture packer won't be present in the paths specified in the atlas file.

BinaryCats wrote
The reason is the export - for what ever reason - doesn't take certain texture packer settings into account (such as combine subdirectories).

See here. Export packs images attached to the skeleton. Running the packer separately packs all images in a directory.