I remember playing Wolfenstein and Ken's Labyrinth, and Doom, and wondering just how the heck it all was done. Then I came across a copy of this book in a "computer store" I was working at who couldn't (or wouldn't) pay wages. He told me I could have any book in the store for my work that day, and I grabbed this one on impulse.
I remember missing my stop on the bus ride home, because even though it was about flight sims, the algorithms and methods inside were about 3D programming - the very thing I'd been wondering about!
I never built a flight sim, but I _did_ build a rudimentary 3d game with the knowledge I gleaned from this book. There wasn't any collision on the walls, and the sprite-base object pickups with get corrupted randomly after a while, and I never really got the hang of doing matrix multiplications instead of geometric transforms, but this book cemented my love of programming at a point where I may not have really pursued it much more without an in-depth project to spur me on!
I remember playing Wolfenstein and Ken's Labyrinth, and Doom, and wondering just how the heck it all was done. Then I came across a copy of this book in a "computer store" I was working at who couldn't (or wouldn't) pay wages. He told me I could have any book in the store for my work that day, and I grabbed this one on impulse.
I remember missing my stop on the bus ride home, because even though it was about flight sims, the algorithms and methods inside were about 3D programming - the very thing I'd been wondering about!
I never built a flight sim, but I _did_ build a rudimentary 3d game with the knowledge I gleaned from this book. There wasn't any collision on the walls, and the sprite-base object pickups with get corrupted randomly after a while, and I never really got the hang of doing matrix multiplications instead of geometric transforms, but this book cemented my love of programming at a point where I may not have really pursued it much more without an in-depth project to spur me on!