Yoshi and the Mysterious Book (demo)
The game reaches responsive gameplay with a correctly rendered HUD, but the 3D scene is black. Graphics programs are rejected and draws are skipped.
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: Windows 11
| Build | Status | GPU / CPU | FPS | Details |
|---|---|---|---|---|
| build-117 | runs with issues | AMD RX 6000 series or older / Not provided | Not provided | Open report |
| build-88 | unknown | RTX 4070 / i7 13700k | 20 FPS | Open report |
| latest prelease build 93 | not booting | AMD RX 6000 series or older / Not provided | Not provided | Open report |
build-117 report
Statusruns with issues
GPUAMD RX 6000 series or older
CPUNot provided
DriverNot provided
Recorded FPSNot provided
Problems or notes: Crashes after the continue-game loading screen.
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.
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] (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-117 (1 record); previous: build-116 (0 records).
Donkey Kong Bananza Reported platform: Windows
Also listed as: dkb
| Build | Status | GPU / CPU | FPS | Details |
|---|---|---|---|---|
| build-93 | runs with issues | NVIDIA RTX 50 series / Not provided | 20–60 FPS | Open report |
| build-75 | runs with issues | NVIDIA GeForce RTX 4060 Laptop, 8 GB / Intel Core i7-13650HX | 20 FPS | Open report |
| build-70 | runs with issues | NVIDIA GeForce RTX 4060 Laptop, 8 GB / Intel Core i7-13650HX | 20 FPS | Open report |
| build-65 | playable | NVIDIA GeForce RTX 4060 Laptop, 8 GB / Intel Core i7-13650HX | 10–30 FPS | Open report |
| Eglantine NX2 Windows build 2026-10-31 (1.0.0-stable-1.0.0) | runs with issues | AMD Radeon RX 7600 8 GB / AMD Ryzen 7 7800X3D | Not provided | Open report |
| build 70 (286117c) | runs with issues | AMD RX 6000 series or older / Not provided | 57 FPS | Open report |
build-93 report
Statusruns with issues
GPUNVIDIA RTX 50 series
CPUNot provided
DriverNot provided
Recorded FPS20–60 FPS
Problems or notes: User reports FPS fluctuating approximately between 20 and 60, frequent periods around 30, and 25–28 FPS in the Dragon Layer. With a GameSir G7 Pro, controller rumble is sometimes excessive, occurs without an obvious in-game trigger, and sometimes continues longer than expected.
build-75 report
Statusruns with issues
GPUNVIDIA GeForce RTX 4060 Laptop, 8 GB
CPUIntel Core i7-13650HX
Driver32.0.16.2101
Recorded FPS20 FPS
Problems or notes: Terrain/world renders solid white while the HUD and characters still draw. With EDEN_NX2_RESETFIX=0, the ground renders black without texture or lighting.
build-70 report
Statusruns with issues
GPUNVIDIA GeForce RTX 4060 Laptop, 8 GB
CPUIntel Core i7-13650HX
Driver32.0.16.2101
Recorded FPS20 FPS
Problems or notes: Terrain/world renders solid white while the HUD and characters still draw.
build-65 report
Statusplayable
GPUNVIDIA GeForce RTX 4060 Laptop, 8 GB
CPUIntel Core i7-13650HX
Driver32.0.16.2101
Recorded FPS10–30 FPS
Problems or notes: Not provided
Eglantine NX2 Windows build 2026-10-31 (1.0.0-stable-1.0.0) report
Statusruns with issues
GPUAMD Radeon RX 7600 8 GB
CPUAMD Ryzen 7 7800X3D
DriverAMD proprietary Vulkan driver 2.0.395
Recorded FPSNot provided
Problems or notes: After gameplay starts, a 960x540 VP9 video panel appears as a solid yellow box in stable-1.0.0. When the video reaches end of stream, the game aborts with 2111-3604 and emulation freezes. The report says this reproduces in Eglantine NX2 Windows build 2026-10-31 (1.0.0-stable-1.0.0) and PokeDinner fork 2.1.0 (007f3ac08d). Without EDEN_NX2_TENSOR=1, two compute shaders are rejected and the 3D scene remains flat lavender with only the HUD visible. A later user comment reports that the game played past the tutorial video without the abort.
build 70 (286117c) report
Statusruns with issues
GPUAMD RX 6000 series or older
CPUNot provided
DriverNot provided
Recorded FPS57 FPS
Problems or notes: On Windows 11 with Vulkan, the game reportedly held about 57 FPS during gameplay, then the process aborted after 133.8 seconds with 0xC0000409 at lichii.exe+0x2ecd3bd. With the MinGW PGO zip of the same build, it reportedly died on the intro screen seconds after launch.
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-93 (1 record); previous: build-88 (0 records).
Donkey Kong Bananza Reported platform: unknown
Also listed as: dkb
| 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 visual artifacts, especially on shadows.
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).
Showing 1–10 of 308 reports
Known issues from Lichii sources
Known Game Issues
Other / not listed
Game freezes when the user tries the Ocarina at the Temple of Time.
Other / not listed
User reports a crash when booting the game in build 88 after it worked in build 75.
Ocarina of Time
AMD GPUs may show a black screen or crash the graphics driver after loading, the intro, or a cutscene.
Ocarina of Time
On a local nx2 build, white or yellow haze outdoors and black water or foliage after an area change were reported as remaining graphics issues.
The Legend of Zelda: Ocarina of Time Remake
A user reports that the game speeds up when Dynamic FPS reaches 30 FPS, while running at normal speed around 20 FPS.
OoT
On build-83, repeated graphics-pipeline builds on the GPU thread across boots cause a visible gameplay hitch.
Recorded fix: A user reported that build-88 (MSVC), which includes #194, fixed the issue for them; this is not a maintainer-confirmed fix.
Ocarina of Time
A user reported repeated GPU-thread pipeline builds and tessellation-related warnings in one Linux session; recurrence across launches was not confirmed.
The Legend of Zelda: Ocarina of Time (Switch 2)
On macOS arm64 with Vulkan via MoltenVK, the Metal device may be lost with a GPU address fault or device error during intro video playback, or the GPU thread may hang at the video-to-gameplay transition in fence waiting or buffer download.
The Legend of Zelda: Ocarina of Time (Switch 2)
On Apple GPUs, attachment-less framebuffer draws using a 32768×32768 surface clip can exceed device framebuffer limits and cause GPU failure/device loss. A user also reports a stream-buffer constant-buffer tail read issue on Metal.
Showing 281–290 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.