6 of 15 people found the following review helpful
For 3D only,
Verified Purchase(What is this?)
This review is from: Game Engine Architecture (Hardcover)
Unlike all other reviewers I haven't been overly impressed with this one. For starters make sure you're a 3d game programmer only, this book does not cater for 2D games at all.
I just couldn't gain any knowledge from it, the information is just too brief. In fact the book is a very very general overview of game engines. Sometimes the author likes to go a bit more into detail, but then he goes overboard. Take the pages on animation for instance, suddenly the author is using the most complicated mathematical terminology I've ever seen. It just doesn't seem aimed at a specific audience.
But other reviewers have given it 5 stars so maybe I'm missing something here, but this book didn't help me with learning how to construct a game engine.
Sort: Oldest first | Newest first
Showing 1-3 of 3 posts in this discussion
Initial post: 16 Oct 2011, 20:07:58 BST
Mark Baxter says:
The book is aimed more at people with a background in programming at an intermediate to advanced level. It says so on the back. It also says within the first few pages that prior knowledge is expected but I wouldn't say that it was required. You do however need to know how to program in C++ and some basic maths for computers. This is an excellent book and I would highly recommend it.
In reply to an earlier post on 4 May 2012, 10:46:46 BST
@Mark Sleith: I'd like to ask a follow-up question: I am form a Java Background and would consider myself "advanced" in regard to programming - I do understand the basics of C++ code if I see it, but have never really delved deeper into it - would this book still be useful? I am planning on writing a rather simply smartphone game but am still trying to find a decent architecture (I came across Component Design/Data-driven design so far) I can build it on.
In reply to an earlier post on 18 Jun 2012, 10:58:04 BST
J. Bond says:
Don't buy this book as a guide on "How to write" game engines, this book, as it explains, is a textbook on the topic of game engine architecture; to assist persons on a systems course pass said course and give a grounding in the topic of Game Engine Architecture. The book won't give you a "how to" or even a "what to" write, it will just give you a great insight into how to communicate between the discrete parts which make up an generic game engine.
Your project however, does not sound generic, and as many sources point out, many programmers get bogged down in the minutia of trying to write a reusable game engine, rather than actually writing the game at hand.
Therefore, I'd happily suggest you write your game, with whatever technology you're happiest with now, and later review that game project and look how you might want to reuse the elements within for a different game.... THEN buy this book, that way you might help your on going progression from specific, dedicated, game to generic game engine... But for the first step, just make the game, don't think about a game engine.
Hope that helps.
‹ Previous 1 Next ›