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: OoT, Ocarina of Time, OOT REMAKE
| Build | Status | GPU / CPU | FPS | Details |
|---|---|---|---|---|
| nx2 fork at 99ac3d5955 with local patches (commit 1e53321757) | runs with issues | RTX 5080 / Ryzen 9 7950X3D | Not provided | Open report |
| 09b78bd2df | runs with issues | GTX 1070 / Not provided | Not provided | Open report |
| Not provided | runs with issues | GTX 1070 / Not provided | Not provided | Open report |
| a7a281757da390ce45070e772784e0333831bb25 | runs with issues | NVIDIA GeForce GTX 1080 / AMD Ryzen 9 3900X | Not provided | Open report |
| build-95 | runs with issues | RTX 4070 Ti SUPER / Not provided | Not provided | Open report |
| 95 | not booting | AMD Radeon RX 7900 XTX (RADV) / Intel Core i7-11700K | 0 FPS | Open report |
| Build 95 | not booting | AMD Radeon RX 5700 XT (RADV NAVI10) / AMD Ryzen 5 3600 6-Core Processor | Not provided | Open report |
| Build 95 | not booting | NVIDIA GeForce RTX 3050 Laptop GPU / i5-12500H | Not provided | Open report |
| nx2 @ 89440b29a9 | runs with issues | Not provided / Not provided | Not provided | Open report |
Problems or notes: A user comment reports a median frame time of 22.4 ms in Kokiri Forest and CPU time concentrated on the GPUBack thread, with the GPU front thread mostly waiting. This is a user measurement, not an official compatibility result.
Problems or notes: A merged user report says a door and most vegetation are missing. It attributes the symptom to mesh-shader pipelines being skipped when VK_EXT_mesh_shader is unavailable; the reporter could not confirm on screen that the missing objects corresponded exactly to those draws.
Problems or notes: A draft compute-based fallback reportedly rendered falling leaves, ground leaves, and some foliage shadows with correct textures, but the emulated geometry flickered and canopies, grass, and house walls remained missing.
Problems or notes: Missing leaves, foliage, walls, textures, and other geometry. The report says attempted recompilation and builds 78, 88, 92, Fritzi v2, and perf/Fritzi-Intergrated did not resolve the issue; comments report that #395, #434, and #430 did not restore the geometry.
Problems or notes: Large flat red patches appear across the wet stream bed by the road from Castle Town Market to Hyrule Castle. Another user later reported that stream as clean with their build, attributing the earlier difference possibly to missing #432 and #351; this report's setup used build-95.
Problems or notes: Stalls at a black screen; repeated native MME macro execution failures are reported. Enabling compute pipelines, clearing pipeline caches, and disabling implicit Vulkan layers did not resolve the issue.
Problems or notes: A user-provided build-95 log shows the game loading, followed by a compute pipeline compilation error and an unhandled SIGSEGV. The user later supplied crash details indicating a null-pointer dereference. The log identifies KDE neon User Edition as the host OS.
Problems or notes: Black screen at the intro video after the loading shaders screen; music continues, FPS counter stays at 0, and GPU channels wait on unreleased semaphores. Build 93 reaches gameplay on the same machine. Two other users report the same build 95 hang on Linux with NVIDIA RTX 3060 and RTX 3090 systems. Two users say EDEN_NX2_SPLIT=1 makes the game work.
Problems or notes: User reports that motion controls are affected: Motion 1/Motion 2 mapping does not detect shaking, and gyro/accelerometer input stops after the controller reconnects or after a few seconds with Steam running.
Current: build-93 (3 records); previous: build-88 (0 records).
Also listed as: OoT
| Build | Status | GPU / CPU | FPS | Details |
|---|---|---|---|---|
| Not provided | not booting | AMD Radeon RX 6700 XT (12 GB) / AMD Ryzen 9 5900X | Not provided | Open report |
Problems or notes: On first launch, shader rebuild runs for about 9-10 minutes, then Lichii closes with no error message. The reported Event Viewer faulting module is amdvlk64.dll with exception code 0xc0000005.
Showing 91–100 of 194 reports
Known issues from Lichii sources
On AMD Radeon RX 9070 XT with driver 2.0.416, a dotted cyan/magenta line appeared along mountain and sky silhouettes in Hyrule Field.
Recorded fix: Zero the color write mask of render targets the fragment shader does not store; the issue comment says this fix landed in build 95.
Coloured blocks or a magenta line along the Hyrule Field mountain ridge on AMD GPUs; the original report described NaNs in the scene target that bloom spread into a coloured band.
Recorded fix: The #353 per-component write-mask fix was reported to remove the coloured blocks or line. A temporary workaround is to set EDEN_NX2_REJECT_HASH=fe1f903f1bf52a9d,4f5673eca06ebecb, which drops the draw and loses its far-distance effect.
Distant mountains remain overexposed with a white glow after the coloured blocks are removed; the source identifies this as a separate bloom/exposure issue.
On Linux with AMD RX 9000-series graphics using RADV, an invalid SPIR-V fragment shader can cause a segfault during Vulkan graphics-pipeline construction during gameplay.
Recorded fix: Fixed in build 93 and later releases.
On AMD's proprietary Windows Vulkan driver, the intro could freeze while two compute shaders were optimized, taking 6–18 minutes; long graphics-pipeline builds can also cause substantial in-game stalls.
Recorded fix: Build 93 and later build the two identified compute shaders without driver optimization on AMD's proprietary Vulkan driver. The source says long graphics-pipeline builds are a separate matter and are not covered.
On earlier builds, small details such as leaves, pebbles, and grass flickered or appeared black with Low GPU accuracy and the split GPU thread enabled.
Recorded fix: Update to build 95 or later; the source attributes the fix to buffer usage tracking changes, with additional near-foliage fixes. EDEN_NX2_PERF_VERIFY=1 was an earlier workaround but was reported as no longer needed on build 95.
A user reports that games do not work on a Lenovo Legion Go 2 Z2 with an eGPU 7600xt on Version 95; on Version 93 or earlier, they can see the scene.
On Linux with AMD graphics, Fire Emblem: Fortune's Weave can crash after a black screen with VK_ERROR_DEVICE_LOST and a GPU reset.
On Windows 11, extracting a NUP to a path longer than 260 characters fails even when LongPathsEnabled is set. The issue reports a malformed longPathAware manifest entry as the probable cause.
AV1 cinematics are delayed, with audio playing faster.
Showing 161–170 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é.