Ok... I got LaMothe''s "tricks for windows gameprogramming gurus". haven''t read it so much... so damn boring in the beginning. Hella much bullshiet about this and that... Anyway... i was wondering if i should buy "Programming Role-Playing Games with DirectX" ? or does LaMothe''s book cover the same later on ?... i mean, it seems that LaMothe''s book covers alot of DirectDraw. Hence, my problem is that i don''t wanna read the first 350 pages before i can get into DirectDraw... The book, "Programming Role-Playing Games with DirectX", seems like something good. I have knowledge in visual basic, c++, java (currently on object oriented programming). Those cpurses are the ones i have been on at school. So... the beginning of LaMothe''s book is no problem for me. But it seems like he is complementing the code as he goes futher. So i cant understand so much when he gets on directX... would be greatfull if someone could say how "Programming Role-Playing Games with DirectX" developes... c ya

His jokes get annoying after a while

There was a good description about color depths and how it is arranged in memory, but his RGB conversion and file-loading function blow goats

And you don''t read programming books front to back, you go to the part thats most interesting!!!

I think someone else should write/edit a book for a change

the trick is if you understand programming already, then you look through books at the store before purchase. also check the back of the book, most computer books give an approiate level expected for use of the book. dont get beginner books. you "sound" like you think the courses you took for programming will get you prepared for everything coming your way. most likly they only galzed the basics. if you find the section your reading something you could explain to someone who does not know the information THEN go farther into the book. otherwise, its boring more because you dont understand it and want to make games. like all art and sciences, there is no shortcut. seeing things explained by different ppl help. uset he book as a resource instead of one large tutorial. to truly see if your ready for the next level past all the boring stuff. code some of the problems at the end of each chapter and answer the questions (never used his books so i dont know if he does this, most programming books give excerisces). NO copying code now, thats cheating yourself. you may be surprised to find out what you dont know.

I haven''t read "tricks for windows gameprogramming gurus" but I do have his book on Special Effect programming (using DirectX) and the Roleplaying book you mentioned. Of all the books in this series, I have seen a ton of overlap. I would have preferred if each book was half the size and more concise. Lugging those beasts around is a real pain and the bloat is unneccessary (IMHO). Both books have been fairly easy reads, though.

The Roleplaying book is more theoretical offering various tips for handling inventory management, monster management, character development, design, etc. It was probably worth reading, but I don''t think the examples are very practical. There is a "fully-functioning" RPG game on the CD (The Tower), but it''s awful. I''ve seen more impressive gameboy apps.

If I had to choose between the two (Special Effects using DirectX or Roleplaying), I would buy the Special Effects book.

Personally I wish O''Reilly would publish a similar series. They have recently released one about Game Physics Development that is excellent.

Personally I''ve given up on buying game programming books; after roughly 6 ringing up at about $30 each I''ve decided to go with current DirectX documentation (free) and tutorials on the web (also free) since most of the new books that I''ve thumbed through seem to be little more than wrappers for the DirectX documentation. Why pay for something that you can get legally for free?

I really like LaMothe''s writing style...

Also I don''t see you problem with the first 350 pages of a book... If you already know it, skip it, if you don''t then you need to know it.