If you haven’t already read the intro to this tutorial, you can find it here. In it we are introduced to sprite sheets, what they are, and some examples for where to use them.
One of those examples included combining many assets into a single sprite sheet. We can then extract a portion of this bitmap as its own unique element and use it as if we had loaded it separately. This kind of sprite sheet could be used for a variety of things. Maybe you’re designing an interface and you want to group similar UI elements in order to load them all at once. You could also find yourself developing a game in which there are many items for the player to collect and you need an easy way to organize them. The example below shows such a sprite sheet:
Images © Nintendo
Like we mentioned above, this kind of sprite sheet would be the most useful to us if we had a way to extract an individual element from it. Thankfully with the help of some code and a little Triforce of Wisdom we can do just that.
Flash Builder 4
I’ve been using Flash Builder 4 beta for a couple of months now and for the most part have been quite pleased. FB is the follow up to Flex 3. Adobe states that the name change is to help distinguish between the open-source Flex framework and their commercial IDE. Makes sense, but personally I like the name packaged with the initial beta release – ‘Gumbo’!
So anyways, the license on my copy of Flash Builder mysteriously stopped working yesterday. After a brief panic attack I decided to check out the Adobe Labs website and noticed that the beta 2 release was out. Cool! As with beta 1, my Flex 3 license is supposed to provide me with a new working FB copy – however, licensing software is one of my least favorite things to do so I’ll get back to that after the weekend. The renewed 60 day trial will suffice for now.
In this post I would like to introduce you to a custom class I wrote for working with sprite sheets. Now “what’s a sprite sheet?” you might ask. Well, while I’m not going to delve into much of the theory or the speed benefits from using them, you should know a few things:
A sprite sheet is a collection of sprites arranged into a single image, where each sprite represents a frame of an animation, an asset, a part of an image, or something to that extent. The idea of a sprite sheet has been utilized for a long time, namely in early gaming systems like Atari and Nintendo. In recent times they are most often used for efficient bitmap animation and are extremely useful in tile based games for level creation.
When loading external assets, many times you will find that it is much more time and code efficient to load many in one state – Not to mention that when used effectively this can save memory. Also, once you start animating many objects in a scene you will see a real performance spike when compared to regular Flash keyframe animation. Props to 8bitrocket for some useful info.