Zelda: Ocarina of Time
Conflicting reports of low and high frame rates on an RX 9070 XT, with one comment suggesting Windows performance may be worse than Linux.
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 76 entrées par jeu et environnement, et 175 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.
| Build | Status | GPU / CPU | FPS | Details |
|---|---|---|---|---|
| build-75 | runs with issues | NVIDIA GeForce RTX 5080 (16 GB) / Intel Core Ultra 7 270K Plus (24 threads) | 28–29 FPS | Open report |
Problems or notes: User report: Docked mode was required to render; Handheld showed a black 3D screen. Gameplay settled at 28–29 FPS, while menus and loading screens ran at 53–59 FPS. The report attributes the limit to CPU load. No attempted settings changes improved the gameplay ceiling.
Current: build-75 (1 record); previous: build-70 (0 records).
| Build | Status | GPU / CPU | FPS | Details |
|---|---|---|---|---|
| build-75 | runs with issues | NVIDIA RTX 3050 Laptop / AMD Ryzen 7 5800H | 30 FPS | Open report |
Problems or notes: User report: The game boots and presents frames at a steady 30 FPS, but remains on a black screen after its AV1 video streams fail because FFmpeg has no decoder for "video/av1". NVDEC Off and Gpu reportedly make no difference; the same result was reported on an AMD Radeon iGPU. Vulkan was used.
Current: build-75 (1 record); previous: build-70 (0 records).
| Build | Status | GPU / CPU | FPS | Details |
|---|---|---|---|---|
| 75 (`nx2-build-75`, Linux x86_64 PGO AppImage) | runs with issues | AMD RX 7000 series (Radeon RX 7600, RADV 26.2.5, Vulkan 1.4.354) / Not provided | Not provided | Open report |
Problems or notes: During the intro AV1 cutscene, the video area is solid green; audio and subtitles work. The report says decoded frames are produced at 60 fps, but the image does not reach the screen.
| Build | Status | GPU / CPU | FPS | Details |
|---|---|---|---|---|
| `nx2-build-75`, MSVC x86_64 (`lichii-windows-x86_64.zip`) | runs with issues | AMD Radeon RX 6700 XT 8 GB, AMD driver 2.0.353, Vulkan 1.4.315 / AMD Ryzen 7 5800X, 32 GB RAM | Not provided | Open report |
Problems or notes: The game renders normally before the intro AV1 cutscene, but the video layer is black while audio and subtitles work, then the emulator hangs indefinitely. The report says the freeze starts when the AV1 decoder opens.
Also listed as: OoT
| Build | Status | GPU / CPU | FPS | Details |
|---|---|---|---|---|
| Not provided | playable | RTX 4070 SUPER / Not provided | 59.3–60 FPS | Open report |
Problems or notes: A commenter reports no texture flicker during roughly six minutes of gameplay with Low GPU accuracy and EDEN_NX2_SPLIT=2; light scenes reached the game's 60 FPS cap.
| Build | Status | GPU / CPU | FPS | Details |
|---|---|---|---|---|
| build-75 | runs with issues | Adreno 740 / Snapdragon 8 Gen 2 | Not provided | Open report |
Problems or notes: Black screen despite booting to the AV1 video stage; pipeline-builder threads remain busy compiling large compute shaders, with memory exhaustion or GPU hangs reported in tests. Audio was intermittent. In a separate Eglantine PR #614 test, it reached the title screen and New Game, then went black at the first in-game frame at about 60 FPS.
Current: build-75 (1 record); previous: build-70 (0 records).
| Build | Status | GPU / CPU | FPS | Details |
|---|---|---|---|---|
| build-93 | runs with issues | AMD RX 9000 series / Not provided | Not provided | Open report |
| build-93 | runs with issues | RTX 3060 Ti / Intel Core i7-12700 | 19–31 FPS | Open report |
| build-93 | runs with issues | NVIDIA RTX 50 series; AMD RX 9060 XT 16gb graphics card / Not provided | Not provided | Open report |
| build-75 | not booting | AMD Radeon RX 6750 XT (RDNA2) / Intel Core i7-11700F | Not provided | Open report |
Problems or notes: The emulator closes when loading Hyrule Market after the user exits Kokiri Forest and enters Hyrule Castle.
Problems or notes: About 31 FPS on average, down to about 19 FPS, with short freezes while attacking in crowded scenes. The report attributes performance stalls to front/back GPU thread serialization. With EDEN_NX2_PRELOAD_ALL_PIPELINES=1, runtime pipeline builds fell from 942 to 65 and frames over 100 ms fell from 77 to 40 during the reported session.
Problems or notes: The user reports textures not working properly, slow frame rate, and a shield glitch. They also report that trying a '.dat' file did not work. The issue body gives conflicting GPU details.
Problems or notes: On Windows 11 25H2, the game passes the initial launching stage but becomes unresponsive at “Building 9 shaders”; audio continues and it does not reach gameplay. The report identifies the game as Switch 2 version 1.1.1.
Current: build-93 (3 records); previous: build-88 (0 records).
Showing 1–10 of 98 reports
Known issues from Lichii sources
Conflicting reports of low and high frame rates on an RX 9070 XT, with one comment suggesting Windows performance may be worse than Linux.
The issue says FPS is worse than on most other forks.
A black screen with title music and unresponsive controls; after waiting for shaders to load, the game worked but was extremely glitchy and laggy.
Recorded fix: Waiting for shaders to load resolved the reported black screen, according to the user; gameplay remained unplayable.
The emulator closes when loading Hyrule Market after the user exits Kokiri Forest and enters Hyrule Castle.
The console restarts after the scene on Linux with a lenovo legion go 2 z2 and egpu 7600xt; the report names versions 83 et 93.
On AMD RX 9070XT under SteamOS/Linux, the game reportedly froze before the title screen, then showed pixel artefacts and caused a system crash.
The source refers to the game as OOT but does not clearly identify which listed Ocarina of Time game it is. On AMD RX 9070XT under SteamOS/Linux, loading a save reportedly led to a black screen and system crash. After trying EDEN_NX2_NO_MESH=1, rendering and shading issues remained.
Walls and objects are missing/not rendered inside the Deku tree.
Overexposure in specific areas, including the lower part of Saria's house and the right side of the entrance to hyrule castle.
User reports audio/video desynchronization on the title screen and intro; a commenter reports slow-motion live-rendered title-screen video with audio leading by approximately three seconds, worsening by the initial dream cutscene.
Showing 101–110 of 188 issues
Notes de version récentes
Version build-94 · Ocarina of Time
Version build-94 · Non renseigné
Version build-94 · Non renseigné
Version build-94 · Non renseigné
Version build-94 · Non renseigné
Choix d’une 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.
build-83 · Publiée le November 6, 2026
12 fichiers à télécharger pour cette version.
Essayez la dernière version disponible : build-94. 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é.