I am currently reading “Unity iOS Essentials”, which I won from ManiacDev’s book giveaway contest.
And so far, I find that this book seems to be all over the place and it inspires to be a Game Design book.
Why made me think so? Well, Chapter 1 is about Planning Ahead for an Unity iOS Game, it starts out pretty clear, it aims to give the readers a little heads up before they start their game, it mentions considerations such as terrain, lighting, audio, etc. And then it got to the Let’s Get Started part, which is pretty much the author make all sorts of game design suggestions, and sometimes he would suggest something and not really explain why, such as he said that Fog is not such a great idea, and he suggests that we use particles instead, but why? Why isn’t fog a good idea? He even mentioned that it adds ambiance, so why isn’t it a good idea? Also there is a whole chunk that he talks about teleportation (wut? o.O), which provides means for players to travel across our large levels. He could have ended that bit there, but he goes on to suggest different ways of doing teleportation, warp gates, trains, what nots. And then after being distracted by all those really not important stuff, he starts talking about culling. Now, culling is important (even the author says so). But the reader could have skipped that part (okay, at least I almost skipped that part because I was skipping the trying to skip the teleportation part).
Chapter 2 is called iOS Performance Guide, but like Chapter 1, instead of getting right down to it (the performance guide), he starts the chapter with different kinds of games that the reader can make. And briefly mention skybox and how we’re supposed to use a cube with reversed normals instead of the one that Unity came with (again, no explanation whatsoever on why we shouldn’t use the Unity one). And then some bits about how we should do our terrain (not the technical part, the design part of making a terrain). Some more bits about different game genres.And then suddenly, Unified Graphic Architecture and the other stuff that actually seems like the iOS Performance Guide.
Chapter 3 is called Advanced Game Concepts, but really the things covered in the chapter is not very advanced, it’s stuff about menus, interface, screen sizes, accelerometer, shaders and organizing your assets.
Chapter 4 is called Flyby Background. Can’t say anything about it, because I skipped it.
I’m after Chapter 5 because it’s about Scalable GUIs, which I happen to be working on right now. So far, it’s understandable, pretty easy to follow. But the way the code bits are edited makes it somewhat unreadable. Oh and don’t expect the code to work as is.
That’s where I am right now, there are still four more chapters that I haven’t read yet.
So far, my comment is, it’s all over the place.