A Moogle  🏳️‍🌈 💻 🎮 🎶 🇸🇪

this is being made even more confusing by the fact that you target MAME's render engine rather than GL or D3D

MAME doesn't *have* a render engine per se. It's all software rasterization. By the time geometry gets handed over to poly_manager, the verts must be in screen-space for the bitmap to which it will be drawn.

my point stands

Sure, but it ultimately boils down to the resulting X and Y members of vertex_t should theoretically be in the range of 0..639 and 0..479.

from the matrix values you told me, my assumption is that the values would be in NDC coordinates, and the the 772* value in the last corner scales the vector's x/y components to pixel size. only a single one is required to do that.

The baffling thing is that I'm not sure the meaning of the 772 value. I have, however, found a much better scene, as it has a single full-screen quad.

After each coordinate is run through f24_to_f32 in the namcos23 driver (linked previously), the resulting X/Y ranges are -/+1.5625 and -/+0.585938. Problem is, I'm not sure if it intentionally exceeds the screen bounds.