Sams Teach Yourself Game Programming in 24 Hours

Michael Morrison

1 People want too much in this book
When you boil this book down to its basics, it teaches basic windows programming in the context of creating simple 2d sprite based games that simulate 3d enviroments. It does not teach C++, nor should it. It does not teach DirectX, or openGL, nor should it, nor does it ever claim to. It does not teach poor programming practices, like writing an entire application in a single file, that is insanity.

It accomplishes its goals and does it in an interesting and fun manner, what more could you want in a primer?

I wish they would do away with the nonsense "learn X in 24 hours/1week/3 nanoseconds" titles and name them something more appropriate. No one can learn the windows API in 24 hours, no one can learn the C++ language in a week. It is fraudulent to even try and claim to. Most of the books in this series are pretty decent, although not for a serious CS student or professional programmer. They are however, decent books for lay people who can't or don't want to learn the ins and outs of computer systems, but like tinkering around with them and creating programs. They are also a decent,inexpensive way to learn material that would normally be taught in elective courses, although these books don't go far enough to become an expert, it is still a decent beginning.

2 I'm disappointed
I got this book for my birthday hoping it would teach me windows/and game programming. However, None of the .exe's run right on my computer, they would only run on winXP. And only one of the programs would compile.
As far as writing quality, i don't think it's as good as Teach Yourself C in 21 days, Mr. morrison doesn't explain stuff real well. And every time i open it i say "What's going on?" I would reccomend getting (WINDOWS XP!!!) a separate book to teach you Windows programming, and THEN maybe getting this book.

3 What?????
this book is a waste of money it expects you too know c++ already what is up with that!it says teach yourself and it says its for beginners this bokk is crap dont buy it it sucks!

4 Code to perform the most common game operations
Many years ago, after I purchased my TRS-80, I did what so many budding programmers did, I purchased some games and then tried my hand at writing my own. In the subsequent years, the conversations that I have had with many other programmers has revolved around their first attempts to write games. In fact, a solid argument can be made that for many people of that era, the first "large" programs that they wrote were games. Any attempt to write a game requires the use of most of what we do in programming. Topics such as file handling, sophisticated graphics, advanced data handling and complex decision making are all necessary to a good game. In this book Morrison covers all of those areas, as he steps you through the construction of several games.
The coverage of what is needed for game development is complete, and all of the code is available on CD, which is fortunate, because there is a lot of it. The language is C++, specifically Microsoft Visual C++ and
Borland C++ builder version 6. Code for the games in both versions is included on the CD. Borland C++ builder version 5.5 complete and a trial copy of version 6 are also on the CD for those who lack access to a suitable compiler. While I consider the language choice to be fine, it will pose a problem for those with limited exposure to their structures.
By necessity, Morrison is forced to spend the bulk of his allotted ink in explaining the programming of the games. Therefore, anyone unfamiliar with object-oriented programming or how these two versions of C++ are structured will find it difficult to follow the code. This is not to say that it cannot be understood, just that limited exposure to these versions of C++ will probably require that you consult another resource.
If you have a background in these versions of C++, then let the games begin. Morrison gives you a solid background in what is an excellent way to learn the fundamentals of programming, how to develop and organize a complex program and how to have fun while doing it.

5 Interestingly Useless and yet Good
Let me first start by stating that I am only interested in games design as it relates to DirectX. I believe that as I embark on making games, DirectX will be the only tool that can help me create commercial quality games.

I had been hard pressed for a couple of weeks to find ANY information in or out of books on 2D game programming with directX. I was excited by this book, though mildly worried that it didn't say anywhere that it incorporated DirectX. I bought it anyway, and after an hour of looking through it discovered that the author avoided DirectX because of the "steep" learning curve.

I currently hate this book. Its a waste because, while two years ago before I even knew what a graphics library was, this kind of book would have interested me. I've already had experience in game design with pre-built engines and so I wanted to create my own engine and use it to finish a game. This book won't help me do that. At least not a high quality game. Its an interesting read for anyone completely new to games programming, but not for anyone aspiring to create even a high quality 2d game.

This book still gets three stars because it was really my fault for not knowing that it didn't use DirectX. Its well written, and covers its subject matter pretty well. I think that the author fails to realize that probably most programmers will understand the value of DirectX and will probably pass this book up for a similar one on DirectX.

I can say at this point that 2D game programming with DirectX is such a sought after subject for a book or online tutorial for me that I'd pay a hundred dollars for said book. Actually before writing this review I did see another Sam's book with the same name + "with DirectX" so I guess I'll be checking that out.

I do have this to say in closing. This will be the first time that Sam's has disappointed me. And only because I didn't spend enough time to discover the book's entire content. Also, I am 17 and I still feel that this book is too useless to be the kind of help I'd hoped it would be. I needs my DirectX and so I probably won't even start reading this book. However, I have nothing but praise for books like Sam's Teach Yourself C++ in 10 Minutes. If you want to learn C++ then check that delicious bit of literary goodness. That's all.

6 Great introductory books
I have a passion about games. That's why I studied computer science, and I finally decided to dedicate all my free time to start learning how to program games. So I bought Teach yourself game programming in 24 hours by Michael Morrison. Let me tell you, I was surprisingly pleased, and didn't want the book to end.

To start with, this book is not for complete newbies into the C++ language but it shouldn't be. I hate a game book that spends half of its pages teaching you how to program C++. If I wanted that, I'd go back to school and take another C++ course. It also doesn't throw all the theory and math on you like some gaming books out there that are better left for writing a PHD thesis. No, this one is easy enough to follow but also assumes you already have working knowledge of C++. It digs into building a game engine from the ground up, and uses all that knowledge to build gradually more fun and interesting 2D games. It really opened my eyes to many little new tricks I can use to build my own games like the sprite manager and animation. If you guys can't compile the games, I think you still need to have better knowledge of C++ before you tackle this one. I had no problems compiling all the programs using Microsoft Visual C++ 6.0, and although there was a problem or two (due to the fact that the book was written in 2002 and some windows functions used in the book have changed since MSVC++ 6.0), I still found a way to fix them and get them to work. Now why didn't I give it the 5 shining stars then?

Well, first of all it is a 2D book, and it does not use DirectX. So we can use it to build primitive games, but come on, how many companies out there don't use DirectX. Like for example, there is no maximize button in all the windows the book creates, because then the different resolutions can mess up the game. That's where directx comes to your help. Also the sound libraries used are very primitive. PlaySound is not useful in mixing 2 sounds at the same time, and there were some games in the book that sounded weird because of that.

The other thing I didn't like about the book was how the text had lots of bugs in it. Like the text does not actually map one to one to the code on the CDs. But if you are not picky and a little alert, it's not a big deal. Anyway, a couple of emails to the publisher and a 2nd edition will fix that.

My final pet peave was that in so many cases, I was begging that the author would go in detail about the subject, but he would say, "this is too complex, but what I'm providing you is very good". I want some of that complex stuff too. Like I wanna know how a scrolling background works (Many adventure games use it like "Broken Sword"). My knowledge is not complete without it.

But overall, I think the book taught me many new things I didn't know, and although I won't be able to go write a commercial game out there by just reading this book, I can really put that knowledge with the knowledge from more advanced books to use.

I hope Michael Morrison will consider writing a DirectX book version of the Game Programming book, with 3D graphics, and the more "complex" stuff which were missed in this one. Even if the book costs double this one, I'll be the first to buy it.

7 good book, however...
This is a good book for a beginner for the subject. I wish the book had a section to explain how to compile example programs contained in CD in Chapter 2 so that a beginner feels confident, and can read further chapters. Also, the example programs should be bug-free with current versions of Windows.

8 About the code in this book.
The code in this book is NOT ment to be copied and compiled from the first few chapters except for the skeleton program. In the begginging it just shows you some examples of code and what they do, as an introduction, which by the way is excellent. You cant start compiling till you setup all your classes and objects, which you dont do till later in this book. This is an excellent start for ANYONE who wants to get into game programming. It starts with an explination of code(NOT MENT TO BE COMPILED)and goes to the nit and grit of starting a skelton program to forming an engine and finally game. Also for those of you who quit after the first two chapters, because the code didnt work, which it isnt supposed to. Take a deeper dive into the book. I gurantee it'll blow you away.

9 The code _does_ compile!
This book teaches you how to program 2D games and a game engine. It doesn't teach you DirectX or OpenGL, just programming with the Windows API. I've got a Dutch translation, I don't know if the code is cleared from bugs in my edition, but chapter 3 compiles, even in Dev-C++.
I want to say to the poster about the C++ language: you can't give a book a low rating because the author uses a language you don't understand. Learn C++ and read the book again then, maybe you will understand it better.

10 False and faulty information
This book clearly states in several places that the accompanied listings (both in the book and on the cd) will compile with Dev-C++, Microsoft Visual C++, Borland 6.0, and the accompaning software. However all 4 of these programs DO NOT work and produce the same error messages when compiling. While it is good for the basics of what games are, and how they work, the code is faulty and makes it impossible to compile your own programs. DO NOT PURCHASE IF YOU WANT EXACT INFORMATION.

11 Great Book
I love this book it is great I could not understand any of the other books I bought on game programming this one I can finally understand. BUT it is a book about Windows GDI. NOT DIRECT X.

12 Great Book
I love this book it is great I could not understand any of the other books I bought on game programming this one I can finally understand. BUT it is a book about Windows GDI. NOT DIRECT X.

13 Running into trouble...
Chapter 3 will not compile in Borland 5.5 or DEVC++ on XP Pro... this could be because many of the code citations do not indicate in which file to place them. Is it possible that the author assumes I know more than I do? It's supposed to be a "teach yourself", not a "honing your already excellent skills" book.

Currently tripping on "Declaration syntax error" in a resource file. Argh.

14 The C++ is unnecessary, Lamothe is clearer
Good introduction to Game programming and Windows GDI graphics functions, the only problem is I got lost in Chapter 3 "Creating an Engine for Games." My problem is all the unnecessary C++ code. I'm new to game programming and Lamothe's Game Programming Gurus book Volume 1 is much more understandable, much more comprehensive, AND covers DirectX as well, and sticks with C and only goes into C++ when necessary (such as the calls to DirectX).

So if you prefer keeping track of pointers, extra classes, and the (to me) confusing C++ syntax (part of the "Game Engine" in this book), then get this book. If you prefer a book that covers the same content as this book, keeps the code in C, and also covers DirectX and is more comprehensive, get Lamothe's Game Programming Gurus book Volume 1 (Lamothe Volume 2 covers Direct3D and 3D math/physics as well).

In short, there is no need for a "Game Engine" as this book describes. It might make things "easier" in the long run (as I said I'm new to game programming), but the code (to me) is less readable. All you need for every game is to copy and paste Lamothe's basic game code, which is (for example)

LRESULT CALLBACK WinProc... etc // your Windows Procedure

int WINAPI WinMain... etc // your WinMain
{

GameInit(); // initialization function for your game

// enter main event loop using PeekMessage()

while(TRUE)
{

// is there a message in queue, if so get it
if (PeekMessage ...) etc...
{
} // end if

GameMain(); // your main game loop

} // end while

GameQuit(); // final cleanup and quit goes here

return(msg.wParam); return to Windows

} // end WinMain

// GAME CODE STARTS HERE //////////////////////////////////

That is basically all that is required. No need for a separate and complex "game engine." The code in Lamothe is much more readable. For example, see the "Outpost" game and source code at the end of Lamothe's book Volume 1. A much better game than anything in Morrison's book, its kept in one source file (except for the DirectX stuff), and the code is more understandable.

Phil Porvaznik

15 Sams Teach Yourself Game Programming In 24 Hours
Buy It! Why? This book teaches the fundamentals of game
programmiing - //minus the confusing direct x layer
Learning C++,Win32,SDK,API is quite a challenge for the
beginner and adding COM (+) Direct X is quite daunting
for absolutebeginners.
Michael outlines how to write simple games with source
code and all of the executables work,but you will have
to tweak them,if you want to add minutes to the
gameplay or add levels.
The reason I like this book was because it taught the

fundamentals of game programming. After studying this
text, if you want, you can then move on to algorithms,
data structures,3d-mathmatics and other game wizardry.
I highly recommend Sams Teach Yourself Game Programming
In 24 Hours.

If you're like me you read everything in the bookstore,
in the computer gaming section and end up purchasing
too many books.
Unfortunately, all books are not created equal. So, to
save you a little time and fustration, read the list
below for what I think are a few fundamental c++ and
game programming text currently on the market. I know
that "Stroudstrap" wrote C,C++ and parts of Unix, but
brilliant programmer does not always translate into
great author;(personal experience).
These are excellent books are for absolute beginners
and soon to be Gurus:

1. C++ How to Program (Fourth Edition)Author: Deitel
It's not a "fun read", but it covers all of the
fundamentals inside and out.
Do yourself a favor - Get it!
It covers everything. After reading this, you will not have a
need for Stroudstrap, (unless you want to "get fancy and show-
off".

2. Programming Windows (Fifth Edition) Author: Charles Petzold

Fundamentals again. Teaches how to write code for a
window,how to write bitmaps to the screen,blitting,
color palattes...
Everyone has it,it's an easy read, get it.
Rector is o.k., but he's talking about programming
for windows apps and using MFC (isn't that a fried
chicken franchise somewhere)? skim and read through
it several times,you'll see what I mean. "Corporate
will never understand the creative"!

3.Tricks of The Game Programming Gurus (Second Edition)
Author: Andre LaMothe

After completing cs101,cs202,cs303 of the above listed texts;
this book should "in a perfect world" culminate your learning
while matriculating through the virtual world of game
programming.

Game Programming Gurus covers all of the information in the
previous titles, but it covers "real world code". If you have
dreams of becoming the next "Great Programmer", you will use
all of the information in this book. Much unlike many of the
corporate college courses you've probably completed.
"Not that (it)'s anything wrong with 4 years".
This book covers algorithms,2d,3d,direct x,gdi,COM,sound,...

After reading,then (studying), these four texts I think that you
will have confidence and ablity to accomplish anything!

Yes indeed,
you'll be able to exclaim,
with a complete and popular domain,
without sounding insane,
"Yes! I Got Game".

16 To people who buy this book.
Please write a review as soon as possible for I want to buy this book too.

Does it make a 2d and a 3d game engine or does it only talks about 2d game engines.