Spielekompatibilität des Lichii Emulators

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 (1 record); previous: build-65 (1 record).

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).

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).

Related game issues

• Release note: Some races still stall while shaders build.

Compared with Previous Build

Current: build-70 (1 record); previous: build-65 (0 records).

Related game issues

• [Crash] GPU crash on mesh shader building, fixed in other fork (open)
• [Crash] Linux RADV, Navi 33 (Steam Machine): GPU reset from mesh draws in OoT, "Illegal opcode in command stream", also MKW on stock build 88 (open)
• [Perf] Mario Kart World (0400C3F00006E000): severe 3D in-game performance drop from build 93 (40-54 FPS) to build 95 (17-23 FPS) (open)
• [VBug] Switch Pro Controller causes desktop input flood / mouse click freeze on Windows (open)
• [Crash] RX9070XT, SteamOS (closed)
• [VBug] MKW 1.8.0 no render no textures (intel uhd graphics) (open)
• [Crash] (open)
• crash or infinite loading when use windows 10 (any game) (closed)
• GPU crash (closed)
• [GBug] Mario Kart World – Severe Performance Regression in Build 75 (closed)
• [VBug] Build 93 finaly has no major visual errors but has poor performance 9070xt (open)
• graphics memory leak in MKW (closed)
• Mario kart Crash on SplashScreen (closed)
• [VBug] playing mario kart world but textures wont load. also crashes when playing the grand prix race (open)
• [Crash] macOS MKW Loading Splash animation shows, but crashes after. (closed)
• [MKW 1.8.0] Grand Prix crash during course selection, but excellent Free Roam performance on 16 GB RAM (Build 31) (closed)
• Release note: Building mesh shaders can cause a hard crash on AMD 7000 series and some other AMD cards; on Linux this may freeze the system, while on Windows it crashes the emulator.
• Release note: A user report says stock build 88 reset the GPU about 25 seconds after launch on Linux RADV.
• Release note: User reports 17–23.8 FPS in 3D races on build-95, compared with 40.0–54.1 FPS on build-93 under the same reported test conditions.
• Release note: On Windows 11, connecting an official Nintendo Switch Pro Controller while Lichii is open reportedly floods the host OS with phantom inputs, making desktop mouse clicks unresponsive and keyboard typing erratic. Unplugging the controller reportedly restores normal input.
• Release note: On Linux, the game froze near the title screen, followed by pixel artefacts and a system crash.
• Release note: On Intel UHD integrated graphics, the game reportedly boots with no rendering or textures; later, some textures appeared gray. The reporter also reports crashes when teleporting during free roam.
• Release note: Crash reported after joining the game with OpenGL.
• Release note: A user reports a crash after brief rendering while loading on Windows 10.
• Release note: A user reported GPU crashes when booting on Bazzite with Mesa 26.2.4; the report was later said to concern an older nx2 build.
• Release note: A user reports severe performance regression after updating from Build 70 to Build 75 on Linux, with around 10 FPS on the title screen, barely reaching 15 FPS, constant stuttering, and RAM usage increasing nonstop.
• Release note: A commenter reports darker, heavily shaded characters and a frame-rate drop of about 5 to 10 FPS in builds after 72, and associates the onset in their tests with commit 3aa89d1c.
• Release note: Poor frame rates; the issue says performance is worse than on most other forks.
• Release note: A user reported rapidly increasing VRAM usage after starting the game, followed by low framerate.
• Release note: Crashes while loading before the main menu; user comments also report session or emulator crashes.
• Release note: The user reports missing textures and buggy visuals, occasional startup crashes, and crashes during Grand Prix races on Intel integrated graphics.
• Release note: On macOS, crashes after the loading splash in tag/build-65.
• Release note: The emulator crashed/exited while selecting a course in Grand Prix mode. The user had not confirmed reproducibility or whether Process Lasso contributed.

Compared with Previous Build

Current: build-70 (1 record); previous: build-65 (0 records).

Related game issues

• [GBug] StarFox: nx2_sysmix accepts a constant 70.32% of mixer output, so audio plays as "robot voice" (open)
• [Crash] StarFox, Device loss occurred! (closed)
• [GBug] Starfox - Unmapped write64 error spam in console (closed)
• [Crash] Starfox is crashing right before the training mission begins. I got it to pass one time havent been able to get it work again. (closed)
• Release note: On RTX 50-series GPUs, the GPU device can still be lost after a scene change.
• Release note: Gameplay is capped at about 30 fps, even though the game asks for 60.
• Release note: On RTX 50-series GPUs (5070 Ti, 5090), the GPU device can be lost shortly after a scene change.
• Release note: User reports heavily distorted speech, music, and effects (“robot voice”) on build 70. Comments clarify that the approximately 0.7032 accepted/copied ratio reflects retries rather than lost samples; possible causes discussed include emulated time running ahead of wall time or slow host audio draining, but the cause is not confirmed.
• Release note: A user reports the emulator closes about a minute after gameplay begins on Build 75 with an NVIDIA RTX 50 series GPU and Windows 11.
• Release note: Repeated Unmapped Write64 errors while the game is running, possible audio popping, and an emulation crash when closing the game, as reported by a user.
• Release note: User reports crashes before the training mission begins; another user reports crashes during the campaign after skipping training.

Compared with Previous Build

Current: build-70 (1 record); previous: build-65 (0 records).

Related game issues

• [GBug] Yoshi and the Mysterious Book (0400245021D2C000): HUD renders, 3D scene black — stage 1 vertex program is fetched as all zeros (open)
• Release note: Some textures are still black, and the game can crash later in play.
• Release note: The game reaches responsive gameplay with a correctly rendered HUD, but the 3D scene is black. Graphics programs are rejected and draws are skipped.

Compared with Previous Build

Current: build-70 (1 record); previous: build-65 (0 records).