152 karma · joined February 13, 2021
(edit) Terje Mathisen's "almost all programming can be viewed as an exercise in caching" is often quoted amongst game developers, as it rings true with how we use hardware and pre-calculation of data.
I had also wondered if streaming was driving some of these changes, by reducing noise and providing better compression reducing the image to simple gradients.
Two pixels per cycle for flat shaded or rectangular primitives. Add another cycle for color interpolation, and another for on-cache texture reads (divided by how many texels are packed into 16 bits). The GPU is clocked around 53MHz so the range of 'many' here is roughly 1 to 4, ignorning that a CPU renderer would probably write two pixels at once. The CPU is also hampered by main memory reads taking a minimum of 5 cycles. Pipelining helps a little but extensive scratchpad use, such as putting the stack on it, was essential.
DOOM PSX did use triangles for the walls, just that they were a single pixel wide.
I made an internal "cel-shading" tech demo back in 1998, tracking the polygon edges and then using line primitives to outline the objects but there was no game to apply it to.
There were bump/normal mapping demos around then too, where a palette entry was assigned to a vector (so 256 vectors max), lit, and the texture applied additively (or subtractively).
On a personal project attempting a mesh shader like approach (although you can say it's really a PS2 VU1 workflow) to transform and sort a cluster on scratchpad, then triple buffer the output in memory, ready to be kicked off to the GPU in slice mode. It might end up slower than the old brute-force OTZ approach but it's fun to figure this stuff out.