Spielekompatibilität
Du hast ein bestimmtes Spiel im Sinn? Erfahre, wie es mit Lichii läuft, welche Probleme bekannt sind und welchen Build du ausprobieren kannst.
Ein Spiel finden
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
Recorded performance
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.
| 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 |
Problems or notes: Crashes after the continue-game loading screen.
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.
Problems or notes: User reports a crash when loading a save.
Current: build-117 (1 record); previous: build-116 (0 records).
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 |
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.
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.
Problems or notes: Terrain/world renders solid white while the HUD and characters still draw.
Problems or notes: Not 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.
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.
Current: build-93 (1 record); previous: build-88 (0 records).
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 |
Problems or notes: User reports visual artifacts, especially on shadows.
Current: build-70 (2 records); previous: build-65 (0 records).
Showing 1–10 of 18 reports
Known issues from Lichii sources
When fastmem could not be created, guest code ran about 1.4x slower; Kokiri Forest ran at 22.2–26.6 FPS rather than 28.5–33.8 FPS. The report attributes the slow boots to failure to allocate 14336 MiB of backing memory.
Recorded fix: Change #645 retries the section after a private commit that grows the page file; in eight back-to-back boots, all three initial failures recovered on the second attempt and none ran slowly.
Graphics fail to load in the Water Temple; a commenter describes the area as unplayable.
Recorded fix: A commenter reports resolving the issue by using a NUP containing the missing texture files, described as 23.8 GB rather than 23.3 GB.
Many Water Temple rooms are invisible, with transparent walls. A comment attributes this to a damaged texture file in the game dump; another user reports the issue was resolved by making a fresh dump with a NUP with a higher file size.
On AMD Windows proprietary drivers, older builds can lose the GPU device when gameplay or a save starts; build-83 and build-88 reports include this problem.
Recorded fix: A Windows RX 9060 XT report found the issue absent in build-93. A Windows RX 7900 XTX report also found it absent in the CI build at 18cfe85.
On AMD RADV Mesa 26.2.4, task/mesh shader use can hang the GPU and cause device loss during 3D gameplay.
Recorded fix: The reporter found that updating to Mesa RADV 26.2.6 avoided the hang on the same GPU with the same build. If using a distrobox in gamescope gaming mode, the reporter says to install the gamescope package in the container so its Vulkan WSI layer is present.
On build-95, the user reports draws held while unbuilt pipelines are being built, causing multi-second stalls, even with async shaders enabled.
The user reports that a fresh build-95 config starts with slow defaults, including High GPU accuracy, asynchronous shaders off, async presentation off, Handheld mode, 4 GB memory layout, and CPU NVDEC; the game ran at 10–15 fps with stalls up to 8.9 s and blurry/pixelated Handheld resolution.
Recorded fix: The user reports that writing the six listed settings before launch helped: gpu_accuracy=0, use_asynchronous_shaders=true, async_presentation=true, nvdec_emulation=2, memory_layout_mode=2, and use_docked_mode=1; set each key's \default= line to false as well.
User reports a black-screen stall after the first AV1 frame with async GPU emulation enabled on AMD Radeon RX 6800 XT; with async GPU emulation disabled, the game later froze during gameplay.
Users report failure to start, black screens with 0 FPS, or emulator crashes in builds 88–95, including a build-95 Linux report with an unhandled SIGSEGV and null-pointer dereference. The comments caution that the reports may have different causes.
The user reports performance remaining at 20 FPS with music glitches on macOS.
Showing 121–130 of 361 issues
Aktuelle Release-Hinweise
Build build-117 · Ocarina of Time
Build build-116 · Zelda: Ocarina of Time
Build build-116 · Zelda: Ocarina of Time
Build build-116 · Zelda: Ocarina of Time
Build build-116 · Mario Tennis Fever
Den passenden Build finden
build-70 · Veröffentlicht am November 4, 2026
12 veröffentlichte Downloaddateien für diesen Build.
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
Setze die Filter für Spiel, Status, GPU und Build und kopiere anschließend die Seitenadresse. Ein direkter Link zum Spiel öffnet dessen Berichtskarte.
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.
Treiberversion, Grafikeinstellungen, CPU-Auslastung und die getestete Spielszene können das Ergebnis beeinflussen. Vergleiche diese Details, bevor du deine Konfiguration änderst.
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.