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 |
|---|---|---|---|---|
| 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 |
| 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 |
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%.
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.
Current: build-117 (2 records); previous: build-116 (0 records).
Showing 151–160 of 308 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
Choisissez un jeu ci-dessus pour voir quelles versions testées sont disponibles au téléchargement. En attendant, utilisez la dernière version disponible et lisez ses notes.
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é.