English

Game Engine Anatomy 101

About the Author Jake Simpson is a games programmer who's been in this business off and on for about 20 years. He started at age 15 in his native England, in the days of the C64, Sinclair Spectrums and BBC Micros, went through the Amiga and ST, took a bit of time off, then came back to work on Arcade machines for Midway Games back in the mid to late 90's. -He recently worked for Raven Software, home of Soldier of Fortune, Heretic, Hexen, Star Trek : Voyager : Elite force and Jedi Knight II : Outcast, and can now be found at Maxis in Northern California working on titles from Will Wright's stable. In his spare time he codes for the GameBoy Color and Advance, because "it's as far from C++ coding as you can get, besides, as John Carmack said, low level programming is good for a programmers soul". Start from the Start So let's get started by first talking about the key differences between a game engine, and the game itself. Many people confuse the engine with the entire game. That would be like confusing an automobile engine with an entire car. You can take the engine out of the car, and build another shell around it, and use it again. Games are like that too. The engine can be defined

Accedi al tuo account gratuito per leggere, scaricare EPUB o ascoltare.