The Legend of Zelda: Ocarina of Time Remake
Crashes at the same moment as it flies under the user's feet; the log reports an application error in amdvlk64.dll.
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 | AMD Radeon RX 7900 XTX / Not provided | 12 FPS | Open report |
| build-70 | not booting | NVIDIA GeForce RTX 3070 / AMD Ryzen 7 5800X 8-Core Processor | Not provided | Open report |
| R75 MSVC | boots | Not provided / Not provided | Not provided | Open report |
| build 83 (MSVC) | runs with issues | NVIDIA GeForce GTX 1070 / Intel Core i7-7700 | 18 FPS | Open report |
| Not provided | runs with issues | RX 5700 / Not provided | Not provided | Open report |
| Not provided | runs with issues | AMD Radeon RX 7900 XTX / Not provided | Not provided | Open report |
| Not provided | runs with issues | AMD Radeon RX 7900 XTX / Not provided | Not provided | Open report |
| nx2-build-88 (55532f2) | runs with issues | NVIDIA GeForce RTX 5060 (8 GB VRAM) / AMD Ryzen 5 5600G (6C/12T) | Not provided | Open report |
| nx2-build-93 | runs with issues | RTX 2060 6 GB / Xeon E5-1620 v3 (4C/8T) | Not provided | Open report |
Problems or notes: User reports no hang, but the 3D scene is black with HUD only.
Problems or notes: Issue reporter says the game remains on "Launching..." indefinitely; the log shows the emulated program breaking execution with error F001. Additional user reports mention infinite launch screens. Other users report that R75 MSVC boots past the intro FMV in docked mode, but describes severe white/black-screen graphics problems in other builds or modes.
Problems or notes: A user reports booting and working past the intro FMV in docked mode; no sustained gameplay is stated.
Problems or notes: User report: Approximately 18 FPS in gameplay, with frequent hangs or stalls whose trigger and duration were not isolated. Settings included Vulkan, 1X resolution, Accurate GPU mode, and Handheld console mode.
Problems or notes: The local ClangCL build of b8c812b18 stalled at max present 8 and showed no frames. A local MSVC build of the same commit also stalled at max present 8 and died within a minute.
Problems or notes: User reports GPU hang or device loss when gameplay starts on local build 27226d2. A separate local build with #150 reverted, #127 kept, and docked mode reportedly avoids the hang and renders the full scene at about 24 FPS; another configuration without #127 renders only areas lit by Navi.
Problems or notes: A user reports a local 27226d2 build with #150 pointer-binding commits reverted ran for 5+ minutes past the point where the original build timed out; grass and trees were reportedly still missing.
Problems or notes: In a 1h 49m gameplay session, the reporter observed severe 1.3–6.59 second freezes, continuous frame-time micro-stutters, repeated GPU-thread shader translation stalls, and 579,265+ synchronous OnCPURead waits. The session had 0 crashes. Vulkan, 1x, GPU Mode Accurate, Async GPU and async shader compilation enabled, and Enable Reactive Flushing enabled.
Problems or notes: A user follow-up reports FPS averages falling from 53 in the first 10-minute bucket to about 23 in the 80–90-minute bucket during a 98-minute session with Reactive Flushing enabled, alongside 365,889 OnCPURead events and stalls over 2 seconds. In additional roughly 100-minute sessions, OnCPURead growth occurred with Reactive Flushing both on and off; with it off, FPS averages were 16–33 after the first 10 minutes and stalls reached 12 seconds, with one around 49 seconds. The reporter notes the comparison is not conclusive.
Current: build-83 (1 record); previous: build-75 (2 records).
Also listed as: OoT
| Build | Status | GPU / CPU | FPS | Details |
|---|---|---|---|---|
| build-93 | runs with issues | AMD Radeon RX 6900 XT / AMD Ryzen 9 5900X | 24–30 FPS | Open report |
Problems or notes: Severe lighting flickering and overexposure or corrupted lighting effects; significant slowdowns in some sequences; audio desynchronization during cinematics; initial shader compilation takes considerable time. The user reports approximately 24 FPS in Kokiri Forest and approximately 30 FPS in menus and some cinematics.
Current: build-93 (4 records); previous: build-88 (0 records).
Showing 31–40 of 98 reports
Known issues from Lichii sources
Crashes at the same moment as it flies under the user's feet; the log reports an application error in amdvlk64.dll.
User reports freezing while loading a game and a subsequent emulator crash on macOS; in Build 93, pressing A on a controller reportedly does nothing when attempting to return to the title screen.
In the measurement-only experiment, disabling per-fence Preflushable downloads or batching downloads by 64 fences caused overexposure in Kokiri Forest.
A commenter reports that an experimental compute storage write-extent analysis reduced marked GPU-written data and fence copies while preserving correct auto-exposure. It was described as code on a user's branch, not as an upstream or validated release fix.
Static review and a separate research comment describe read-trap bookkeeping and dirty-state issues that can leave stale GPU-written data when per-fence downloads are disabled; proposed corrections and batching remain untested or local experiments.
User reports the game is locked at 20 FPS, including menus and title screen, on Windows 11.
The game reaches responsive gameplay with a correctly rendered HUD, but the 3D scene is black. Graphics programs are rejected and draws are skipped.
On AMD's proprietary Windows driver, two compute pipelines can take 6 to 18 minutes to compile during the intro, leaving the game at 0 FPS while audio continues. Rejecting the shader hashes avoids the wait but causes black areas in the intro, title, and castle scenes.
Recorded fix: Leave the game at the intro for about 20 minutes once so both pipelines finish and are cached; later boots reportedly pass the intro immediately until the driver or Lichii is updated. Alternatively, set `EDEN_NX2_REJECT_HASH=eff3ccbe1438679d,f9ea14a22394f5b1`; this avoids the wait but leaves parts of the picture black.
User reports an unhandled Vulkan::vk::Exception and emulator crash shortly after the first cutscene when texture allocation fails with VK_ERROR_OUT_OF_DEVICE_MEMORY on an AMD Radeon RX 9060 XT 8 GB.
Game freezes when the user tries the Ocarina at the Temple of Time.
Showing 121–130 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é.