- Tapa blanda: 594 páginas
- Editor: Jones and Bartlett Publishers, Inc (20 de agosto de 2010)
- Idioma: Inglés
- ISBN-10: 0763784516
- ISBN-13: 978-0763784515
Clasificación en los más vendidos de Amazon:
nº790.831 en Libros en idiomas extranjeros (Ver el Top 100 en Libros en idiomas extranjeros)
- n°2584 en Libros en idiomas extranjeros > Informática, internet y medios digitales > Guías de videojuegos y juegos para PC
- n°7217 en Libros en idiomas extranjeros > Informática, internet y medios digitales > Internet y web
- n°13510 en Libros en idiomas extranjeros > Informática, internet y medios digitales > Programación y desarrollo de software
Game Engine Design And Implementation (Inglés) Tapa blanda – 20 ago 2010
|Nuevo desde||Usado desde|
Los clientes que compraron este producto también compraron
Descripción del producto
Reseña del editor
Part of the new Foundations of Game Development Series! Almost every video game on the market today is powered by a game engine. But, what is a game engine? What does it do? How are they useful to both developers and the game? And how are they made? These, and other important engine related questions, are explored and discussed in this book. In clear and concise language, this book examines through examples and exercises both the design and implementation of a video game engine. Specifically, it focuses on the core components of a game engine, audio and sound systems, file and resource management, graphics and optimization techniques, scripting and physics, and much more. Suitable for students, hobbyists, and independent developers, this no-nonsense book helps fine-tune an understanding of solid engine design and implementation for creating games that sell.
Biografía del autor
Alan Thorn is a London-based game developer, freelance programmer, and author with more than 13 years of industry experience. He founded the game studio Wax Lyrical Games in 2010 and is the creator of the award-winning game Baron Wittard: Nemesis of Ragnarok. He is the author of ten video training courses and thirteen books on game development, including Practical Game Development with Unity and Blender and UDK Game Development. Alan has worked freelance on more than 500 projects, including games, simulators, kiosks, serious games, and augmented reality software for game studios, museums, and theme parks worldwide. He is currently working on an upcoming 2D-adventure game, Mega Bad Code, for desktop computers and mobile devices.
No es necesario ningún dispositivo Kindle. Descárgate una de las apps de Kindle gratuitas para comenzar a leer libros Kindle en tu smartphone, tablet u ordenador.
Obtén la app gratuita:
Detalles del producto
Opiniones de clientes
Opiniones de clientes más útiles en Amazon.com (beta)
The first few chapters are great. They explain a lot about game engines; generally, how they work and why.
The author even shows you how to create your own c++ game engine from scratch. I love this.
He also makes a point that game engine design is a huge topic that cannot be covered in one book, however at times it seems like he is trying to, which hurts the content.
In the chapter about a DirectX 10 Render Manager, he spends over 100 pages talking about it and how to write a basic one. At the end he explains that the manager he just showed you is actually a piece of crap: camera doesn't move at all, no lighting, etc. The very next chapter (3D Scene Manager) he completely throws out directX and uses OGRE 3D.
I have no problem at all seeing a lot of different examples / ways of creating the different parts of the engine. But I'd also look to different books/resources for different examples. I was looking at this for consistency, which falls apart midway through.
He doesn't incorporate Ogre3D into the engine that the whole book is about making. He only goes over the basics. Also the next chapter is physics, again he picks an sdk introduces you to it and does not implement it in the engine. Ok now the final chapter in the book is where he nearly shoots the whole book in the foot. He talks about DXStudio. He goes on about how it can be used to build a scene easily and output to xml so your engine can use it. But DXStudio Does NOT I repeat NOT load ogre3D's ".mesh" files. So it will not work with Ogre3D. And since the directx10 renderer built in the book doesn't load models at all, the chapter basically has the point of, forget trying to build your own engine and just use someone else's engine/tools instead. After reading 600+ pages of a book that claims to teach you Game Engine Design, having it end with the "Just use someone else's engine/tools" lesson is a hard pill to swallow.
What makes it all so strange is that the first 9 chapters are all excellent, and you are constantly building a game engine from scratch. It's a lot of work, but it's all explained well, and the code is great. So why in the world do the final 3 chapters not just give up on that plan, but kick it in the nuts?
The frameworks used in the book include: OGRE, OIS, SDL, BASS, and a few others. There is hardly any grounds-up work.
This book puts together the engine, but doesn't do any implementation of it (by this, I mean a game implementation, it does implement the parts, not the whole), nor does it really show you code to test the engine. Also, due to the structure, the book is a little bit hard to code along with (in conjunction with the lack of test code).
This book is good if you want to learn some abstract interfaces for a game engine, and maybe get a clue of where to go, itll also teach you the basis of the frameworks. And it's price also isn't too bad.
I rated this 5 stars because I feel like I got something out of it, reading the entire way through, more advanced people probably won't find this book rewarding.
In comes chapter 10 where the book moves away from using directx directly and into using Ogre3D, this is a really good thing because Ogre3D is very good SDK and makes using directx/opengl very easy. He explains the basics pretty good but thats all, he NEVER implements Ogre3D into the engine that the previous 9 chapters where all about building. Doesn't make any sense to just abandon the engine all together, And strangely he never even mentions the engine again from the beginning of this chapter on. And since the chapter you build a directx10 renderer doesn't include any way to load models from file, you are left with an engine that CAN'T draw 3d models from a file, and several other important missing features that Ogre3D provides.
So that was a HUGE dissapointment.
In comes chapter 11 where you are introduced to bullet physics SDK again this is not incorported into the engine. It is just a very light intro to it.
So if he had put the ogre3d renderer in the engine this book would have been really good but because at the end you have just a pile of worthless code, its only worth 3/5 stars to me. Those 3 stars are because I did learn a lot from the early chapters.
The text begins with the basics: downloading Visual Studio or Code::Blocks and configuring a development environment. It shows you how to create and call a DLL. Some brief coverage of the STL. All useful stuff. Then it moves on to some basic engine features, like logging errors and handling exceptions. Again a great place to start. It continues with a resource manager based on XML. Then a 2D scene manager and renderer using SDL. Supporting sound and music with the BASS library. Processing input with OIS. Then a renderer with DirectX 10. Great stuff. Then in the next chapter it throws out everything you just learned and jumps to working with OGRE. Don’t get me wrong, OGRE is a great API. But it seems strange for a book titled “Game Engine Design and Implementation” to use an off-the-shelf library and not code the, erm, implementation themselves. The book follows up with coverage of Bullet physics and ends with a brief overview of DX Studio, which is an all-in-one game engine solution.
While each chapter alone is very interesting and informative, I feel like the book as a whole lost it’s focus somewhere and the engine that you think you are creating at the beginning of the book never materializes. I almost feel bad, it’s like the author started with one premise of creating an engine from scratch, and then gives up half-way. I even agree that using pre-built tools are a good idea in many cases, and most people don’t want to re-invent SDL or OGRE or whatever. But there are other books that focus on these engines and frameworks. People picking up a book like “Game Engine Design and Implementation” probably are more interested in rolling their own engine.
That said, I still feel like the book was a worthwhile read and I did learn a little bit about some stuff and found it useful. Going in I had read the reviews on Amazon, and I knew the author was going to jump around with different libraries. Had I not known this I may have been more upset. As is, Alan Thorn is a competent writer and clearly knows a thing or two about game engines. I guess I just wish there was more of a focus on creating something cohesive and original and not just a jumble of introductions into different APIs. However, if you are on a journey (like me) of creating a 3D game engine you will need as much ammo has possible and this book certainly has a place in the arsenal. Just not the first place.
Buscar productos similares por categoría
- Libros en idiomas extranjeros > Informática, internet y medios digitales > Guías de videojuegos y juegos para PC
- Libros en idiomas extranjeros > Informática, internet y medios digitales > Internet y web
- Libros en idiomas extranjeros > Informática, internet y medios digitales > Programación y desarrollo de software