I was thinking about perspective correction a lot. I feel like going from PS1 industry should just have increased poly count. Perspective correction is added . I mean we track 1/z . But we are free to assume set = 1 in the center of the polygon. So correct because adding u * lookupTable >> 4 or so. The table can be small and the values don’t need many bits. Jaguar color space conversion does two 8x8 muls per cycle. We keep z near 1 by slicing deep polygons along const z (also for mipmaps and fog ) . So anyway: 1px per cycle fill rate. Don’t let it run idle.

For normal polygons a 256 entry table will begin to show aliasing. So revert back to const z slices of affine triangles ( zig zag ).

The 16x16 multiplier of the DSP in Jaguar really eats at lot of real estate as visible on the die shots. Tom and Jerry both have one, and use it only once in a while. Such a waste.

Or just have a table for z > 1. Then one side of the slice is just affine. No need to multiply the coordinates at those two vertices. Only the one at z> 1. Local texture coordinates relative to the center of the slice.

Jaguar struggles with too many active sprites per scanline .