Yes, that method should work for other dimensions just as well. Simply change the values you're entering on step 7. :)
As for how to determine the frame size and offset... Rubberduck explicitly listed 16x16 in the tags for this one, but it's not always so easy.
Usually I'll pick a tile in the spritesheet with a clear border (for example, the trusses at 160,80)
Open the spritesheet in GIMP.
Menu bar > View > Show grid
Menu bar > Image > Configure Grid
Then I start adjusting the grid width and height until the grid lines seem to line up with the tiles, paying special attention to the tile I picked out earlier.
It involves some guesswork, but this method works pretty fast for me. Most spritesheets have dimensions in powers of 2, so 16x16, 32x32, 64x64 are pretty common. Often the width and height are mixed and matched, though: 16x32, 32x48. On the other hand, there's no rule that says sprites MUST be powers of two, so you'll sometimes encouter sprites with strange dimensions like 21x33. Other times, the graphics is set to conserve as much room as possible, so the sprites are not arranged in a grid (sprite-atlas) but in wherever they will fit.
For example, this pixel dungeon spritesheet (below) has sprites in multiple sizes (16x16, 14x20, 32x32, 35x35, etc) In these cases, no amount of grid tweaking will properly slice all the sprites. Some tools like Unity have texture atlas tools that help auto-slicing the atlas, but other than that, there isn't a good easy way to do it with atlases. Just open it in gimp and start manually cutting each sprite out.
Ah, looks like rubberduck set them up so the overflowing tiles are adjacent. I was wrong about the offsets. It's a 16x16 spritesheet with some tiles having overflow. So, here's how to split them out into individual tiles:
The sprite dimensions for this sheet are not grid-aligned. They appear to be 16x16, but separate sections have different offsets, which makes this more of a "sprite-atlas" rather than a spritesheet. Can you tell me where this came from?
As mentioned in that other tread, I usually use GIMP, though Piskel also does well. It would help us understand what you're trying to accomplish if you would attach the spritesheet you're working with to this topic thread.
@MetroVG Studio Bluebird: This submission has been marked as having a licensing issue while we investigate. Downloads are disabled. Can you provide more information about the circumstances? Please Private Message me links to the documents you've mentioned and/or the relevant JASRAC entries.
Don't be calling it before the finish line; there's 29 people participating and they still have 10 days to submit. I turned in my last jam submission with only 8 minutes left on the timer. :)
curate. some things it's obvious why they were deleted: poor quality, duplicate, licensing issue. This collection is things that were deleted, but I can see no reason why they were deleted and hope to contact the author to bring them back.
Yes, that method should work for other dimensions just as well. Simply change the values you're entering on step 7. :)
As for how to determine the frame size and offset... Rubberduck explicitly listed 16x16 in the tags for this one, but it's not always so easy.
It involves some guesswork, but this method works pretty fast for me. Most spritesheets have dimensions in powers of 2, so 16x16, 32x32, 64x64 are pretty common. Often the width and height are mixed and matched, though: 16x32, 32x48. On the other hand, there's no rule that says sprites MUST be powers of two, so you'll sometimes encouter sprites with strange dimensions like 21x33. Other times, the graphics is set to conserve as much room as possible, so the sprites are not arranged in a grid (sprite-atlas) but in wherever they will fit.
For example, this pixel dungeon spritesheet (below) has sprites in multiple sizes (16x16, 14x20, 32x32, 35x35, etc) In these cases, no amount of grid tweaking will properly slice all the sprites. Some tools like Unity have texture atlas tools that help auto-slicing the atlas, but other than that, there isn't a good easy way to do it with atlases. Just open it in gimp and start manually cutting each sprite out.
Fortunately, in this example, Zombietom uploaded all of watabou's individual spritesheets in a zip file as well, so there is no need to slice this one image manually: https://opengameart.org/content/pixel-dungeon-graphics-by-watabou
Ah, looks like rubberduck set them up so the overflowing tiles are adjacent. I was wrong about the offsets. It's a 16x16 spritesheet with some tiles having overflow. So, here's how to split them out into individual tiles:
The sprite dimensions for this sheet are not grid-aligned. They appear to be 16x16, but separate sections have different offsets, which makes this more of a "sprite-atlas" rather than a spritesheet. Can you tell me where this came from?
As mentioned in that other tread, I usually use GIMP, though Piskel also does well. It would help us understand what you're trying to accomplish if you would attach the spritesheet you're working with to this topic thread.
licensing flag lifted: patent troll.
@MetroVG Studio Bluebird: This submission has been marked as having a licensing issue while we investigate. Downloads are disabled. Can you provide more information about the circumstances? Please Private Message me links to the documents you've mentioned and/or the relevant JASRAC entries.
Amazing.
Don't be calling it before the finish line; there's 29 people participating and they still have 10 days to submit. I turned in my last jam submission with only 8 minutes left on the timer. :)
curate. some things it's obvious why they were deleted: poor quality, duplicate, licensing issue. This collection is things that were deleted, but I can see no reason why they were deleted and hope to contact the author to bring them back.
5 hours?! did you use anything as a base?
Pages