Compatibilité des jeux
Vous avez un jeu en tête ? Voyez comment il tourne dans Lichii, repérez les problèmes et choisissez une version à essayer.
Trouver un jeu
Les données actuelles comptent 108 entrées par jeu et environnement, et 308 rapports sur Lichii.
Un jeu manque ? Un résultat vide indique qu’aucun rapport sur ce jeu n’est encore répertorié pour Lichii. Cela ne signifie pas que le jeu a échoué à un test.
Consultez la plateforme indiquée pour distinguer les différentes versions d’un jeu.
Signification des statuts : « Unknown » : aucune conclusion. « Not booting » : le jeu ne démarre pas. « Boots » : seul le démarrage a été constaté. « Runs with issues » : des problèmes surviennent en jeu. « Playable » : la personne ayant testé le jeu a pu continuer à jouer.
Compatibility results
Recorded performance
Open a game for its test details. Start with a GPU and build close to your own, then explore the driver, FPS, and gameplay notes.
No games match these filters. Try a different name, GPU, or build, or clear a filter to broaden the search.
Also listed as: Ocarina of Time, OoT
| Build | Status | GPU / CPU | FPS | Details |
|---|---|---|---|---|
| Not provided | runs with issues | RTX 5080 / Ryzen 9 9950X3D | Not provided | Open report |
| Not provided | runs with issues | RX 6700 XT / Not provided | Not provided | Open report |
| Not provided | not booting | RX 5700 / Not provided | Not provided | Open report |
| nx2-build-88 (55532f2) | runs with issues | NVIDIA GeForce RTX 5060 (8 GB VRAM) / AMD Ryzen 5 5600G (6C/12T) | Not provided | Open report |
| nx2-build-93 | runs with issues | RTX 2060 6 GB / Xeon E5-1620 v3 (4C/8T) | Not provided | Open report |
| nx2-build-117 | runs with issues | AMD Radeon RX 580 8 GB (Polaris, GCN 4) / i3-8100 | Not provided | Open report |
| nx2-build-93 | runs with issues | AMD Radeon RX 6750 GRE 10GB (RDNA2) / Ryzen 5 5600 | Not provided | Open report |
| nx2-build-117 | runs with issues | NVIDIA RTX 40 series (RTX 4070 Ti Super) / Ryzen 7 9800X3D | Not provided | Open report |
Problems or notes: A commenter reports the same guard-house freeze, both while talking to the guard and while moving around inside.
Problems or notes: A commenter reports crashes in the guard house, reproduced 5/5 times while looking toward the wall with windows and panning the camera. A reported VRAM allocation burst preceded the crashes; whether memory pressure caused them was unclear.
Problems or notes: A commenter reports black 3D graphics with working UI and attributes this to a possible DemoteCombinationPass issue; this is a user-provided analysis, not a confirmed fix.
Problems or notes: In a 1h 49m gameplay session, the reporter observed severe 1.3–6.59 second freezes, continuous frame-time micro-stutters, repeated GPU-thread shader translation stalls, and 579,265+ synchronous OnCPURead waits. The session had 0 crashes. Vulkan, 1x, GPU Mode Accurate, Async GPU and async shader compilation enabled, and Enable Reactive Flushing enabled.
Problems or notes: A user follow-up reports FPS averages falling from 53 in the first 10-minute bucket to about 23 in the 80–90-minute bucket during a 98-minute session with Reactive Flushing enabled, alongside 365,889 OnCPURead events and stalls over 2 seconds. In additional roughly 100-minute sessions, OnCPURead growth occurred with Reactive Flushing both on and off; with it off, FPS averages were 16–33 after the first 10 minutes and stalls reached 12 seconds, with one around 49 seconds. The reporter notes the comparison is not conclusive.
Problems or notes: A user reports the AMD Vulkan driver faults with exception 0xc0000005 during compute-pipeline compilation. Two shader pipelines repeatedly fail to finish; the same was reproduced on nx2-build-95. OpenGL was also reported to fail because GLSL task and mesh programs are not implemented.
Problems or notes: On Vulkan, the AV1 intro audio plays and decoding starts, but no video image is presented; eight compute shaders fail with VK_ERROR_OUT_OF_HOST_MEMORY and the process eventually aborts with 0xc0000409. The issue says the same crash signature also occurred on nx2-build-88 and nx2-build-83 (MSVC).
Problems or notes: With Switch 2 draws with unbuilt pipelines set to Bounded and an 8 ms wait, the image washed out to white and orange and parts of the scene rendered as large flat polygons while pipelines were building. Switching to Wait produced a normal picture with the usual stutter while pipelines built.
Current: build-93 (1 record); previous: build-88 (2 records).
Also listed as: Ocarina of Time
| Build | Status | GPU / CPU | FPS | Details |
|---|---|---|---|---|
| Not provided | runs with issues | AMD RX 6900 XT (RDNA2) / i7-9700K | 18–30 FPS | Open report |
Problems or notes: The user reports a driver crash after starting a new game and skipping a cutscene. With a local build using EDEN_NX2_NOOPT_SHADERS=all, they report no crash during 40+ minutes of play in Kokiri Forest, Deku Tree, cutscenes, and save load. The same setup was CPU-bound at 18-30 fps in Kokiri Forest.
| Build | Status | GPU / CPU | FPS | Details |
|---|---|---|---|---|
| Lichii Development Build | 1.0.0-sharkiix-3.1.1 | runs with issues | AMD Radeon RX 6700 XT 12 GB (Navi 22) / AMD Ryzen 5 5600G (6C/12T, Zen 3) | 20 FPS | Open report |
Problems or notes: Menus and pause screen run at 60 FPS, but gameplay is around 20 FPS with audio crackling below full speed. Forcing full GPU clock and performance EPP made gameplay smoother but did not raise the frame rate. The report attributes the limitation to synchronization between emulator threads. On Windows with the same PC, only subtitles rendered. The report also describes a device loss after about nine minutes with Mesa 25.0.7 and kernel 6.12.115; it was not seen again after updating to Mesa 26.1.6 and kernel 7.2.11.
Showing 91–100 of 151 reports
Known issues from Lichii sources
On the reported Radeon 890M system, the game freezes during early Kokiri Forest gameplay, accompanied by Unmapped Device ReadBlock errors; a later report on build 117 also describes pipeline-building stalls and a hard freeze.
Stutters or freezes and drops to 15 or fewer FPS while shaders are building.
First-visit shader stutter.
Hard lag or freezes when shaders are being built, mostly on first visits to areas, as reported by the issue author.
In build 117, the reporter experienced pervasive shader stutter and repeated shader rewriting, instability and choppiness, and broken frame generation. A commenter separately reports freezes when entering new areas.
Long freezes while entering new areas, according to a commenter.
In Build 117, pre-rendered cutscenes reportedly run at 28 FPS in slow motion and fall out of sync with audio, while gameplay is unaffected.
A commenter reports slow motion in Build 93.
On Linux using a Steam Deck, the reporter describes a main-menu performance regression in build 117, from 60 FPS with some drops on the prior legacy build to 10 FPS, with audio out of sync. The non-PGO version reportedly had the same problem.
Shader stutter and multi-second freezes while shaders are being built, including during first visits.
Recorded fix: A commenter reports the stutter was resolved for them on a fork built with PR #579 by running the one-time shader warm-up from the game files; it took about 23 minutes on their CPU.
Showing 51–60 of 361 issues
Notes de version récentes
Version build-117 · Ocarina of Time
Version build-116 · Zelda: Ocarina of Time
Version build-116 · Zelda: Ocarina of Time
Version build-116 · Zelda: Ocarina of Time
Version build-116 · Mario Tennis Fever
Choix d’une version
build-117 · Publiée le November 7, 2026
12 fichiers à télécharger pour cette version.
build-93 · Publiée le November 6, 2026
7 fichiers à télécharger pour cette version.
build-88 · Publiée le November 6, 2026
7 fichiers à télécharger pour cette version.
Essayez la dernière version disponible : build-117. Gardez une version fonctionnelle sous la main pendant vos essais.
Questions sur la compatibilité
Appliquez les filtres de jeu, de statut, de GPU et de version, puis copiez l’URL de la page. Un lien vers un jeu précis ouvre sa fiche.
Vérifiez dans d’autres rapports si le jeu atteint les menus ou une partie jouable. Notez votre pilote et le moteur de rendu, puis recherchez le jeu ou l’erreur dans le guide de dépannage.
La version du pilote, les réglages graphiques, la charge du processeur et la partie du jeu testée peuvent influer sur le résultat. Comparez ces détails avant de modifier votre configuration.
Utilisez le suivi officiel des tickets de Lichii. Indiquez le jeu, le tag de la version, le matériel, le pilote, les réglages et les étapes pour reproduire ce que vous avez observé.