Greetings, I am working on a 1st person DirectX9 adventure game that will be the biggest project I have done thus far. It will be composed of various elements, such as rendering, level geometry, objects, sounds, input etc. Now what I am wondering about is how to best implement such elements, on the global scale. I mean I could go ahead with an approach I think would work, but I would rather educated myself in some solid methods, dos or do nots etc. of this sort of things. Just to give you an example of a few big questions that are on my mind: * Error Logging: how to best implement that? I am guessing one, perhaps global "error logger" class that every single object in my program includes and refers to whenever errors occur. Or is there a better way? * Rendering engine: on one hand I want to keep it separate from the gameplay and mechanics, on the other, I am having problems figuring out how. Lets take my cLevelGeometry class for example. I could easily create a Draw function that would draw it based on parameters, but then I have each class drawing itself, instead of a unified draw engine. But to create a drawing engine, it would need access to private members of all my displayable classes, which I don't really like either. * Object manipulation and interaction: should they all be self sufficient (Block.Move(), Block.CheckCollisions() etc.) or should I have a controlling class that takes all my elements and manipulates them? In the former case, each object must know everything about the game world, I would need to effectively pass a list of all objects into each of its functions. In the latter, I run into the problem with the render engine, where such manipulator would need to access the private members of each of my objects. And if I use something like "friend class cManipulator" then each of my objects needs to know about the manipulator class, which creates a lot of dependancies and makes the code less reusable / self-contained. * Inheritance: what's the best way to even start thinking about my inheritance tree? Should ALL my objects originate from a common cObject class, or is that too excessive? * Player interaction: how to effectively implement a player class without creating a lot of "hacking" of code to make it work or something that doesn't fit very well with the rest of the code? These are just examples of some of the dillemas I am facing. If anyone could recommend some indepth reading (preferably online, but print in worst case scenario) I would be very appreciative.