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: unknown
Also listed as: dkb
| Build | Status | GPU / CPU | FPS | Details |
|---|---|---|---|---|
| nx2 build 65 (3bdd53d) | runs with issues | Sapphire nitro+ 7900XTX / 9800x3D | Not provided | Open report |
| Not provided | unknown | RX 9070 XT / Not provided | Not provided | Open report |
| Not provided | not booting | AMD RX 6000 series or older / Not provided | Not provided | Open report |
nx2 build 65 (3bdd53d) report
Statusruns with issues
GPUSapphire nitro+ 7900XTX
CPU9800x3D
Driver26.10.1
Recorded FPSNot provided
Problems or notes: A black rectangle appears in a mini-example guide; the reporter says it also occurs on build-70.
Not provided report
Statusunknown
GPURX 9070 XT
CPUNot provided
DriverNot provided
Recorded FPSNot provided
Problems or notes: The issue's reproduction text says it has worse FPS than most other forks; no specific FPS or separate test details are given.
Not provided report
Statusnot booting
GPUAMD RX 6000 series or older
CPUNot provided
DriverNot provided
Recorded FPSNot provided
Problems or notes: User reports that the game crashes when the loading screen appears on Windows 10.
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-70 (1 record); previous: build-65 (0 records).
Fast Fusion Reported platform: unknown
| Build | Status | GPU / CPU | FPS | Details |
|---|---|---|---|---|
| release-binaries #80 | unknown | NVIDIA RTX 50 series / Not provided | 23–24 FPS | Open report |
release-binaries #80 report
Statusunknown
GPUNVIDIA RTX 50 series
CPUNot provided
DriverNot provided
Recorded FPS23–24 FPS
Problems or notes: User report: the game runs at a maximum of 23–24 FPS.
Related game issues
Compared with Previous Build
Fire Emblem Reported platform: unknown
| Build | Status | GPU / CPU | FPS | Details |
|---|---|---|---|---|
| build-70 | runs with issues | NVIDIA RTX 40 series / Not provided | Not provided | Open report |
build-70 report
Statusruns with issues
GPUNVIDIA RTX 40 series
CPUNot provided
DriverNot provided
Recorded FPSNot provided
Problems or notes: User reports that FMVs and pre-rendered videos are skipped; the opening cut-scene skips to the in-engine scene.
Related game issues
- [Crash] VK_ERROR_DEVICE_LOST, FEFW (Linux + AMD) (open)
- [GBug] Fire Emblem Fortunes Weave - FMVs Skipped/Do not play. (closed)
- Screen Shaking (Fire Emblem Fortune's Weave) (closed)
- Release note: User reports that Fire Emblem: Fortune's Weave crashes on Linux with VK_ERROR_DEVICE_LOST and a GPU reset on AMD Radeon GPUs.
- Release note: FMVs and pre-rendered videos are skipped, including the opening cut-scene.
Compared with Previous Build
Current: build-70 (1 record); previous: build-65 (0 records).
Fire Emblem Reported platform: Linux
| Build | Status | GPU / CPU | FPS | Details |
|---|---|---|---|---|
| build 93 (09b78bd) | not booting | AMD RX 9000 series; RX9070XT / R5 3600 | Not provided | Open report |
build 93 (09b78bd) report
Statusnot booting
GPUAMD RX 9000 series; RX9070XT
CPUR5 3600
DriverNot provided
Recorded FPSNot provided
Problems or notes: User reports that Fire Emblem: Fortune's Weave shows a black screen for several seconds, then crashes with VK_ERROR_DEVICE_LOST. The report says it does not happen in Windows on the same system. Other user reports describe the same failure on Linux with Radeon GPUs; Eglantine 212 reportedly boots the game with "use game's own dlss" disabled, but that is not a confirmed Lichii fix.
Related game issues
- [Crash] VK_ERROR_DEVICE_LOST, FEFW (Linux + AMD) (open)
- [GBug] Fire Emblem Fortunes Weave - FMVs Skipped/Do not play. (closed)
- Screen Shaking (Fire Emblem Fortune's Weave) (closed)
- Release note: User reports that Fire Emblem: Fortune's Weave crashes on Linux with VK_ERROR_DEVICE_LOST and a GPU reset on AMD Radeon GPUs.
- Release note: FMVs and pre-rendered videos are skipped, including the opening cut-scene.
Compared with Previous Build
green-hat child game Reported platform: unknown
| Build | Status | GPU / CPU | FPS | Details |
|---|---|---|---|---|
| build-93 | runs with issues | NVIDIA RTX 50 series / Not provided | Not provided | Open report |
build-93 report
Statusruns with issues
GPUNVIDIA RTX 50 series
CPUNot provided
DriverNot provided
Recorded FPSNot provided
Problems or notes: Many water temple rooms are not visible; walls are completely transparent.
Related game issues
Compared with Previous Build
Current: build-93 (1 record); previous: build-88 (0 records).
green-hat kid adventure Reported platform: Linux
| Build | Status | GPU / CPU | FPS | Details |
|---|---|---|---|---|
| 5a50f50 | runs with issues | AMD RX 7000 series / Not provided | Not provided | Open report |
5a50f50 report
Statusruns with issues
GPUAMD RX 7000 series
CPUNot provided
DriverNot provided
Recorded FPSNot provided
Problems or notes: User reports repeated crashes around Deku Tree; after the first crash, booting gets stuck compiling shaders until the shader cache is deleted. Another user says the problem occurs only with RADV and that the game runs too slowly to be playable on their NVIDIA GPU.
Related game issues
Compared with Previous Build
Hyrule Warriors Reported platform: unknown
| Build | Status | GPU / CPU | FPS | Details |
|---|---|---|---|---|
| 80 | runs with issues | NVIDIA RTX 40 series / Not provided | Not provided | Open report |
80 report
Statusruns with issues
GPUNVIDIA RTX 40 series
CPUNot provided
DriverNot provided
Recorded FPSNot provided
Problems or notes: In stages past the first one, gameplay displays a black screen while the UI remains visible; pausing shows the world rendered in the background. The reporter says it worked on older builds of eglantine.
Related game issues
Compared with Previous Build
Hyrule Warriors Reported platform: Windows 11
| Build | Status | GPU / CPU | FPS | Details |
|---|---|---|---|---|
| build 75 (c9ebb5c) | runs with issues | AMD RX 9000 series; RX 9060 XT 16GB / Not provided | Not provided | Open report |
build 75 (c9ebb5c) report
Statusruns with issues
GPUAMD RX 9000 series; RX 9060 XT 16GB
CPUNot provided
DriverNot provided
Recorded FPSNot provided
Problems or notes: An error appears after the cinematic and remains on screen, blocking the view.
Related game issues
Compared with Previous Build
Showing 11–20 of 175 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?
Wähle oben ein Spiel aus, um zu sehen, welche getesteten Builds zum Download verfügbar sind. Bis dahin kannst du den neuesten veröffentlichten Build verwenden und seine Release-Hinweise lesen.
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.