Archived

This topic is now archived and is closed to further replies.

2D and 3D pipeline?

This topic is 5883 days old which is more than the 365 day threshold we allow for new replies. Please post a new topic.

If you intended to correct an error in the post then please contact us.

Recommended Posts

It''s a term for the "path" graphics take in your system going from numbers stored in memory through the rasterization process and end up as excited phosphors on your screen.

Think of it as a bunch of bits in memory going to work. Along the way they have to grab a taxi to get to a train station. Then the train takes them to a bus stop and the bus takes drops them off at the surface of your monitor. At each stop, a bunch of bits get off and walk away. The taxi and train and bus are different things that are done to them along the way, like transformation and culling. The bits that "got off" along the way experienced clipping.

Share this post


Link to post
Share on other sites
Check any reference book, like one of the OpenGL red/blue books or any number of third party OGL books, or any book on Direct3D--or just plain graphics in general. They''re all based on the same idea.

Share this post


Link to post
Share on other sites
quote:
Do you know where can I find an even more technical explanation?

wait, wait... you mean there''s not REALLY a bus stop in my computer?!?!

--- krez (krezisback@aol.com)

Share this post


Link to post
Share on other sites
there''s also a very good, and (I think) fairly general description of the 3D pipeline in the DirectX SDK; you can probably find it by doing a search on msdn.microsoft.com for "3D pipeline".

Share this post


Link to post
Share on other sites