Actually, turns out most people do not want code as much as ideas. I would highly suggest you take ideas from the code rather than trying to “copy” exactly what you see here.

If you want a free game engine obviously the code is here to take. If you want to learn to write game engines, take what you see here and improve on it in your own fashion.

My best guess is if you copied the code as is, you wont have a working engine. If you have learned from the design patterns implemented here and improved on them in your own work, well yeah, I suppose you would have something that works at this point.

Finally, the biggest complaint I have heard thus far is that the engine is too slow to actually make anything work for a game. As a result, I have taken a long time off of writing articles to improve on the basic design principals I chose to implement.

Hopefully, when the series returns it will be for the better.

Has anyone else tried copying the articles as-is up to this point and gotten anything to work?

I also get an error the first time I run, and the first time I exit…something with the gradient texture?

I very much like your ideas and will begin implementing in the engine. You are absolutely right, there is no reason whatsoever for each object to draw its own bounding box. Some sort of instancing will be done.

And, taking that thought one step further, Drawing each of these objects’ models individually probably lowers performance. Some sort of instancing mechanism would do well. Any plans on including that in the engine?