After: Dynamic FPS mod enabled by default; Max Resolution remains a separate Add-On.
build-83 → build-88
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-88 | unknown | RTX 4070 / i7 13700k | 20 FPS | Open report |
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.
Current: build-88 (1 record); previous: build-83 (0 records).
| Build | Status | GPU / CPU | FPS | Details |
|---|---|---|---|---|
| build-88 | runs with issues | nvidia rtx 40 series / Not provided | Not provided | Open report |
Problems or notes: A commenter reports the same bug at the start.
Current: build-88 (1 record); previous: build-83 (0 records).
Also listed as: MKW
| Build | Status | GPU / CPU | FPS | Details |
|---|---|---|---|---|
| build-88 | not booting | AMD RX 7000 series / AMD Custom CPU 1772 | Not provided | Open report |
Problems or notes: One user report says the GPU reset about 25 seconds after launch on stock build 88, before gameplay was reported. The setup included an audio-only LayeredFS mod, a thread-pinning script, EDEN_NX2_AUTO_STUB=1, and GPU accuracy High.
Current: build-88 (1 record); previous: build-83 (1 record).
| Build | Status | GPU / CPU | FPS | Details |
|---|---|---|---|---|
| build-88 | unknown | Other / Not provided | Not provided | Open report |
| build-88 | unknown | Other / Not provided | 20 FPS | Open report |
Problems or notes: User reports a crash when booting the game.
Problems or notes: The issue title reports 20 fps.
Current: build-88 (2 records); previous: build-83 (0 records).
Also listed as: green-hat kid adventure, green-hat kid game
| Build | Status | GPU / CPU | FPS | Details |
|---|---|---|---|---|
| build-88 | runs with issues | RX 9070 XT / Not provided | Not provided | Open report |
Problems or notes: One user reported GPU/display blackout and VK_ERROR_DEVICE_LOST when entering gameplay without EDEN_NX2_NO_MESH=1; with that option, gameplay ran for at least five minutes. The report does not establish long-term stability or the precise failing shader or command.
Current: build-88 (1 record); previous: build-83 (1 record).
| Build | Status | GPU / CPU | FPS | Details |
|---|---|---|---|---|
| build-88 | runs with issues | Intel(R) Iris(R) Xe Graphics / 12th Gen Intel(R) Core(TM) i7-1255U | Not provided | Open report |
Problems or notes: Only character outlines and UI are visible; the user reports a black-screen-like graphics issue.
Current: build-88 (1 record); previous: build-83 (0 records).
Also listed as: Ocarina of Time, Zelda: Ocarina of Time, OoT, Zelda OoT, TLoZ: OoT
| Build | Status | GPU / CPU | FPS | Details |
|---|---|---|---|---|
| build-88 | runs with issues | 7800xt / Ryzen 7 5700X | Not provided | Open report |
| build-88 | not booting | AMD Radeon RX 9070 XT / AMD Ryzen 7 7800X3D | Not provided | Open report |
| build-88 | runs with issues | AMD Radeon RX 9070 XT 16GB / AMD Ryzen 7 7800X3D | Not provided | Open report |
Problems or notes: A commenter using CachyOS and Linux 7.2.9-2-cachyos reports severe audio/video delay during the initial cutscene, then black screens on both monitors and a GPU crash and reset when character control begins. They report the same issue with a fork.
Problems or notes: User reports the logo, text, and UI are visible but the 3D environment remains black; audio continues, and the AMD driver sometimes times out or crashes. The issue reportedly persists after updating or rolling back the driver and restarting.
Problems or notes: The game launches with logo, text, and UI visible, but the 3D environment remains black. Audio continues. AMD driver TDR errors or crashes are also reported.
From build-83 to build-88: follow the gameplay changes described for these two builds.
After: Dynamic FPS mod enabled by default; Max Resolution remains a separate Add-On.
build-83 → build-88
Showing 1–10 of 16 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.