Zelda Ocarina of Time
On build 83, a user reports device loss at gameplay start with VK_ERROR_DEVICE_LOST.
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
76 Einträge zu Spielen und Testumgebungen sowie 175 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.
| 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 58 reports
Known issues from Lichii sources
On build 83, a user reports device loss at gameplay start with VK_ERROR_DEVICE_LOST.
On the Vulkan backend with an AMD RX 6750 GRE, eight compute shaders are reported rejected with VK_ERROR_OUT_OF_HOST_MEMORY; the AV1 intro video is not presented and the process later aborts with 0xc0000409.
The screen has visual noise ("nieve") and lag when entering the game.
User reports GPU driver timeout or device loss when gameplay starts on AMD Windows systems, including RX 7900 XTX and RX 9060 XT. Reports associate the issue with #150 pointer-binding changes, but this is an unconfirmed hypothesis.
On build-93, reported low FPS causes gameplay to run in slow motion; users also report heavy bloom and overexposure in bright areas and a dark-silhouette rendering of the Great Deku Tree in its intro scene.
On the Lichii-AMD 2026.11.07 (nauxph fork, f4e938f516), GPU Mode Fast reportedly causes recurring blackouts of the game world while the HUD remains visible; the game continues running.
Recorded fix: Switching GPU Mode from Fast to Accurate at runtime restores the picture without restarting; the user reports Accurate avoids blackouts but causes heavy stutter.
A user reports that gpu_accuracy, scaling_filter, and anti_aliasing values edited in qt-config.ini are rewritten at startup and says these settings must be changed through the GUI.
Shaders load slowly and significantly slow gameplay, rebuilding when entering the same area. In the Kokiri Sword area, Link and most surroundings turn solid black; white flickers also occur.
User reports a crash at the first cutscene and emulator shutdown after compiling existing shaders on reboot.
On AMD Radeon RX 6800 XT, opening the game leaves the screen black with no video output and unresponsive controls; music eventually stops.
Showing 51–60 of 188 issues
Aktuelle Release-Hinweise
Build build-94 · Ocarina of Time
Build build-94 · Nicht angegeben
Build build-94 · Nicht angegeben
Build build-94 · Nicht angegeben
Build build-94 · Nicht angegeben
Den passenden Build finden
build-93 · Veröffentlicht am November 6, 2026
7 veröffentlichte Downloaddateien für diesen Build.
build-75 · Veröffentlicht am November 5, 2026
12 veröffentlichte Downloaddateien für diesen Build.
Probiere den neuesten verfügbaren Release aus: build-94. 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.