• 2D shoot 'em up
SDL2 Rogue tutorial
SDL2 Gunner tutorial
SDL2 Shooter 2 tutorial
SDL2 Widget tutorial
SDL2 Adventure tutorial
— Sprite Atlas Tutorial —
A sprite atlas (or texture atlas) is a single image composed of many other sprites or textures. The advantage of using such an image is that it greatly speeds up the performance of games and applications working on modern GPUs. With only one source of image data to work with, the GPU has to perform very little context switching and is able to work faster. Image data can therefore be drawn in batches, resulting in very fast and efficient rendering. Building such an atlas can be tricky, however. In this tutorial, we'll see how we can use SDL to create an atlas and use it in a simple application.
This first part will focus on preparing our files for use, as there are a few things we need to consider when creating our atlas. As this is a tool and we're starting out, there will only be console output to view.
Unpack the code and then type make to build. Once compiling is finished type ./gen01 to run the code.
Inspecting the code
All the work for generating our atlas will be done in atlasGen.c. We'll start with the main function and work our way around.
main is quite simple. It handles the command line arguments, inits SDL, gathers the images for use, prints them out, and then frees all the data that was allocated. We'll look at handleCommandLine in a later tutorial. For now, let's jump straight to initImages, as this is a critical part of the atlas creation.
The initImages function performs three important steps: it counts the number of images available, so that we can allocate the right amount of memory to hold them; it loads the actual images themselves and stores them, and finally sorts the images. It finally returns the total number of images that are to be added to the atlas. Starting with the first function, countImages:
We're passing in the directory we wish to scan, and then iterating through all the entries contained within. We're using a C function called opendir and then reading each entry. Notice something important here: we are testing the type of entry that we have currently read, by testing the value of ent->d_type. If the value is DT_DIR, this entry is a directory. As such, will want to open it and scan the contents of it, too. This is done by calling the countImages function again, but this time using the path of the subdirectory we've encountered. This will allow us to recurse into subdirectories and count the total number of images available.
Take a look at the gfx directory. You'll see it contains 4 subfolders, each containing 5 images. If we only scanned the top level gfx directory, we'd not find any files, and the countImages function would return 0.
Something that's important here, too. We're testing that the first character of the filename is not a . (dot). When listing directory entries, two meta entries will show up: . (dot) and .. (double dot). These represent the current directory and the parent directory respectively. If we were to recurse into those, we could end up in an infinite loop and our program would crash (and perhaps even the computer). We therefore want to ignore them. This approach does mean that files that really start with a dot will be ignored, but that's of little consequence here.
Finally, when we do find a real file, we'll increment a counter (i) by 1. The recursive function called will then return its count, which will be added to the existing count of the prior call. This will ultimately count the total number of files found in all subdirectories of the parent.
With that done, and our array of Images has been created (see structs.h for the typedef), we can see the next major step in the initImages function is to load the actual image data itself. This is done in the loadImageData function:
Once again, we're opening the root directory and recursing through it. This time, however, we're attempting to load the image using SDL's IMG_Load function. Should this be successful (and it might not, because we might attempt to load a file that's not an image), we copy the filename into the filename variable of the Image item we're working with.
The final part of the function is a call to qsort, passing in the images that we've loaded. The function is simple, comparing the heights of the loaded images and pushing those that are tallest to the top of the list:
The reason for this sorting will become clear later on. It should be noted that we're only sorting the images that were actually loaded, which might be different from the number of files that we scanned.
With all that done, we can loop through our list of images and print them out. When you run the program, you will see a list like this:
[01 / 33] gfx/tall/long.png [02 / 33] gfx/misc/pinkTextured.png [03 / 33] gfx/cubes/bigGrey.png [04 / 33] gfx/cubes/bigGreen.png [05 / 33] gfx/cubes/bigRed.png [06 / 33] gfx/tall/multi.png [07 / 33] gfx/tall/turquoise.png [08 / 33] gfx/tall/purple.png [09 / 33] gfx/tiles/7.png [10 / 33] gfx/tiles/1.png [11 / 33] gfx/tiles/2.png [12 / 33] gfx/tiles/4.png [13 / 33] gfx/tiles/10.png [14 / 33] gfx/tiles/6.png [15 / 33] gfx/tiles/9.png [16 / 33] gfx/tiles/11.png [17 / 33] gfx/tiles/3.png [18 / 33] gfx/tiles/5.png [19 / 33] gfx/tiles/8.png [20 / 33] gfx/cubes/smallYellow.png [21 / 33] gfx/cubes/smallBlue.png [22 / 33] gfx/cubes/smallPink.png [23 / 33] gfx/spheres/lime.png [24 / 33] gfx/spheres/blue.png [25 / 33] gfx/spheres/orange.png [26 / 33] gfx/spheres/red.png [27 / 33] gfx/spheres/purple.png [28 / 33] gfx/ui/arrow.png [29 / 33] gfx/ui/plus.png [30 / 33] gfx/spheres/smallRed.png [31 / 33] gfx/spheres/smallGreen.png [32 / 33] gfx/spheres/smallGrey.png [33 / 33] gfx/spheres/smallCyan.png
But that's not very useful right now. In the next part, we'll look at actually creating the atlas image itself.
The source code for all parts of this tutorial (including assets) is available here:
It is also available as part of the SDL2 tutorial bundle (with on-going updates):
If you do not wish to create an itch.io account, you can also purchase the tutorial bundle using PayPal. This method will be slower, however, as it will require manual verification of the transaction.
Share your comments and thoughts below. All comments are anonymous and cannot be edited.