I don't even know wtf happened, man... I swore I wouldn't get sucked into any of these vibed-up, fully AI-based Sega Dreamcast ports that have been popping up everywhere, all of a sudden... ...but here I am, 6+ hours deep into mapping the matrix skinning and TnL math from Lamb2k's Resident Evil 4 port from Gamecube-targeted routines to SH4ZAM, my accelerated math library for the Sega Dreamcast's SH4 CPU. The prospect of one of my all-time favorite games coming to my all-time favorite console has given me the courage to wade through this Clanker-generated hellish nightmare of AI slop code in search of GAINZ for our little white box. THANK GOD I added first-class support for 3x4 transform matrices to SH4ZAM's XMTRX API, including loading, saving, and operating on their transposes... because of course, the Dreamcast is chad 4x4 column-major at the HW-level, while the Lamecube loved 3x4 row-major matrices... ...as you can see from this direct hardware capture, the game already looks absolutely stunning at the Dreamcast's beautiful and crisp 480p with 2x horizontal FSAA enabled, but... the real question is now HOW IS IT GOING TO RUN IN THE END? NO CLUE, because I'm still trying to get a grasp on just how well the AI optimized the port, given that portions of the code look like absolute dog-shit, totally ignoring the vector instructions on the SH4 FPU for critical-path math... but at the same time, from what I can gather from the clusterfuck that is the renderer, the actual vertex submission code is quite efficient... So I really can't say precisely just how much room is left for GAINZ here just yet, tbh. The port is DEFINITELY extremely CPU-bound atm, but we'll just have to see where this one takes us!