   Ok I want to make a game will these books get me going?
  I am currently learning c++, but once I am finished I plan on getting into game developement. So what I want to ask is will these books get me started? I will list them in the order I will read them.1.begining opengl 2.More opengl  (thats the name of the book)3.Real-Time Collision Detection (The Morgan Kaufmann Series in Interactive 3-D Technology) (Hardcover)4.Game Physics Engine Development (The Morgan Kaufmann Series in Interactive 3D Technology) (Hardcover)5.3D Game Engine Architecture: Engineering Real-Time Applications with Wild Magic (The Morgan Kaufmann Series in Interactive 3D Technology) (Hardcover)   
  Reading about a topic, and doing as part of a larger project, are two entirely different animals.You read the material. Unlikely you will absorb all of it properly. Regardless if you do, that does not mean you can apply any of it. Even if you can, just learning that material does not teach you have to make games.Because the most important ingredient is experience. Books cannot teach you what experience does. You want to get into game development? Start by writing small trivial programs that exercise your language skills. Then work your way up slowly step by step. Each step will give you valuable experience that will come into play when you make bigger games. Eventually, you'll be able to start working on a tetris or pong clone. Make that clone super polished. Doing so will teach you a number of things as well. And so on.   ;  Ok I was too lazy to mention that I do realize that I have to start out slow and work my way up (I didn't want to type alot).My plan is after I am done with learning c++ to learn 2d and first make 2d games like pong, tetris ect. then after I have made some 2d games I will read the opengl books and get into 3d. once I am done reading those I will read the collision detection and physics books and make a few simple 3d games. Finally after that I will read the 3d game engine book and start coding my 3d game engine.So is that a good plan?   ;  Not so much. Learn C++. Once you get well along in that (and get some test/toy/learning applications under your belt) you'll know tons more, including what you'll need to learn next to get closer to your goal.   ;Quote:Original post by TelastynNot so much. Learn C++. Once you get well along in that (and get some test/toy/learning applications under your belt) you'll know tons more, including what you'll need to learn next to get closer to your goal.Quote:I am currently learning c++, but once I am finished I plan on getting into game developement.sounds like that's already part of the plan.  i think the general timeline of learn to program, then learn 2D, then learn 3D is good.  However don't just rely on books.  You won't really actually learn anything until you try everything yourself.One other thing: physics and collision detection aren't exclusive to 3D games.   ;  I know that I have to start slow and work my way up. I am not just expecting the books to teach me everything, but I still need them to learn how opengl works or how to add collision detection ect. I have read the article "how to make games: a path to game development" here on game dev and I will take its advice and start simple with games like pong and work my way up to a polished Tetris. I know that I need experience and that I cant just jump in and expect to be able do it all, but what im asking of you guys is are these books what I need to get me in the door of game developement? After reading these books will I have the basic knowledege of how to make a functional game?   ;Quote:Original post by gregrampageQuote:Original post by TelastynNot so much. Learn C++. Once you get well along in that (and get some test/toy/learning applications under your belt) you'll know tons more, including what you'll need to learn next to get closer to your goal.Quote:I am currently learning c++, but once I am finished I plan on getting into game developement.sounds like that's already part of the plan.  You're missing the point. It's... counterproductive (to be kind) to start planning beyond 'learn to program', because that process will drastically effect your knowledge, goals, and timeframe.And it's certainly counterproductive to start planning 'what to do next' before finishing what's in front of you.AND it's naive to think that 'learning c++' is equivalent to 'learn to program' or will be done in the relatively near future. You don't need to learn opengl or collision detection now. And it will be a waste of time to even try until you do know how to program moderately well, how to design a non-trivial application moderately well, all in addition to having a firm grasp on syntax. Take one step, and only then the second. Learn C++. Learn the Standard Library. Learn program design. Then look towards these details. No need to commit to (or even plan around) books now when you're not going to be able to put their knowledge into practice for a long, long time.   