Ocarina of Time
AMD black foliage and haze.
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-94 | not booting | Radeon RX 7800 XT / Not provided | Not provided | Open report |
| build-94 | not booting | RTX 5070 / Ryzen 5 7600X | Not provided | Open report |
Problems or notes: Without the workaround, a black screen with audio and repeated split-front macro errors; only presents #1 through #8 occurred before rendering stopped. With EDEN_NX2_SPLIT=1, the game rendered and reached present #1200 about 47 seconds after launch.
Problems or notes: Black screen and emulator hang about 26 seconds after boot with split-front macro errors. EDEN_NX2_SPLIT=1 was reported to make it run normally in a 60-second test.
Current: build-94 (2 records); previous: build-93 (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 |
|---|---|---|---|---|
| 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 |
|---|---|---|---|---|
| nx2 @ 09b78bd2df | runs with issues | NVIDIA GeForce GTX 1070 (Pascal) / Not provided | Not provided | Open report |
| 95 | not booting | AMD Radeon RX 7900 XTX (RADV) / Intel Core i7-11700K | 0 FPS | Open report |
Problems or notes: User reports missing scene parts, including a door and most vegetation, during gameplay. The source says it could not confirm these were caused by skipped mesh draws.
Problems or notes: Stalls on a black screen. Logs report native MME macro execution failures, including instruction outside uploaded RAM. Enabling compute pipelines, clearing pipeline caches, and disabling implicit Vulkan layers did not resolve the issue.
Also listed as: OoT
| Build | Status | GPU / CPU | FPS | Details |
|---|---|---|---|---|
| build 83 (clang 23.1.6) | runs with issues | AMD RX 9000 series / Not provided | Not provided | Open report |
| Not provided | runs with issues | egpu 7600xt / lenovo legion go 2 z2 | Not provided | Open report |
Problems or notes: User reports repeated segfaults during gameplay in the Great Deku Tree while RADV builds a graphics pipeline. The reported fragment shader fails spirv-val because its depth image sampled type is u32 while the sampling result type is f32.
Problems or notes: The console restarts after the scene.
Also listed as: OoT
| Build | Status | GPU / CPU | FPS | Details |
|---|---|---|---|---|
| Not provided | unknown | RTX 3080 Ti / i9-12900K | 46–47.8 FPS | Open report |
Problems or notes: A user comment reports same-binary, 300-second headless-harness measurements in Kokiri Forest: median FPS was 46.0 in Full mode and 47.8 in Auto mode. The comment reports correct auto-exposure in both modes and identifies readback bandwidth and stale-constants flicker as visible concerns; no sustained gameplay validation is stated.
Showing 1–9 of 9 reports
Known issues from Lichii sources
AMD black foliage and haze.
HUD flicker.
Cutscene audio drift.
First-launch shader stall on Linux.
An NVIDIA device-lost crash was reported on build 93; the release says it is awaiting retest on this build.
Outdoor areas have far too much fog and glow compared with console; performance is about 12–22 fps on a Ryzen 5900X with an RTX 3080, and three rare shaders remain unsupported.
On RTX 50-series GPUs, the GPU device can still be lost after a scene change.
Recorded fix: Try NVIDIA driver 610.88.
Gameplay is capped at about 30 fps, even though the game asks for 60.
On RTX 50-series GPUs (5070 Ti, 5090), the GPU device can be lost shortly after a scene change.
Recorded fix: Try NVIDIA driver 610.88.
Some textures are still black, and the game can crash later in play.
Showing 1–10 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-94 · Veröffentlicht am November 7, 2026
7 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.