thanks for The Feed Back, Very encouraging.
Ok. I studdied About An Engine, and took a look at multiple games made with engines. I Know i should go slow but i wanted to have a sneak peek at what i will face in the neer future. So far I Know: "From a 3D Engine View"
1) A Renderer To put The Images On the Screen
R(1) Needs 3D Math
R(2) Api's (Application Programming Interface) Some: SGI's OpenGL, Microsoft's Direct3D
Info: graphics drivers and hardware are called by the APIs to performing many of the graphics operations in hardware.
Graphics APIs actually abstract the application from the hardware, and vice versa, providing the application with true device independence. Thus, such APIs are often called Hardware Abstraction Layers (HALs). The goal of this design is pretty straightforward-- application makers can write their program once to an API, and it will (should) run on any hardware whose drivers support that API.
R(3) 3D Acelerator Cards
R(4) Maybe some culling, which tells the renderer, "If the view camera (the viewer's eye) can't see it, don't bother processing it and only worry about what the view camera can see."
Processing: Using Energy To Make The Gfx Look as nice as it was modeled
Or even somewhat more enhanced.
|