I’m going to write a game engine because I hate myself.

Chris Engelsma
2 min readOct 19, 2022
Photo by Matthew Henry on Unsplash

That damn canyon.

I’ve always wanted to make a game from scratch, and I don’t have a good reason why. There’s this itch at the back of my brain — the same gnawing that Evel Knievel felt when he yearned to jump the Grand Canyon. Only, he never did that jump — it ended up being his son. In truth, there were medical complications that prevented him from performing the stunt, but I’m sure it always left him wondering.

I decided I’m going to jump my damn canyon.

Photo by Bertrand Borie on Unsplash

I’ve never made a game engine before, but I have a basic idea of how one is to be put together. There’s threading, an event management system, graphics libraries, baking soda, vinegar, and food coloring.

For the primary language, I’m going to go with C++: like C, but object oriented. For graphics: Vulkan. Now your starting to get uncomfortable, I can sense it. Why not OpenGL? We’ll, it’s apparently going away. Eventually. Any moment now. It’ll probably go away the same time as Python 2.7 (never) but system architectures such as Apple are phasing it support, so I’m not going to bother with it.

Which is a shame as I’m actually familiar with OpenGL.

Please feel free to drop any resources that may help me as this is going to be a bumpy ride, and y’all are going to love watching me suffer, I’m sure.

Also don’t mention Unity. I know it exists and it’s great. It’s not a part of my canyon.

--

--

Chris Engelsma

Geophysicist, software engineer, and web developer. Hopefully if I throw enough spaghetti at the wall something sticks.