How we test

Every compatibility row on a game page is the output of a run we performed ourselves. This page explains how those runs work so you can judge the results.

Test hardware

We maintain four reference configurations covering the tiers most readers actually own: a desktop PC, a handheld gaming PC, an Android flagship and a budget retro handheld. Each contributor profile lists the exact machines they test on.

Procedure

1. Install the emulator build from the project official release channel and record its version.
2. Clear any existing shader cache so first-run stutter is measured, not hidden.
3. Run a fixed route through the title covering its most demanding scenes.
4. Record sustained frame rate across that route, not a peak figure.
5. Note every visual or audio defect observed, however minor.
6. Stamp the result with the device and the date.

Status ratings

• Perfect — completable with no observed defects at the target frame rate.
• Playable — completable, with minor defects or occasional frame rate dips.
• Ingame — gameplay runs but with significant defects or unstable performance.
• Menus — boots to menus but gameplay does not run usably.
• Boots — launches but does not reach a menu.
• Nothing — does not launch.

Re-testing and corrections

Emulator forks move quickly, so results age. We re-test the titles in our core suite when a significant build lands, and every row shows its own test date rather than inheriting a page-level timestamp. If you believe a result is wrong, tell us with your hardware and build details and we will re-run it.