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 |
|---|---|---|---|---|
| Lichii nx2 build 75 (c9ebb5c) | runs with issues | NVIDIA GeForce RTX 4060 Laptop GPU / Intel Core i7-14650HX | Not provided | Open report |
| 286117c7e0-nx2 | not booting | NVIDIA RTX 50 series / Not provided | Not provided | Open report |
| Frizti v2 (765659af4) | playable | RTX 5090 / Ryzen 9800X3D | 53.66 FPS | Open report |
| build 80 (Lichii Development Build | fix/oot-upscaler-gathers-build-80) | runs with issues | Radeon RX 9070 16 GB / Ryzen 5 7500F | Not provided | Open report |
| current nx2 | playable | RTX 4070 SUPER / Not provided | Not provided | Open report |
| nx2-build-83 | runs with issues | AMD RX 9000 series / Not provided | 41 FPS | Open report |
| Not provided | runs with issues | RX 7900 XTX / Not provided | Not provided | Open report |
| build -88 MSVC 19.44.35229.0 | runs with issues | AMD RX 9000 series; RX 9060XT 16GIG / Ryzen 7 5700X | Not provided | Open report |
| nx2-build-88 | not booting | AMD Radeon RX 6600 / AMD Ryzen 5 5600 6-Core Processor | 0 FPS | Open report |
| v93 | runs with issues | RX 9070 XT and RX 5700 / Not provided | 15–30 FPS | Open report |
Problems or notes: Gameplay starts, but the 3D scene and character are black; menus and item preview can render, and HUD elements remain visible. Reported GPU shader errors include rejected native texture gather shaders and draws skipped for no pipeline.
Problems or notes: The user reported an infinite startup launch loop when booting the .NUP version. A comment corrected the GPU to RTX 3080.
Problems or notes: A user comment reports 53.66 presents/s in a stationary village view and a limited continuous gameplay check through the training-area crawl passage to the maze entrance and back to the east pond/Mido approach. Native 60 FPS was not locked; the Deku Tree and later areas were not tested, and the release's overexposure warning was not cleared.
Problems or notes: The title screen rendered normally, but after starting a new game the world rendered almost entirely black, with only the HUD, areas lit by Navi and around Link's feet, and some blown-out white shapes visible. Multi-second stalls of 6.4 s and 5.6 s occurred during pipeline building and ASTC decodes. The report used Vulkan, 1x resolution, ScaleForce, and FIFO vsync on Windows 11 25H2. The closing comment says later builds include many Ocarina of Time fixes but does not confirm this issue was fixed.
Problems or notes: Commenter reports the over-bright, washed-out rendering is gone and says the title was played for about 20 minutes without stretched/exploded environment geometry recurring. The specific build changes responsible are unknown.
Problems or notes: The issue author reports audio running ahead of the video, cutting out and repeating during the opening cutscene, followed by a full computer freeze at the Deku Tree cutscene. Reported settings: Vulkan, GPU Mode Fast, Docked, Bilinear window adapting filter, and no anti-aliasing.
Problems or notes: A commenter reports an AMD driver timeout and GPU reset when control of Link begins, attributing it to an ambient-lighting compute dispatch. They say PR #206 fixes that timeout in their testing, but note it does not fix separate pipeline-build crashes or black-world problems.
Problems or notes: The user reports audio delays after scenes, followed by a black screen and emulator crash. A commenter reports a similar crash on Linux with AMD graphics.
Problems or notes: User reports a permanent black-screen freeze at “Building: 13 shader(s)” during the initial AV1 title screen video decoding sequence with Vulkan, GPU Mode Low/Fast, and Asynchronous Shaders enabled. The emulator shows 0 FPS and requires forced termination. The same user reports that an NVIDIA RTX 2060 boots and renders 3D gameplay with the same portable-folder configuration. Another user reports the issue on an RX 6600M.
Problems or notes: A user reports FPS between 15 and 30 with constant drops and GPU usage frequently reaching 100%.
Current: build-117 (2 records); previous: build-116 (0 records).
Showing 11–20 of 160 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-116 · 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-83 · Publiée le November 6, 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é.