The Engine module source code was released by Ken Silverman on J.Unfortunately both part of the game were not open sourced simultaneously: The 3D Realms team on their side would take care of developing the Game module ( Game.OBJ)Īnd would also release the final executable DUKE3D.EXE. He would only deliver a binary static library ( Engine.OBJ) with an Engine.h Silverman would write a new engine for 3D Realms but he would keep the source code.
They found his skills promising and worked out a deal: (18 years old at the time) wrote a 3D engine at home and sent a demo for evaluation to 3D Realms. Is where Ken Silverman enters the picture.Īccording to his well-documented website and When 3D Realmsĭecided to write a game that would challenge Doom, they had to find the technology that would power it. Why such a division? Because back in 1993, when development started, very few people had the skills and dedication
Game Module: Using Build's services in order to generate a gaming experience. Build engine: Providing rendition, network, filesystem and caching services. I would like to thanks Ken Silverman for proof-reading this article: His patience and diligent replies to my emails were instrumental.ĭuke Nukem 3D is not one codebase but two : Read more source code and become better engineers. Legacy and what helps a software live long.Īs usual I cleaned up my notes into an article. This reading session taught me a lot about code Of organization, best practices and comments/documentation. The engine delivered great value and ranked high in terms of speed, stability and memory consumptionīut my enthousiasm met a source code controversial in terms It turned out to be a difficult experience: Having exhausted the insanely good idSoftware pool,ĭuke Nukem 3D and the engine powering it named " Build". Since I left my job at Amazon I have spent a lot of time reading great source code. February 14th, 2013 Duke Nukem 3D Code Review: INTRODUCTION (PART 1 OF 4) >
0 kommentar(er)
