Orbit64

Game compatibility

Every game is played in Orbit64 by an automatic tester that finds a route to gameplay (title screens, menus, prompts) and remembers it. The route is replayed for each build and the result is judged from the pictures and the game's behaviour.

0games

These results are not 100% certain. Every game is played by an automatic tester, so it can be wrong: a game shown as Menu or Intro / title may work fine and the tester just didn't find its way further (it can't pick a mode or a character, needs a specific button sequence, a save, or a longer search), and a status can also be too good when a menu looks like gameplay. Menu and Intro / title do not mean the game is broken. Statuses corrected by hand are marked checked. If you know a game's real state, please tell us.

How the status is decided

A tool plays each game from the start and looks for the inputs that get it furthest. It tries every button from the same save state, keeps what changes the picture, reads the text on the screen (OCR) to answer prompts and choose menu entries, and finally checks whether the stick moves the character or the camera. The inputs that worked are saved as the game's route. Each build replays every route in seconds, compares the high-level emulation with the low-level one (which runs the game's own microcode) and judges the pictures, so a status always comes from a route that was actually played.

"In-game" is not "perfect": glitches, missing effects and slowdowns are not rated here. The search for a route has a limited time, so a game that needs a long intro, a choice in a menu or a specific button sequence can show up as Menu or Intro even though it runs fine. Only Black screen and Crash / error point to a problem in the emulator with any likelihood.