Graphics /Discover / The graphics pipeline
The graphics pipeline
scenario
How Does Geometry Reach the Screen?
You already know how vertices describe geometry, how matrices change those vertices, and how rasterisation turns geometric coverage into discrete samples. Now start from the other end of the problem: your program contains only six floating-point numbers for one triangle, but the screen is still blank.
Those CPU-side numbers do not specify by themselves how the graphics system should store them, interpret each pair, transform the resulting vertices, decide which screen samples belong to the triangle, or choose the output colour. A draw command also cannot manufacture all of that missing state automatically.
Your task is to work out the responsibilities that must exist between the source array and the final framebuffer image, and which information must be prepared before drawing can begin.
Starting with the six numbers {100,100, 300,100, 200,300}, what responsibilities must be handled between that CPU-side array and a coloured triangle appearing in the framebuffer?