Explanation
Basically sprite sheet maker is a program I wrote for my own use for one of my projects (written over the amazing time frame of about an hour u_u). I've decided to clean it up and post it here.
Basically it allows you to take poorly formatted sprite sheets and run them through this program and produce well laid out sprite sheets capable of being easily imported into most game engines.
Blah, blah, blah. Simply put I needed to convert a bunch of sprite sheets from some well known websites, none of them were laid out very well so I decided to write this little tool rather than spend ages ripping all of them.
The tool is crude, and its slow, and its far from complete (new version soon hopefully, hate the current algorithem) but it does the job I need it for. Perhaps you may find use of it *shrugs*.
Next thing I'm going to do if I can get the chance is to change the algorithm (my god its slow u_u), and to add a window where you can change the index of each frame, as well as making slight positioning changes (saves opening paint and doing it
).
Example
An example of its use might be if you had a sheet like this;
You could remove the text and general crap, to get this kind of sheet;
Then run it through the program to get something like this;
+ A few positioning tweeks and you have a sprite sheet thats easily importable into a game engine.
Downloads
Build 1:
http://www.binaryphoenix.com/index.php?action=download&id=125Screenshot
Heres the contents of the readme file, save me from typing it all again;
---------------------------------
Sprite Sheet Maker
Copyright (C) 2008 Binary Phoenix
---------------------------------
This tool is pretty simple to use. All you do is drag an image onto the
left hand panel and the tool will try and process it into a more game
friendly format.
At the moment this tool is still very early in development and will
probably crash now and again. I apologise for this, all I can say is you'll
have to bear with my while I fix the problems.
Tips on use
- Remove text or exterenuous data from the image first.
If you don't do this the algorithem may pick up individual text
letters as frames. You really don't want this to happen as it may
cause very long progress times, and very messed up sprite sheets.
- Keep images small
The bigger the image, the longer its going to take to progress! Keep all
images as small as possible to keep everything going smoothly!
- Try and keep all things on one row
This isn't neccessary, but it helps fix indexing problems in the final sprite sheet.
There are a number of currently know problems, mainly;
- Very slow
This is due to the inefficient segmenting algorithem the system
currently uses. I'm currently working on implementing a faster
more efficient one.
- Emitted frames may not be in the correct order.
This is simply a problem on the side of the computer. Deciding exactly
which frames should go where is hard to determine, especially if they
are not lined up in the original image. The program will try as hard
as it can to organise them in a top-left to bottom-right grid but occassionaly
you may have to reorganise some yourselves.
- Problems with indexed color images (palleted images)
This is due to the method I'm using to read data from images. This should
be fixed soon.
- Problems with artifacts around a frame (dust, particles, .etc)
This is a problem with the algorithem currently in use. If the
artifact dosen't touch the main body of the frame it will be considered
a different frame by the algorithem. I'm currently implementing a
"tolerance threshold" into the system so it will accept artifacts within
a certain range of a frame.
- Progress bar may hang at 100% for a few minutes
This is due to some extra calculations which may take time but aren't
factored into the progress bar. Should be fixed in the next release.
