So you’ve decided to bite the bullet and are ready to make that video game. Excellent. You do a little bit of planning and you’ve got your game scheduled for release in three weeks time. Let’s get this done.
There’s a couple of reasons you might want to make a video game. Maybe you just finished the latest blockbuster AAA cinematic game released on the latest platform and you have ideas. Or perhaps you’ve seen some of those nifty little “indie” games that keep getting released that you see on Steam and think, yeah I can do that! Hey, maybe you’re a software developer and you’ve heard that game development will build up your skills.
Whatever the reason, you’re here, and you want to know how to make a video game. So let’s get started.
You’re making your game, testing it as you add new features. Man, it’s pretty fun. But something’s missing, it’s too quiet. You need some music. Sure you could go and download some music available online for free, but that’s not gamedev, that’s using other people’s work. So, let’s make our own music.
In Part 1 we handled rendering, and in Part 2 we went over the rest of the components needed for the engine. Now that we can draw things on the screen and we’ve got a plan, the next thing we’ll want to do is play music and sound effects.
When first learning to make games, I think it pays to begin by re-creating some of the classics. Think about it, a lot of those old games were made by one person, on a very small team that didn’t have access to the tools you have now.
One of the effects I needed for a previous game was creating nebula for outerspace. But as a pixel art game, the nebula needed to look… pixel-artsy?
Error handling in a state-based C API such as OpenGL in C++ can sometimes be a bit of a pain. To help me with my own graphics engine, I created this simple method of wrapping the OpenGL function pointers to report errors as they happen.