Where do the reports come from?
The official Lichii compatibility site collects reports from players. The site shows labels including Perfect, Playable, Runs, Loads, Unplayable and Untested, together with information such as build, graphics family and operating system.
Those are community reports, not hardware certification. A positive report and a crash report can both be valid when their builds, drivers, game versions or tested scenes differ. The useful question is “which observation resembles my setup?”
What should you compare first?
| Field | Why it matters |
|---|---|
| Game and game version | A related title or a different game update can behave differently |
| Emulator build | Renderer fixes and regressions can change the result |
| GPU and driver | Similar card names do not imply identical driver behavior |
| Operating system | Windows, Linux and macOS use different graphics paths |
| CPU and settings | A GPU match alone does not isolate a bottleneck |
| Tested scene and duration | A movie, title screen and sustained gameplay are different checks |
Use the setup matching helper to prepare a comparison checklist. It does not run a benchmark or calculate a personalized FPS value.
Does Playable mean the full game was tested?
Do not assume it does. Read the free-text report. Look for the actual scene, gameplay duration, known glitches and whether saving and loading worked. When those details are absent, keep that uncertainty.
Similarly, an Untested catalog entry means the site lacks a published test result for that entry. It does not prove that the game fails, has no interested users, or is impossible to emulate.
The Ocarina of Time guide is a good example of why details matter: community reports include both playable sessions and crashes around the first 3D scene.
How do you investigate conflicting reports?
Open the matching GitHub issues. Check the build and dates. A release note may fix a particular regression without resolving every similar symptom. Do not combine several partial fixes into a new claim that all hardware now works.
If you compare builds yourself, change one variable at a time and keep your own logs. PGO vs standard explains a controlled comparison.
How can you contribute a useful report?
The project README says desktop reporting needs a build containing PR #303 and is unavailable in build 88. In a supported build, play and stop a Switch 2 game, then right-click it and choose Submit compatibility report. Only the latest session in the current process is eligible.
Confirm the matching catalog entry and review the public preview before consenting to submit. The native v1 reporter does not automatically upload logs or files. Include the actual scene and limitations rather than only a positive adjective. If reporting a bug instead, attach relevant logs only after checking for private information; never upload game files, keys or firmware.