Existing Sprite Sheets :wonder:

BBBower

Currently I have 40 or so different sprite sheets.
I need to import the sprite sheets into spine.
Example. sprite_head.png has each of the different facial expressions my character can make 48 pixels by 48 pixels. This sheet is currently 20 frames wide (20*48) = 960. Many of the other parts of my character are also broken down into sprite sheets. Each sub image is necessary even for my spine animations. However I do not want to take the long amount of time it would take to break each sprite sheet down to individual .png files. (would be hundreds of them)

Is there a way to only pull an image part ie (x,y,width,height) from a .png file without having to break the image down. Or to pull all of the sub images from my large image?

I would assume it would be a method seeing as how Spine exports the textures in a manner similar to how my sprites area already exported.

Thanks in advance!

Nate

Look for a tool that does spritesheet -> individual images or you can write code to do it. If your sprite sheets are a grid, it is even easier. If your spritesheet is a Spine atlas, libgdx has TextureUnpacker which turns the atlas into individual images.

BBBower

Nate wrote
Look for a tool that does spritesheet -> individual images or you can write code to do it. If your sprite sheets are a grid, it is even easier. If your spritesheet is a Spine atlas, libgdx has TextureUnpacker which turns the atlas into individual images.

They are not an atlas file, but disassembling the atlas file it seems it would be very simple to create an atlas file for my sprite by hand. And yes my sprite sheet is already in a grid.
I was hoping there would be a support option for importing existing sheets rather than cutting them up because my characters already have attachments that are pre built with the idea of layering them on top of each of the other sheets. Meaning for each direction the head can turn I have a hat / helm / facial hair sprite in the pixel perfect location on a separate sheet image so they could be cycled out easily.

My characters have an 4 directional top down drawing scheme and the sprites for the armor / shoes / ect.. are all finished. I would just be using Spine for those fine adjustments of tilting, head / chest movement from breathing and possibly cutscene / movie like character animation. Generally i would like to just swap out the image via code in my game to update the (item / accessory / body / head) to the animation, ex Changing the armor from metal to cloth and simply identifying the new image rather than having to import each image piece separate and assign them internally. I could have coded an engine to display it myself but the features spine had already were what I had already pictured in my head and it made it worth the price for the shear amount of time it would save me. However the number of small sprites for each piece i have enters the thousands, cutting them and re-placing each cut piece into spine is going to be hurtful especially considering all i'd really need to do is define a couple of attachments.

Nate

I'm afraid Spine attachments require a single image, Spine doesn't understand spritesheets.

You can setup your skeleton in Spine with a single attachment for each slot. At runtime you can create attachments on the fly, there's no reason to import them all into Spine if they attach at the same position, unless you want to key them in animations in Spine. Even then, you can setup a single skin and key your attachments, then generate a skin and attachments at runtime.

If spritesheet is designed for layering, it's likely you have a lot of whitespace in each grid cell. It may be a big savings to split your spritesheet into individual images and then pack them in an atlas with whitespace stripping. Then again, if you don't need the savings it isn't worth the effort.

BBBower

Nate wrote
I'm afraid Spine attachments require a single image, Spine doesn't understand spritesheets.

You can setup your skeleton in Spine with a single attachment for each slot. At runtime you can create attachments on the fly, there's no reason to import them all into Spine if they attach at the same position, unless you want to key them in animations in Spine. Even then, you can setup a single skin and key your attachments, then generate a skin and attachments at runtime.

If spritesheet is designed for layering, it's likely you have a lot of whitespace in each grid cell. It may be a big savings to split your spritesheet into individual images and then pack them in an atlas with whitespace stripping. Then again, if you don't need the savings it isn't worth the effort.

Yes there is quite a bit of extra space in between the sprites that would benefit saving, although they are very small in size. I'll edit his post with an example when I get home to see if someone may be able to better direct me. The real bounty with my current setup is I can change an armor, helm, pants, ect... on one sprite image or even add a new one and not have to do anything but change the image the layer directs to in the game. Although I have some extra space around the sprites this allows me to create large or small armors without worry for size issues and implement them with a simple player.armor = armor5.png and it will apply to each of the 4 directions of my sprite including their animations. This gives me a lot of versatility in adding / changing things without need to reinsert each piece. I guess the easiest fix would be finding a way to make an atlas point at my current image, cut each sprite with that atlas file either by hand or some utility[ if anyone knows one], then import them each to Spine. Again I'll edit this post later when I have an example to show. Thanks 🙂