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-83 | runs with issues | AMD RX 9000 series / Not provided | Not provided | Open report |
Problems or notes: The emulator crashes after 5 to 10 minutes of gameplay.
Current: build-83 (1 record); previous: build-75 (0 records).
| Build | Status | GPU / CPU | FPS | Details |
|---|---|---|---|---|
| build-83 | not booting | Other / Not provided | Not provided | Open report |
Problems or notes: User reports that the game blacks out when booted. They identify this as a regression from build 75.
Current: build-83 (1 record); previous: build-75 (0 records).
| Build | Status | GPU / CPU | FPS | Details |
|---|---|---|---|---|
| build-83 | runs with issues | RTX 4070 SUPER 12 GB / i5-14600KF | 30–60 FPS | Open report |
Problems or notes: The commenter reports slow motion at about 30 fps and says GPU Mode: Fast reached 60 fps in most areas. They also report shader-build stutter on new content, fewer visual artifacts in a local build, and cache-warming stutter after updates.
Current: build-83 (1 record); previous: build-75 (0 records).
| Build | Status | GPU / CPU | FPS | Details |
|---|---|---|---|---|
| build-83 | runs with issues | RTX 3060 12 GB / i5-11400 | Not provided | Open report |
Problems or notes: The user reports audio/video desynchronization. The AV1 title and intro movies are reported below 60 FPS, and gameplay in Kokiri Forest is reported at about 15 FPS on build 83 versus about 24 FPS on build 80. The user notes that the build-80 movie ran at about 24 FPS and the build-83 movie at about 20–36 FPS.
Current: build-83 (1 record); previous: build-75 (0 records).
Also listed as: MKW
| Build | Status | GPU / CPU | FPS | Details |
|---|---|---|---|---|
| build-83 | unknown | RX 9070 XT / Not provided | Not provided | Open report |
Problems or notes: A user included Mario Kart World among games where they reported early crashes without EDEN_NX2_NO_MESH=1 and no early crashes with it; this is a user testimonial, not a verified result.
Current: build-83 (1 record); previous: build-75 (0 records).
| Build | Status | GPU / CPU | FPS | Details |
|---|---|---|---|---|
| build-83 | runs with issues | intel uhd graphics / intel core i5 gen 13th | Not provided | Open report |
Problems or notes: The user reports missing textures and buggy visuals after boot, occasional crashes during startup, and crashes during Grand Prix races. A comment says the issue is still present in build-88.
Current: build-83 (1 record); previous: build-75 (0 records).
| Build | Status | GPU / CPU | FPS | Details |
|---|---|---|---|---|
| build-83 | playable | RTX 4070 Ti / Ryzen 7 7700X | Not provided | Open report |
Problems or notes: In a tested docked 2x gameplay run, haze was gone and Link and Kokiri Forest were clearly visible without shader rejections. FPS was described as low, with no value stated.
From build-75 to build-83: follow the gameplay changes described for these two builds.
Before: Missing vegetation and incorrect material data; affected lighting and colours; a glowing doorway; one-frame white flashes; and on AMD, shaders could produce a black 3D scene.
After: Additional shader pointers and storage-buffer bindings, corrected buffer tracking and mesh-shader register handling, fixed occlusion-query and nested-return handling, and added the Max Resolution add-on and frame-ahead presentation tuning.
build-75 → build-83
| Build | Status | GPU / CPU | FPS | Details |
|---|---|---|---|---|
| build-83 | runs with issues | NVIDIA RTX 50 series / Not provided | Not provided | Open report |
Problems or notes: Crashes after about 15 to 20 minutes. The reporter states they have 16GB of RAM.
Current: build-83 (1 record); previous: build-75 (1 record).
Also listed as: green-hat kid adventure, green-hat kid game
| Build | Status | GPU / CPU | FPS | Details |
|---|---|---|---|---|
| build-83 | unknown | RX 9070 XT / Not provided | Not provided | Open report |
Problems or notes: A user reported early crashes without EDEN_NX2_NO_MESH=1 and no early crashes with it across more than one game and emulator; this is a user testimonial, not a verified result.
Current: build-83 (1 record); previous: build-75 (0 records).
Also listed as: Ocarina of Time, Zelda: Ocarina of Time, OoT, Zelda OoT, TLoZ: OoT
| Build | Status | GPU / CPU | FPS | Details |
|---|---|---|---|---|
| build-83 | runs with issues | AMD RX 9000 series / Not provided | Not provided | Open report |
Problems or notes: The issue reporter says the game reaches the end of the introductory cutscene, turns black while loading gameplay, then crashes with an AMD TDR. Comments report similar crashes on RX 9060 XT, RX 9070/9070 XT, and RX 7900 XTX. One user says EDEN_NX2_NO_MESH=1 stops the Windows driver crash but leaves the game black-screened or crashing while loading gameplay. Reports on Build 93 conflict: one user reports an early GPU crash without the variable, another reports playing through Kokiri Forest without crashes, and another says the issue remains and visual bugs occur during gameplay.
From build-75 to build-83: follow the gameplay changes described for these two builds.
Before: Missing vegetation and incorrect material data; affected lighting and colours; a glowing doorway; one-frame white flashes; and on AMD, shaders could produce a black 3D scene.
After: Additional shader pointers and storage-buffer bindings, corrected buffer tracking and mesh-shader register handling, fixed occlusion-query and nested-return handling, and added the Max Resolution add-on and frame-ahead presentation tuning.
build-75 → build-83
Showing 1–10 of 15 reports
Known issues from Lichii sources
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.
With Dual Joy-Cons, the game remains on the “Playing with 1 Joy-Con” screen and reports a lost connection, preventing a two-player motion game from starting. The issue reporter's log includes an unsupported controller type disconnection and a Joy-Con sub-command timeout.
Walls and objects are missing/not rendered inside the Deku tree.
The official PGO artifact of build-80 / nx2-latest crashed in dynarmic with Unhandled SIGSEGV after 2-10 minutes on the reporting machine; another report found a PGO AppImage produced audio but no video output.
White flashes were reported before PR #345 in the Deku Tree interior; the sky/lighting colour result from a separate misaligned 64/128-bit SSBO split fix was not verified.
Recorded fix: Use a local non-PGO build with PR #345 merged; the reporter confirmed white flashes were gone after several minutes in the Deku Tree interior.
In a Windows AMD-driver follow-up on Frizti v3, performance was about 20 fps in a busy view and about 60 fps looking at the floor; the reporter said keeping float16 on improved the busy-view result from about 20 to 24-25 fps.
Recorded fix: The reporter found that keeping float16 on improved the measured busy-view performance; this is a user-reported workaround.
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.
On a GPU without VK_EXT_mesh_shader, mesh-shader draws may be skipped, resulting in missing scene geometry. The reported log labels skipped draws as "no pipeline" and caps the warning entries at 64.
Plants and bushes in the Castle appear dead up close, while bushes render correctly at a distance.
On Linux, the game froze near the title screen, followed by pixel artefacts and a system crash.
Recorded fix: The user reported that EDEN_NX2_NO_MESH=1 allowed the game to reach the menus, but Grand Prix did not start successfully.
Showing 181–190 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
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
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.