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, Zelda: Ocarina of Time, OoT, Zelda OoT, TLoZ: OoT
| Build | Status | GPU / CPU | FPS | Details |
|---|---|---|---|---|
| build-95 (`nx2-build-95`) | runs with issues | RTX 4060 Laptop, 8 GB, 45 W max power limit / Intel Core i7-12650H (6P+4E, 16 threads) | 9.4–51.4 FPS | Open report |
| build 95 | runs with issues | Radeon 890M / Ryzen AI Z2 Extreme | 23–25 FPS | Open report |
| build 117 (PGO) | runs with issues | Radeon 890M / Ryzen AI Z2 Extreme | 42–44 FPS | Open report |
| nx2-build-95 | runs with issues | NVIDIA GeForce RTX 2070 / Intel Core i7-12700KF | Not provided | Open report |
| Not provided | not booting | NVIDIA GeForce RTX 3050 / Not provided | Not provided | Open report |
| build 88 and 93 | runs with issues | GTX 1060 6gb / Ryzen 5 5600 | Not provided | Open report |
| Not provided | unknown | RTX 5060 / Not provided | Not provided | Open report |
| Not provided | playable | RTX 4090 / Ryzen 9 7950x3D | Not provided | Open report |
| Not provided | runs with issues | Integrated graphics AMD (Radeon 860M, Ryzen AI 7 350, RADV / Mesa) / Ryzen AI 7 350 | 22–23 FPS | Open report |
Problems or notes: User reports multi-second stalls while draws are held for unbuilt pipelines with async shaders enabled; in about 8 minutes, mean performance was 25.8 fps and six present windows had a maximum frame time over 1 s (worst 4.9 s). A fresh config used slow defaults and ran at 10–15 fps with stalls up to 8.9 s and blurry/pixelated Handheld resolution. Settings for the measured build-95 session were GPU accuracy Low, async shaders and async presentation enabled, Docked, 8 GB memory layout, and NVDEC GPU. The report also describes Frizti v3 behavior separately: it skipped draws with no pipeline, averaging 26.0 fps in 30-fps mode (range 16.4–30), with revisits at 30.0 fps and no frames over 100 ms.
Problems or notes: The intro, Deku Tree cutscene, and initial gameplay rendered correctly, but the game froze at 0 FPS when Navi passed the Kokiri guard on the path to the Deku Tree. The report mentions texture format asserts and Unmapped Device ReadBlock errors.
Problems or notes: The intro and cutscenes ran at 42–44 FPS and the game reached Kokiri Forest, but Unmapped Device ReadBlock errors and multi-second stalls were followed by a hard freeze before Navi reached the guard. The same errors occurred with memory layout set to both 12 GB and 4 GB.
Problems or notes: User reports that after the Kaepora Gaebora cutscene near Hyrule Castle, the area appears empty and foggy, Link falls through the world, and repeated void-outs prevent progression. Reported on Windows 11 25H2 in Handheld mode with Vulkan. The user says the issue reproduces 100% with the same save; listed configuration changes and disabling a built-in patch did not fix it.
Problems or notes: Crashes during boot about 9–13 seconds after launch, after presenting its first frame, at an unimplemented nx2:vi2 function 201. The same crash is reported on builds 93 and 95.
Problems or notes: A commenter reports missing textures in the Deku Tree after loading a save, across two game versions and builds 88 and 93. They also report that it worked the first time.
Problems or notes: The user says the game cannot run at 60 fps in the base village; no actual FPS or gameplay-start status is stated.
Problems or notes: A commenter reports freezes of about 3 seconds with each step due to shader compilation. Another commenter says the game is completely playable for them and describes shader-compilation stuttering; no performance or sustained-play details are provided.
Problems or notes: During gameplay, the texture collector remains in aggressive mode, causing heavy image creation/deletion churn and frequent full GPU waits. Reporter measured 22.3 fps in two default runs and 22.5 fps in two override runs; these are standing FPS measurements, not a general performance result.
Current: build-117 (2 records); previous: build-116 (0 records).
Also listed as: OoT
| Build | Status | GPU / CPU | FPS | Details |
|---|---|---|---|---|
| build-93 | runs with issues | AMD Radeon RX 6900 XT / AMD Ryzen 9 5900X | 24–30 FPS | Open report |
Problems or notes: Severe lighting flickering and overexposure or corrupted lighting effects; significant slowdowns in some sequences; audio desynchronization during cinematics; initial shader compilation takes considerable time. The user reports approximately 24 FPS in Kokiri Forest and approximately 30 FPS in menus and some cinematics.
Current: build-93 (1 record); previous: build-88 (0 records).
Showing 71–80 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é.