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 |
|---|---|---|---|---|
| 95 | runs with issues | NVIDIA RTX 30 series or older; 3080TI / 9800X3D | ?–60 FPS | Open report |
Problems or notes: While walking or spinning, the “Building X Shaders” status message coincides with freezing or stuttering and drops to 15 or fewer FPS; performance is reported as 40–60 FPS otherwise. The commenter reports first-visit shader stutter.
Current: build-117 (1 record); previous: build-116 (0 records).
| Build | Status | GPU / CPU | FPS | Details |
|---|---|---|---|---|
| build-93 | runs with issues | Radeon 9060 XT / Ryzen 7700x | Not provided | Open report |
| nx2-build-95 (222877d) | runs with issues | RTX 5070 Ti / Not provided | Not provided | Open report |
Problems or notes: User reported an extremely bright sky obscuring visibility in open areas such as Hyrule Field. A comment attributed the white haze to light-volume probe data being read further into memory than was bound, and mentioned a separate NaN-safe min/max change that could spread bloom on AMD. The comment said these changes were not yet in a published release.
Problems or notes: User reports that preloaded pipelines were evicted after 9000 frames, leading to runtime pipeline rebuilds and stutter when moving into a new area.
Current: build-93 (1 record); previous: build-88 (0 records).
| Build | Status | GPU / CPU | FPS | Details |
|---|---|---|---|---|
| 95 | runs with issues | RTX2060 / Not provided | 15–22 FPS | Open report |
Problems or notes: The user reports delayed AV1 cinematics and audio playing faster. Normal gameplay is reported at about 15–22 FPS.
Also listed as: Ocarina of Time, Zelda: Ocarina of Time, OoT, Zelda OoT, TLoZ: OoT
| Build | Status | GPU / CPU | FPS | Details |
|---|---|---|---|---|
| build-117 | runs with issues | AMD RX 7000 series; RX 7800 XT (RDNA3) / Not provided | Not provided | Open report |
| build-117 | runs with issues | NVIDIA 4070 Super / AMD 9850x3d | 0–50 FPS | Open report |
| build-93 | runs with issues | AMD RX 9000 series / Not provided | Not provided | Open report |
| build-93 | runs with issues | RTX 3060 Ti / Intel Core i7-12700 | 19–31 FPS | Open report |
| build-93 | runs with issues | NVIDIA RTX 50 series; AMD RX 9060 XT 16gb graphics card / Not provided | Not provided | Open report |
| build-88 | runs with issues | 7800xt / Ryzen 7 5700X | Not provided | Open report |
Problems or notes: In the Bombchu Bowling Alley, stones along the wall and ovens flash pink, yellow, red, or black by day; the sign shows garbage, noise, and fragments of another image. The graphics look correct at night after leaving and returning. The issue remains in official build-117. The Royal Family's Tomb red line is separately reported fixed by #722.
Problems or notes: The issue author reports major stuttering and shader building around Hyrule Castle town, making play unworkable. They say visuals looked good and FPS seemed more stable in previous builds. In comments, users report shader loading/building stutter and repeated shader rebuilding when revisiting areas. One commenter says enabling “switch 2 draws with unbuilt pipelines to skip” fixed the stutter but caused graphical and lighting issues. Another says deleting the shader cache and letting it rebuild helped, but performance remained slower than build 93. A commenter reports build 93 had better FPS but worse visuals than build 117.
Problems or notes: The emulator closes when loading Hyrule Market after the user exits Kokiri Forest and enters Hyrule Castle.
Problems or notes: About 31 FPS on average, down to about 19 FPS in crowded scenes, with short freezes when attacking.
Problems or notes: The user reports textures not working properly, slow frame rate, and a shield glitch. They also report that trying a '.dat' file did not work. The issue body gives conflicting GPU details.
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.
Current: build-117 (2 records); previous: build-116 (0 records).
Showing 31–40 of 194 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
build-117 · Veröffentlicht am November 7, 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.