Ocarina of Time
AMD black foliage and haze.
Spielekompatibilität
Spielekompatibilität des Lichii Emulators
Du hast ein bestimmtes Spiel im Sinn? Erfahre, wie es mit Lichii läuft, welche Probleme bekannt sind und welchen Build du ausprobieren kannst.
Latest recorded build
build-94
Pre-release
Published November 7, 2026
Ein Spiel finden
Nach kompatiblen Lichii-Spielen suchen
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
Game Compatibility Results
Recorded performance
Performance by Build and Hardware
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.
Donkey Kong Bananza Reported platform: Windows 11
| Build | Status | GPU / CPU | FPS | Details |
|---|---|---|---|---|
| build-88 | unknown | RTX 4070 / i7 13700k | 20 FPS | Open report |
| build-70 | runs with issues | NVIDIA RTX 40 series / Not provided | Not provided | Open report |
| build 70 (286117c) | runs with issues | AMD RX 6000 series or older / Not provided | 57 FPS | Open report |
| latest prelease build 93 | not booting | AMD RX 6000 series or older / Not provided | Not provided | Open report |
build-88 report
Statusunknown
GPURTX 4070
CPUi7 13700k
DriverNot provided
Recorded FPS20 FPS
Problems or notes: User report: locked at 20 FPS, including menus and title screen. The user says they do not know whether this is a regression.
build-70 report
Statusruns with issues
GPUNVIDIA RTX 40 series
CPUNot provided
DriverNot provided
Recorded FPSNot provided
Problems or notes: Picture is covered with weird artifacts especially on shadows.
build 70 (286117c) report
Statusruns with issues
GPUAMD RX 6000 series or older
CPUNot provided
DriverNot provided
Recorded FPS57 FPS
Problems or notes: With Vulkan, 1x, handheld, GPU Fast, VRAM Aggressive, Nearest, AA off, and no frame generation, gameplay runs at ~57 fps before the process aborts after 133.8 seconds with 0xC0000409 at lichii.exe+0x2ecd3bd. On the MinGW PGO zip of the same build, it reportedly aborts on the intro screen seconds in, at the same offset.
latest prelease build 93 report
Statusnot booting
GPUAMD RX 6000 series or older
CPUNot provided
DriverNot provided
Recorded FPSNot provided
Problems or notes: User reports a crash when loading a save.
Related game issues
- [Crash] Bananza runs at ~57 fps then aborts silently, 0xC0000409 at +0x2ecd3bd (closed)
- [Crash] rx 6800xt all emulators crash on loading screen (open)
- [VBug] Build 93 finaly has no major visual errors but has poor performance 9070xt (open)
- [UIBug] Bananza — build 93 (open)
- [Crash] donkey kong and ocarina crash on AMD 6800xt (open)
- Donkey Kong Bananza (040074A01BF12000): fatal 2111-3604 right after a VP9 video reaches end of stream (nx2:vdecsvc) (closed)
- [GBug] Donkey Kong Bananza locked at 20 fps (open)
- Donkey kong bananza Crash loading (closed)
- [VBug] Shadow artifacts (closed)
- [GBug] Donkey kong bananza, black rectangle (closed)
- Donkey Kong Bananza: terrain missing (white/black) on builds 70 and 75, renders correctly on build 65 (open)
- donkey kong bananza purple screen issue (closed)
- Release note: On build 70 (286117c), the MSVC zip aborts after 133.8 seconds of gameplay with 0xC0000409 at lichii.exe+0x2ecd3bd. The MinGW PGO zip reportedly aborts on the intro screen at the same offset.
- Release note: User reports the game crashes when the loading screen appears on Windows 10 with an AMD RX 6000 series or older graphics card.
- Release note: The issue says FPS is worse than on most other forks.
- Release note: On build 93, FPS fluctuates approximately between 20 and 60, with frequent periods around 30 and drops to 25–28 FPS in the Dragon Layer; GameSir G7 Pro rumble can be excessive, occur without an obvious trigger, or continue longer than expected.
- Release note: User reports a crash when loading a save on AMD RX 6000 series or older under Windows 11.
- Release note: User reports the game is locked at 20 FPS, including menus and title screen, on Windows 11.
- Release note: Weird artifacts, especially on shadows.
- Release note: A black rectangle appears in a mini-example guide; the reporter says it persists on build-70.
- Release note: On Windows builds 70 and 75, terrain/world renders solid white while the HUD and characters still render. On build 75, EDEN_NX2_RESETFIX=0 changes the ground to black with no texture or lighting.
Compared with Previous Build
Current: build-88 (1 record); previous: build-83 (0 records).
Showing 1–4 of 4 reports
Known issues from Lichii sources
Known Game Issues
Ocarina of Time
HUD flicker.
Ocarina of Time
Cutscene audio drift.
Ocarina of Time
First-launch shader stall on Linux.
Ocarina of Time
An NVIDIA device-lost crash was reported on build 93; the release says it is awaiting retest on this build.
Zelda: Ocarina of Time
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.
Star Fox
On RTX 50-series GPUs, the GPU device can still be lost after a scene change.
Recorded fix: Try NVIDIA driver 610.88.
Star Fox
Gameplay is capped at about 30 fps, even though the game asks for 60.
Star Fox
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.
Yoshi and the Mysterious Book (demo)
Some textures are still black, and the game can crash later in play.
Showing 1–10 of 188 issues
Aktuelle Release-Hinweise
Kompatibilitätsänderungen in den neuesten Builds
Build build-94 · Ocarina of Time
Fixes near foliage disappearing, white flashes during camera movement, terrain drawn over the scene, a stale Z-target reticle, and several shader issues. The changes had only limited gameplay testing.
Build build-94 · Nicht angegeben
Fixes a race-related random crash involving an unallocated SparseLargeVector region, which the release says can affect any game.
Build build-94 · Nicht angegeben
Adds LayeredFS mod support for NUP titles.
Build build-94 · Nicht angegeben
The migration prompt's Keep Old Data option now keeps data instead of moving it.
Build build-94 · Nicht angegeben
Adds an experimental option to pin GPU threads to their own cores. It is off by default and requires 6 or more physical performance cores.
Den passenden Build finden
Welchen Build soll ich verwenden?
build-88 · Veröffentlicht am November 6, 2026
Donkey Kong Bananza
- unknown · GPU RTX 4070 · CPU i7 13700k · Treiber Nicht angegeben
7 veröffentlichte Downloaddateien für diesen Build.
build-70 · Veröffentlicht am November 4, 2026
Donkey Kong Bananza
- runs with issues · GPU NVIDIA RTX 40 series · CPU Nicht angegeben · Treiber Nicht angegeben
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
Häufige Fragen zur Spielekompatibilität
Wie teile ich ein Spiel mit diesen Filtern?
Setze die Filter für Spiel, Status, GPU und Build und kopiere anschließend die Seitenadresse. Ein direkter Link zum Spiel öffnet dessen Berichtskarte.
Was kann ich bei einem schwarzen Bildschirm versuchen?
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.
Warum kann dieselbe GPU unterschiedliche Ergebnisse liefern?
Treiberversion, Grafikeinstellungen, CPU-Auslastung und die getestete Spielszene können das Ergebnis beeinflussen. Vergleiche diese Details, bevor du deine Konfiguration änderst.
Wo kann ich ein fehlendes Testergebnis melden?
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.