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 |
|---|---|---|---|---|
| official build88 (55532f2), standard MSVC package | playable | RTX 5090 / Ryzen 7 9800X3D | 47.64–59.9 FPS | Open report |
| 95 | playable | NVIDIA RTX 3070 8 GB / Ryzen 7 5700X (8C/16T) | 32.82–40.75 FPS | Open report |
| Not provided | runs with issues | NVIDIA RTX 3060 12 GB / i5-13600KF | Not provided | Open report |
| Not provided | runs with issues | RTX 4080 SUPER / Not provided | 20 FPS | Open report |
| 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 |
Problems or notes: A user comment reports local native-present averages of 59.90 FPS at the Mido viewpoint at 1X, 49.53 FPS in a central village tree view at 1X, and 47.64 FPS in that view at 2X. New-area shader hitches occurred. The village/pond check retained three hearts, but the Training Grounds/maze transition and later game were not verified.
Problems or notes: User reports 32.82 / 34.09 FPS with pinning disabled and 40.75 / 39.84 FPS with pinning enabled; no crash in 2,383 recorded intervals. The user reports that sustained 60 FPS was not achieved. Testing used Vulkan, Fast GPU accuracy, Docked, 1x resolution, and 100% speed.
Problems or notes: Freezes in the Hyrule Castle Town guard house when walking toward the guard or looking toward the wall with windows. The report reproduces on multiple builds and GPUs. A commenter reports that a texture pool patch in Frizti v3 stopped the freeze, but the room still had low performance after further texture-cache changes.
Problems or notes: A commenter reports the guard-house freeze on Frizti v3. A texture pool patch reportedly stopped the freeze, but the room's performance remained low, with a floor of about 20 fps after additional texture-cache changes.
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.
Current: build-93 (1 record); previous: build-88 (2 records).
Showing 121–130 of 194 reports
Known issues from Lichii sources
The Fairy Fountain in the Lost Woods does not render. A comment attributes this to a damaged game-data file, not an emulator rendering bug.
Recorded fix: A comment says PR #267 adds a workaround that serves a closest sound sibling when a NUP .zs member has no zstd header; the comment asks the reporter to test whether it works.
A user reports a black screen with title music and unresponsive controls until shaders loaded; after entering gameplay, they reported severe glitches and lag, freezes lasting about 20 seconds during shader building, and a steady 18 FPS.
On an RX 6900 XT with AMD proprietary driver 2.0.353, the driver crashes while compiling shaders during gameplay; rejecting one shader hash does not prevent a subsequent crash at the same driver fault offset. The reject check may not help when the shader is already in the disk cache.
A user reports the frame rate drops to 2.5 FPS when shader loading begins, after the initial cutscene runs at 50–60 FPS.
The game cover/icon is missing among the collection covers when the emulator is opened with the game in the ROM path.
On build 95, Linux and SteamOS users report black-screen hangs with audio still playing; comments associate the issue with repeated `Native MME (split front) failed` errors.
A commenter reports reaching the main menu by starting with GPU accuracy set to Accurate, but reports audio issues and possible recurrence after changing settings.
On Windows 11 with an AMD RX 9000 series GPU and proprietary driver 2.0.416, gameplay is around 20 FPS with large variance, light/haze artifacts, and desynchronized, stuttering audio.
On Linux with an AMD Radeon RX 6700 XT, gameplay is around 20 FPS with audio crackling below full speed. On Windows with the same PC, only subtitles rendered.
With Mesa 25.0.7 and kernel 6.12.115, gameplay was followed after about nine minutes by a Vulkan device loss and an unrecovered display; this was not seen again after updating Mesa and the kernel.
Recorded fix: Update to Mesa 26.1.6 and kernel 7.2.11; the reporter did not see the device loss again afterward.
Showing 171–180 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.
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é.