The Legend of Zelda: Ocarina of Time
Issue reports describe audio desynchronization and crashes or full-system freezes during early cutscenes on AMD graphics cards.
Spielekompatibilität
Du hast ein bestimmtes Spiel im Sinn? Erfahre, wie es mit Lichii läuft, welche Probleme bekannt sind und welchen Build du ausprobieren kannst.
Ein Spiel finden
98 Einträge zu Spielen und Testumgebungen sowie 275 Lichii-Berichte sind derzeit erfasst.
Dein Spiel fehlt? Ein leeres Suchergebnis bedeutet, dass noch kein Lichii-Bericht erfasst ist. Daraus lässt sich kein fehlgeschlagener Test ableiten.
An der Plattformangabe erkennst du, welche Version eines Spiels gemeint ist.
Was die Statuswerte bedeuten: Unknown bedeutet, dass kein Ergebnis feststeht. Not booting heißt, dass das Spiel nicht startete. Boots steht dafür, dass nur der Start gelang. Runs with issues bezeichnet Probleme beim Spielen. Playable heißt, dass der Tester weiterspielen konnte.
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
| Build | Status | GPU / CPU | FPS | Details |
|---|---|---|---|---|
| build-93 | runs with issues | RX 9070 XT / Ryzen 7 9800X3D | 14–37 FPS | Open report |
| build-88 | runs with issues | RTX 4070 Ti 12 GB / Ryzen 7 5800X3D | Not provided | Open report |
| Not provided | not booting | 6700 xt / Not provided | Not provided | Open report |
| Not provided | runs with issues | AMD Radeon RX 6900 XT 16GB / Intel Xeon E5-2697v3 | Not provided | Open report |
| nx2-build-88 | runs with issues | RX 7800 XT / Not provided | Not provided | Open report |
| Not provided | not booting | RX 9060 XT 16gb / Not provided | Not provided | Open report |
| build-95 (the release tagged `build-94`) | runs with issues | RX 5700 / Not provided | 14–24 FPS | Open report |
| build-117 (PGO) | playable | RX 9070 XT / Ryzen 7 9800X3D | Not provided | Open report |
Problems or notes: Boots to title and reaches gameplay without crashes or driver timeouts. Reported approximately 18 FPS on defaults, 17 FPS with async shaders on and GPU accuracy Normal, 14 FPS with async shaders on and GPU accuracy High, and approximately 29 FPS with defaults plus the stated logging, process-priority, and Xbox Game Bar capture changes in Kokiri Forest; intro cutscenes run 32–37 FPS. Gameplay is reported in slow motion. Heavy bloom and overexposure occur in bright areas, and the Great Deku Tree appears as a dark silhouette in its intro scene. One Lichii thread reaches 99% of a core.
Problems or notes: Vulkan reached cutscenes; a visible-window run lasted approximately five minutes without a reported TDR. Two hidden/minimized CLI launches crashed in nvoglv64.dll with exception 0xc0000094 at offset 0xEFC9BB. Pipeline-build stalls and cumulative draw-hold time were reported; the measurements are not frame times or FPS.
Problems or notes: A commenter reports an instant crash after trying the EDEN_NX2_NO_MESH=1 workaround.
Problems or notes: On nx2-build-117, the user reports that EDEN_NX2_NO_MESH=1 avoided device loss for a session of about 176 seconds. The variable skipped 27 draws; the user noticed no obvious visual issues but could not rule out missing visuals.
Problems or notes: Disabling mesh draws with EDEN_NX2_NO_MESH=1 did not prevent the device-loss crash on this configuration; it occurred after the intro cutscene.
Problems or notes: Commenters report crashes when attempting the EDEN_NX2_NO_MESH=1 workaround; one says the screen goes black after the intro and the emulator closes. Game version 1.1.1 is stated by another commenter with a separate instant-crash report.
Problems or notes: Short session in Kokiri Forest and the Deku Tree rendered correctly, with no crash, fence timeout, device loss, or compute rejections. Reported 14 FPS in Kokiri Forest and 22–24 FPS indoors; the commenter says outdoor performance was identical to build 93.
Problems or notes: Commenter reports about 70 minutes of play through the Deku Tree and Gohma with zero blackouts and no Native compute shader rejected (per-tap gather) error, using game version 2.0.0 loaded from a .nup. The same user says blackouts and the log error occurred with extracted base-game version 1.0.0.
Current: build-93 (4 records); previous: build-88 (1 record).
Also listed as: OoT, Ocarina of Time
| Build | Status | GPU / CPU | FPS | Details |
|---|---|---|---|---|
| build-117 | playable | Radeon RX 9070 XT / AMD Ryzen 7 5700X | 19–65 FPS | Open report |
| nx2-build-92 | runs with issues | RX 7800 XT (RADV) / Ryzen 7 7700X | 35–59 FPS | Open report |
Problems or notes: The user reports rendering works again. In Wayland, around 19–25 FPS, fluctuating. In XWayland with QT_QPA_PLATFORM=xcb, Kokiri Village measured 25–54 FPS, usually around 30 FPS; inside the Deku Tree usually 30–45 FPS while idle, occasional peaks to 65 FPS, and recurring drops to 19 FPS. The user reports normal game speed despite frame drops and says the game is playable; FPS/frametime variability remains substantial.
Problems or notes: Ubuntu 26.04, Docked, GPU accuracy Low. Without EDEN_NX2_NO_MESH=1, device loss occurs while loading a save. With the variable, a single 337-second session ran until the user closed it; approximately 59 FPS with dips to 35–50 and some stutter, 47 draws skipped, and a door was transparent at the start. This was not tested in a new game.
Current: build-117 (1 record); previous: build-116 (0 records).
Showing 111–120 of 142 reports
Known issues from Lichii sources
Issue reports describe audio desynchronization and crashes or full-system freezes during early cutscenes on AMD graphics cards.
On AMD RDNA2 GPUs, the 16x16x16 VK_KHR_cooperative_matrix HMMA pipeline path can cause an access violation in amdvlk64.dll during shader or pipeline compilation, typically 30–90 seconds after game startup.
Recorded fix: The source reports that EDEN_NX2_NO_COOP_MATRIX=1 avoids the crash. A later comment states that merged PR #657 fixes it.
On Linux, a black screen can occur with the Native MME error "instruction outside uploaded RAM". One report says shaders load and menu music is audible; another says the game opens, reaches 0 FPS, and freezes.
Recorded fix: A comment reports that setting DMA accuracy to Safe works as a workaround. Another comment attributes the error to a GCC 13 miscompile and says a fix was merged but was not yet in a published release.
Cutscenes play in slow motion, lagging behind audio; the report describes them as locked to 49fps with 99% GPU usage.
The same slow-motion cutscene problem is reported.
The same slow-motion cutscene problem is reported.
After the Kaepora Gaebora cutscene near Hyrule Castle, the scene appears empty and foggy and Link repeatedly falls through the world and voids out, preventing progression.
User reports 17–23.8 FPS in 3D races on build-95, compared with 40.0–54.1 FPS on build-93 under the same reported test conditions.
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.
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.
Showing 91–100 of 287 issues
Aktuelle Release-Hinweise
Build build-117 · Ocarina of Time
Build build-116 · Zelda: Ocarina of Time
Build build-116 · Zelda: Ocarina of Time
Build build-116 · Zelda: Ocarina of Time
Build build-116 · Mario Tennis Fever
Den passenden Build finden
build-75 · Veröffentlicht am November 5, 2026
12 veröffentlichte Downloaddateien für diesen Build.
Probiere den neuesten verfügbaren Release aus: build-117. Behalte beim Testen einen funktionierenden Build, zu dem du zurückkehren kannst.
Fragen zur Kompatibilität
Setze die Filter für Spiel, Status, GPU und Build und kopiere anschließend die Seitenadresse. Ein direkter Link zum Spiel öffnet dessen Berichtskarte.
Prüfe in anderen Berichten, ob das Spiel bis zum Menü oder ins Spielgeschehen gelangt. Notiere Treiber und Renderer und suche nach dem Spiel oder dem Fehler in der Anleitung zur Fehlerbehebung.
Treiberversion, Grafikeinstellungen, CPU-Auslastung und die getestete Spielszene können das Ergebnis beeinflussen. Vergleiche diese Details, bevor du deine Konfiguration änderst.
Nutze den offiziellen Issue-Tracker von Lichii. Nenne das Spiel, den Build-Tag, Hardware, Treiber, Einstellungen und die Schritte, mit denen sich deine Beobachtung reproduzieren lässt.