Other / not listed
User reports a crash at the first cutscene and emulator shutdown after compiling existing shaders on reboot.
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-117
Published November 7, 2026
Ein Spiel finden
Nach kompatiblen Lichii-Spielen suchen
108 Einträge zu Spielen und Testumgebungen sowie 308 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 |
|---|---|---|---|---|
| build-70 | playable | Not provided / Not provided | Not provided | Open report |
| Not provided | runs with issues | Not provided / 9900X | Not provided | Open report |
| 31 | runs with issues | RX 6600 / i5-12400 | Not provided | Open report |
| Not provided | runs with issues | 5070ti / 9800x3d | Not provided | Open report |
| 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 |
build-70 report
Statusplayable
GPUNot provided
CPUNot provided
DriverNot provided
Recorded FPSNot provided
Problems or notes: Runs well, though not at a locked 60 fps.
Not provided report
Statusruns with issues
GPUNot provided
CPU9900X
Driver615.74
Recorded FPSNot provided
Problems or notes: Purple screen when entering the game.
31 report
Statusruns with issues
GPURX 6600
CPUi5-12400
DriverNot provided
Recorded FPSNot provided
Problems or notes: Crashes when loading after the main menu. A commenter speculated that the issue involved shader cache; this was not confirmed.
Not provided report
Statusruns with issues
GPU5070ti
CPU9800x3d
Driver621.01
Recorded FPSNot provided
Problems or notes: The DK character appears all black during the banana-collection cutscene, then returns to normal. The reporter said the issue persisted when retested on build-70.
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 what should be a mini-example guide; the reporter says the issue 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] (open)
- [Crash] Bananza runs at ~57 fps then aborts silently, 0xC0000409 at +0x2ecd3bd (closed)
- Black DK when finding banana (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: Crashes after the continue-game loading screen.
- Release note: On build 70 (286117c), the MSVC package reportedly aborted after about 133.8 seconds of gameplay with 0xC0000409; the MinGW PGO package reportedly aborted on the intro screen with the same offset.
- Release note: DK appears all black during the cutscene when finding or collecting a banana, then returns to normal.
- 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: A VP9 video reaching end of stream triggers error 2111-3604 and freezes emulation; the video panel appears as a solid yellow box in stable-1.0.0.
- Release note: User reports the game is locked at 20 FPS, including menus and title screen, on Windows 11.
- Release note: Crashes when loading after the main menu on build 31.
- Release note: User reports the picture is covered with artifacts, especially on shadows.
- Release note: A black rectangle appears in what should be a mini-example guide; the reporter says it also occurs 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.
- Release note: Purple screen after starting the game and entering it.
Compared with Previous Build
Current: build-70 (2 records); previous: build-65 (0 records).
Donkey Kong Bananza Reported platform: Windows x86_64
| Build | Status | GPU / CPU | FPS | Details |
|---|---|---|---|---|
| nx2-20261031 | boots | Not provided / Not provided | Not provided | Open report |
nx2-20261031 report
Statusboots
GPUNot provided
CPUNot provided
DriverNot provided
Recorded FPSNot provided
Problems or notes: Completed a 180-second GUI check; long-term memory stability and broader game compatibility remain unverified.
Related game issues
- [Crash] (open)
- [Crash] Bananza runs at ~57 fps then aborts silently, 0xC0000409 at +0x2ecd3bd (closed)
- Black DK when finding banana (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: Crashes after the continue-game loading screen.
- Release note: On build 70 (286117c), the MSVC package reportedly aborted after about 133.8 seconds of gameplay with 0xC0000409; the MinGW PGO package reportedly aborted on the intro screen with the same offset.
- Release note: DK appears all black during the cutscene when finding or collecting a banana, then returns to normal.
- 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: A VP9 video reaching end of stream triggers error 2111-3604 and freezes emulation; the video panel appears as a solid yellow box in stable-1.0.0.
- Release note: User reports the game is locked at 20 FPS, including menus and title screen, on Windows 11.
- Release note: Crashes when loading after the main menu on build 31.
- Release note: User reports the picture is covered with artifacts, especially on shadows.
- Release note: A black rectangle appears in what should be a mini-example guide; the reporter says it also occurs 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.
- Release note: Purple screen after starting the game and entering it.
Compared with Previous Build
Fast Fusion Reported platform: Windows 11
| 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 reports that 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: A user reported that Fortunes Weave skips pre-rendered videos, including the opening cut-scene, and proceeds to the in-engine scene.
Related game issues
- DLSS does not work in FE Fortune's Weave - no Game DLSS Network detection (open)
- [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: A user reports that DLSS replacement does not detect the game's DLSS evaluation in Fire Emblem: Fortune's Weave: no Game DLSS network or NVIDIA DLSS (Streamline) line appears, while guest tensor operations run on cooperative matrices and GPU usage is high.
- Release note: On Linux with AMD graphics, Fire Emblem: Fortune's Weave can crash after a black screen with VK_ERROR_DEVICE_LOST and a GPU reset.
- Release note: A user reported that Fortunes Weave skips pre-rendered videos, including the opening cut-scene.
- Release note: Screen and camera shaking during play on build 65.
Compared with Previous Build
Current: build-70 (1 record); previous: build-65 (1 record).
Showing 11–20 of 308 reports
Known issues from Lichii sources
Known Game Issues
Other / not listed
Much of Gerudo does not render correctly, appearing like the skybox; resetting shaders reportedly changes it to physical forms and shapes with skybox textures.
The Legend of Zelda: Ocarina of Time Remake
User reports missing geometry, walls, buildings, and caves in the Great Deku Tree on a GTX 1070 Ti; the issue worsens deeper into the area.
Ocarina of Time
User reported sky-coloured holes in distant mountains of Hyrule Field on nx2 a7a28175 (same content as build-93) + local patches; a later user comment says they could no longer reproduce them on a newer local build.
Zelda Ocarina Of Time Remake
User reports excessive bloom outside the Great Deku Tree and invisible boxes and walls inside it.
The Legend of Zelda: Ocarina of Time Remake
Crashes after the intro sequence on an AMD GPU; another report describes a persistent driver crash with an RX 9070 XT.
The Legend of Zelda: Ocarina of Time (Switch 2)
Heavy stuttering during shader compilation, sometimes dropping to 0 FPS, with poor reported performance.
The Legend of Zelda: Ocarina of Time (Switch 2)
On Radeon RX 580 (Polaris / GCN4), the game hangs at 0 FPS with a black screen while building compute pipelines as the intro video starts.
The Legend of Zelda: Ocarina of Time
A commenter reports subsequent boots hang at Loading Shaders 25 / 27 with use_disk_shader_cache = true.
Recorded fix: Delete cache/shader/0400486024dec000 and set use_disk_shader_cache = false.
The Legend of Zelda: Ocarina of Time
A commenter reports a black screen after the intro on AMD, attributed in the comment to rejection of the game's 1080p upscaler shader.
Showing 221–230 of 361 issues
Aktuelle Release-Hinweise
Kompatibilitätsänderungen in den neuesten Builds
Build build-117 · Ocarina of Time
Fixed a crash during shader building on Windows drivers for RX 6000 (RDNA2), RX 5000 (RDNA1), Vega, and Polaris cards. The faster matrix path now runs only on RDNA3 and newer.
Build build-116 · Zelda: Ocarina of Time
Ocarina of Time is described as very stable; foliage and Hyrule Field grass rendering are fixed, and many users get 60+ fps.
Build build-116 · Zelda: Ocarina of Time
NVIDIA DLSS Super Resolution can replace the game's own upscaler on RTX cards; the setting is experimental.
Build build-116 · Zelda: Ocarina of Time
A new option turns off the game's sharpening anti-aliasing; the default Game setting behaves as before, and DLSS takes priority if both are enabled.
Build build-116 · Mario Tennis Fever
The game runs fully at 60 fps, and texture glitches are fixed.
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-117. 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.