game engine graphics

Just start working on something. Along the way, youll necessarilly rewrite the class structure several times to suit your needs better. Whatever design you make at the beginning, there is a border after which the adding of another feature clutters the code and makes it hard to maintain.
Just start with some import of the objects from some modelling program, add some multitexturing, lighting, animation, collision detection,shaders,frustum culling and youll realize there were hundreds of things you had no idea about when you started designing your engine class hierarchy.
Thats life, fortunately thats the fun part, when you`re learning new stuff from C++ (STL,Namespaces,...) and designing your classes around it while rewriting existing portions of code.
Just Do It.

VladR
Avenger 3D game (Last update MAR-26)

I''ve learned to love managers, that is, appending anything to a class by sending in a filled structure of "attributes" and having it take care of everything for me (collision, updating, rendering). It gets pushed into a linked list of similar objects depending on the manager and attributes it can accept (entities in model representation form, textures, world effects, projectiles, 3d sound effects, misc particle effects). It returns a pointer to the object after it has been added, in order to send that same pointer in for manipulation when needed at any time. Make the managers powerful, and it makes your code much easier to maintain. Then you won''t really have to worry about making a class for this, a class for that, rendering this, updating that. Just add attributes to whichever manager and start feeding it the new features, go nuts over it too, you''ll find it to be much easier this way.