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 |
|---|---|---|---|---|
| Not provided | runs with issues | AMD Radeon RX 7800 XT / Not provided | Not provided | Open report |
| build 95 | runs with issues | AMD Radeon RX 9070 XT / Not provided | Not provided | Open report |
| nx2 a7a28175 + #292, local MSVC build | runs with issues | AMD RX 7000 series / Not provided | Not provided | Open report |
| Not provided | playable | RX 7800 XT / Not provided | Not provided | Open report |
| nx2 @ 09b78bd2df | runs with issues | NVIDIA GeForce GTX 1070 (Pascal) / Not provided | Not provided | Open report |
| nx2-build-93 | runs with issues | NVIDIA GeForce RTX 5090 / AMD Ryzen 7 7800X3D | Not provided | Open report |
| Not provided | runs with issues | RTX 5070 / Intel Core i5-14400F | Not provided | Open report |
| Lichii nx2 build 93 (09b78bd) | runs with issues | NVIDIA RTX 50 series / Not provided | Not provided | Open report |
| Not provided | runs with issues | Radeon 860M / Ryzen AI 7 350 | 22 FPS | Open report |
| bf4c42e223 | runs with issues | RX 9070 XT / Ryzen 9 9950X | 26–57 FPS | Open report |
Problems or notes: A user reported a magenta zigzag line along the Hyrule Field mountain ridge, then reported that a proposed shader-output write-mask fix removed it. This was a user report, not a maintainer-confirmed test.
Problems or notes: A user reported coloured blocks along the Hyrule Field horizon on an earlier local build, with a separate distant-horizon glow. They reported the coloured blocks gone after applying #353 in a later build; the glow remained.
Problems or notes: After outdoor play, the sky turns flat yellow-white and the river shimmers green until reboot. The report attributes the full-screen spread to NaNs handled differently by AMD and NVIDIA.
Problems or notes: Not provided
Problems or notes: User reports missing scene elements, including a door and most vegetation, during gameplay. The report attributes dropped mesh-shader draws to the GPU lacking VK_EXT_mesh_shader, but says the missing elements were not confirmed to be those draws.
Problems or notes: Boots and plays the intro cinematic, then crashes during shader and pipeline compilation with Vulkan device loss. The report says the same behavior also occurred on nx2-build-95. Another user reports that updating to NVIDIA Game Ready 621.14 and rebooting resolved the issue on their system, reaching gameplay with working controller input.
Problems or notes: A user reports gameplay consistently failed after the opening cinematic or when loading a save, with 16 Unmapped Device ReadBlock errors followed by device loss and Windows nvlddmkm Event ID 153. Updating to NVIDIA Game Ready 621.14 and rebooting resolved the issue on this system; gameplay and controller input worked.
Problems or notes: The user reports that the emulator crashes to desktop within a few seconds of entering the Guardhouse in Hyrule Castle Town. Reported environment: Windows 11, Vulkan, Docked, Fast GPU mode, FSR 1, FXAA.
Problems or notes: About 22 FPS in Kokiri Forest. Reported stalls while the front GPU thread waits for the back thread.
Problems or notes: 48–57 FPS in light areas and about 26–33 FPS in busy areas, with thread hand-offs contributing to frame time.
Current: build-117 (2 records); previous: build-116 (0 records).
Showing 21–30 of 151 reports
Known issues from Lichii sources
When fastmem could not be created, guest code ran about 1.4x slower; Kokiri Forest ran at 22.2–26.6 FPS rather than 28.5–33.8 FPS. The report attributes the slow boots to failure to allocate 14336 MiB of backing memory.
Recorded fix: Change #645 retries the section after a private commit that grows the page file; in eight back-to-back boots, all three initial failures recovered on the second attempt and none ran slowly.
Graphics fail to load in the Water Temple; a commenter describes the area as unplayable.
Recorded fix: A commenter reports resolving the issue by using a NUP containing the missing texture files, described as 23.8 GB rather than 23.3 GB.
Many Water Temple rooms are invisible, with transparent walls. A comment attributes this to a damaged texture file in the game dump; another user reports the issue was resolved by making a fresh dump with a NUP with a higher file size.
On AMD Windows proprietary drivers, older builds can lose the GPU device when gameplay or a save starts; build-83 and build-88 reports include this problem.
Recorded fix: A Windows RX 9060 XT report found the issue absent in build-93. A Windows RX 7900 XTX report also found it absent in the CI build at 18cfe85.
On AMD RADV Mesa 26.2.4, task/mesh shader use can hang the GPU and cause device loss during 3D gameplay.
Recorded fix: The reporter found that updating to Mesa RADV 26.2.6 avoided the hang on the same GPU with the same build. If using a distrobox in gamescope gaming mode, the reporter says to install the gamescope package in the container so its Vulkan WSI layer is present.
On build-95, the user reports draws held while unbuilt pipelines are being built, causing multi-second stalls, even with async shaders enabled.
The user reports that a fresh build-95 config starts with slow defaults, including High GPU accuracy, asynchronous shaders off, async presentation off, Handheld mode, 4 GB memory layout, and CPU NVDEC; the game ran at 10–15 fps with stalls up to 8.9 s and blurry/pixelated Handheld resolution.
Recorded fix: The user reports that writing the six listed settings before launch helped: gpu_accuracy=0, use_asynchronous_shaders=true, async_presentation=true, nvdec_emulation=2, memory_layout_mode=2, and use_docked_mode=1; set each key's \default= line to false as well.
User reports a black-screen stall after the first AV1 frame with async GPU emulation enabled on AMD Radeon RX 6800 XT; with async GPU emulation disabled, the game later froze during gameplay.
Users report failure to start, black screens with 0 FPS, or emulator crashes in builds 88–95, including a build-95 Linux report with an unhandled SIGSEGV and null-pointer dereference. The comments caution that the reports may have different causes.
The user reports performance remaining at 20 FPS with music glitches on macOS.
Showing 121–130 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é.