Re: Texturepacker Pro Mac License Key 31
Gro Bert
My use case is that I am *not* an indie dev. I don't work for an agency. I'm not a freelancer. I'm just making art for fun ? And so I'm not in the mood right now to drop $40 on something I may use occasionally ?
You could create a script that generates a pixi compatible json. Would be pretty simple if you skip trimming as the format basically tells the start point of image on sheet and what width / height it has. Though I'd recommend just using the free version of texturepacker if you dont need the licensed version features.
Choose "JSON hash" Data format and disable some of the advanced features like PngQuant compression and Pivot points - stuff you most likely don't want to use anyways in your scenario.
If image-names are of the format "", the texturepacker saves atlas region as name=, index=. Spine run-time doesn't understand this and attempts to looks for a region with name "img-name_number" ignoring the index element. This fails with "unable to find region" error. I modified the Atlas.c/Atlas_findRegion function to have the logic to consider index as part of the name:
This is working for me, but I am not sure if this is the right thing to do. I can't change the naming convention of the images as it affects bunch of other things. I don't see any settings on texturepacker to force it use the full image names instead of creating index value.
Is there a way to add multiple images at once to a slot in the Spine GUI tool? I would like to add 10s of images to a slot (say the wing of a flying bird that keeps changing every few frames) but I am forced to add one image at a time.
1) You can use this texture packer:
It has a "useIndexes" setting you can set to false.
... r#Settings
If you are using Texture Packer Pro from texturepacker.com then I would ask the author to add a setting for you.
3) No, you need to add them one at a time. Adding the image defines the attachment offset SRT. If your images are the same size then you will be saved some trouble when this feature is implemented:
-image-on-a ... c0059d9/18
I switched to the libgdx texturepacker. The GUI tool returns error if I use "useIndexes" in the pack.json settings file. Other settings work fine but if I add "useIndexes: true (or false)" setting, it gives an error:
Glad that worked for you. I didn't write or support the GUI version of my texture packer. Looks like it is out of date. My opinion is that texture packing is a command line thing, and one of the innovative things my tool does is used file naming conventions and subfolders to make a lot of configuration obsolete. They other cool thing it does is using the JSON files for further configuration. Note the pack.json files inherit everything from the parent folder(s) pack.json files.
I'm using the texture packer to create a spritesheet for use with Unity 4.3 and the new 2d features. I'm having a problem with spine creating a spritesheet with the correct animation order, it seems to want to jump around. If I export separate numbered files (sprite_01, sprite_02) it works fine. But when I either pack those separate files or I create my own spritesheet, it won't keep the correct order.
Afraid I don't know how Unity handles atlases well enough to give any insights here. I'll poke Nate and ask him to take a round on the forum soon. One of the Unity regulars might be able to help out in the meantime.
Maybe that's the problem. I'm not having Unity access the atlas at all. I'm just using it as a basic sprite sheet. But the texturepacker that comes with Spline does not seem to pack in the order of the animation.
Spine tries to pack as efficiently as possible. The order in which images are packed is not important. If you need your regions in a particular order, you can use the "index" that each region has by checking "use indexes" in the packer settings and naming your images with "name_xxx.png" where xxx is a number. The index field of each region will be this number, so you can build a list of regions from the atlas and then display your regions in sequence. More info here:
... ge_indexes
I am having a similar problem as the original poster. I would love to use Atlas, but need Spine to place the images in the same order as drawn in the animation. Do not care if it is efficient or not in how it packs the images into the Atlas. No matter how anything seems to be named, Spine will always pack the frames in non sequential order.. Checking use index does nothing different.
7fc3f7cf58