READ THE EVIDENCE
What “compatible” actually tells you
A compatibility claim is useful only when it names the game, the build, the machine and the stage reached. Read the report before treating a label as a result.
Start with per-title reports
The upstream README directs testing reports to its Game bring-up discussions and links a community blocker map. Those are the places to investigate a specific title. We have not independently tested the games in those reports.
Search by the title and, when you have it, the title identifier. Then check the date and the build in the report. A similarly named game or another regional build may not answer your question.
Read the stage, not just the headline
| Observation | What it establishes | What to ask next |
|---|---|---|
| Conversion completed | Output was produced | Did it load on the target host? |
| Window or menu reached | That startup path ran | Which scene was tested? |
| Gameplay shown | An observed segment ran | How long, on which build and hardware? |
| Sustained session reported | A longer test is described | Were saves, audio and later areas checked? |
This is our reading checklist, not a formal upstream rating system. Use it to turn an ambiguous “works” into a test you can understand.
Coverage is a different measurement
Upstream notes that library percentages use the functions currently known to the project as their denominator. That number is not a percentage of playable games.
A coverage milestone is useful development information. A game report asks a separate question: did this title’s actual execution path work in this test? Keep those two pieces of evidence separate.
Make a comparison you can reproduce
- Compare the same title identifier and version when available.
- Check whether the report uses a release, main or a custom patch.
- Look for the hardware, driver and first failing scene.
- Distinguish a screenshot, a short clip and a described session.
- Record unresolved parts instead of promoting the best-looking result to a universal claim.
Common questions
Does a library coverage percentage measure playable games?
No. The upstream README defines it using known library functions, not a game library.
Does this site maintain a tested-games database?
No. It explains how to read the upstream and community evidence.
Sources & context
Documentation reviewed 2026-10-14. Main-branch documents can change.