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.
Also listed as: Ocarina of Time, OoT
| Build | Status | GPU / CPU | FPS | Details |
|---|---|---|---|---|
| Not provided | not booting | RX 5700 / Not provided | Not provided | Open report |
| nx2-build-88 (55532f2) | runs with issues | NVIDIA GeForce RTX 5060 (8 GB VRAM) / AMD Ryzen 5 5600G (6C/12T) | Not provided | Open report |
| nx2-build-93 | runs with issues | RTX 2060 6 GB / Xeon E5-1620 v3 (4C/8T) | Not provided | Open report |
| nx2-build-117 | runs with issues | AMD Radeon RX 580 8 GB (Polaris, GCN 4) / i3-8100 | Not provided | Open report |
| nx2-build-93 | runs with issues | AMD Radeon RX 6750 GRE 10GB (RDNA2) / Ryzen 5 5600 | Not provided | Open report |
| nx2-build-117 | runs with issues | NVIDIA RTX 40 series (RTX 4070 Ti Super) / Ryzen 7 9800X3D | Not provided | Open report |
Problems or notes: A commenter reports black 3D graphics with working UI and attributes this to a possible DemoteCombinationPass issue; this is a user-provided analysis, not a confirmed fix.
Problems or notes: In a 1h 49m gameplay session, the reporter observed severe 1.3–6.59 second freezes, continuous frame-time micro-stutters, repeated GPU-thread shader translation stalls, and 579,265+ synchronous OnCPURead waits. The session had 0 crashes. Vulkan, 1x, GPU Mode Accurate, Async GPU and async shader compilation enabled, and Enable Reactive Flushing enabled.
Problems or notes: A user follow-up reports FPS averages falling from 53 in the first 10-minute bucket to about 23 in the 80–90-minute bucket during a 98-minute session with Reactive Flushing enabled, alongside 365,889 OnCPURead events and stalls over 2 seconds. In additional roughly 100-minute sessions, OnCPURead growth occurred with Reactive Flushing both on and off; with it off, FPS averages were 16–33 after the first 10 minutes and stalls reached 12 seconds, with one around 49 seconds. The reporter notes the comparison is not conclusive.
Problems or notes: A user reports the AMD Vulkan driver faults with exception 0xc0000005 during compute-pipeline compilation. Two shader pipelines repeatedly fail to finish; the same was reproduced on nx2-build-95. OpenGL was also reported to fail because GLSL task and mesh programs are not implemented.
Problems or notes: On Vulkan, the AV1 intro audio plays and decoding starts, but no video image is presented; eight compute shaders fail with VK_ERROR_OUT_OF_HOST_MEMORY and the process eventually aborts with 0xc0000409. The issue says the same crash signature also occurred on nx2-build-88 and nx2-build-83 (MSVC).
Problems or notes: With Switch 2 draws with unbuilt pipelines set to Bounded and an 8 ms wait, the image washed out to white and orange and parts of the scene rendered as large flat polygons while pipelines were building. Switching to Wait produced a normal picture with the usual stutter while pipelines built.
Current: build-93 (1 record); previous: build-88 (2 records).
Also listed as: Ocarina of Time
| Build | Status | GPU / CPU | FPS | Details |
|---|---|---|---|---|
| Not provided | runs with issues | AMD RX 6900 XT (RDNA2) / i7-9700K | 18–30 FPS | Open report |
Problems or notes: The user reports a driver crash after starting a new game and skipping a cutscene. With a local build using EDEN_NX2_NOOPT_SHADERS=all, they report no crash during 40+ minutes of play in Kokiri Forest, Deku Tree, cutscenes, and save load. The same setup was CPU-bound at 18-30 fps in Kokiri Forest.
| Build | Status | GPU / CPU | FPS | Details |
|---|---|---|---|---|
| Lichii Development Build | 1.0.0-sharkiix-3.1.1 | runs with issues | AMD Radeon RX 6700 XT 12 GB (Navi 22) / AMD Ryzen 5 5600G (6C/12T, Zen 3) | 20 FPS | Open report |
Problems or notes: Menus and pause screen run at 60 FPS, but gameplay is around 20 FPS with audio crackling below full speed. Forcing full GPU clock and performance EPP made gameplay smoother but did not raise the frame rate. The report attributes the limitation to synchronization between emulator threads. On Windows with the same PC, only subtitles rendered. The report also describes a device loss after about nine minutes with Mesa 25.0.7 and kernel 6.12.115; it was not seen again after updating to Mesa 26.1.6 and kernel 7.2.11.
Also listed as: OoT
| Build | Status | GPU / CPU | FPS | Details |
|---|---|---|---|---|
| Not provided | runs with issues | Nvidia RTX 4070 SUPER / Not provided | Not provided | Open report |
Problems or notes: The 3D scene is black while subtitles and audio are present.
Also listed as: Ocarina of Time
| Build | Status | GPU / CPU | FPS | Details |
|---|---|---|---|---|
| Not provided | runs with issues | RX 6650 XT (RDNA2) / i5-10400F | 16–27 FPS | Open report |
Problems or notes: In a fork build with the two compute shaders built unoptimized, the intro played and the game reached Kokiri Forest; cutscenes ran at about 25–27 FPS. With `EDEN_NX2_NOOPT_SHADERS=all`, performance dropped to about 16–17 FPS. In another setup, asynchronous shader compilation was associated with a black screen with audio or remaining at Loading Shaders at 0 FPS; the reporter did not wait long enough to determine whether it would eventually finish. A later session reported intermittent long graphics-pipeline stalls, including single-frame stalls and terrain flicker.
Showing 231–240 of 308 reports
Known issues from Lichii sources
White streaks or trails at night, including around Navi, fireflies, and smoke.
Recorded fix: Turn off Emulation → Configure → Graphics → Use NVIDIA DLSS in place of a game's DLSS. The source attributes the issue to DLSS and says a fix is being tested.
Characters look too dark, there is a green tint, and FPS is lower than in earlier builds.
With DLSS on, Navi, fireflies, and smoke can leave trails at night. A fix is being tested.
AMD Radeon RX 6000 series and older on Windows crash while building shaders after boot. The release says this is fixed in build 117; RX 7000/9000 and NVIDIA are not affected.
Recorded fix: Update to build 117.
Characters look too dark, there is a green tint, and FPS is lower than in earlier builds. The issue is being investigated.
AMD black foliage and haze.
HUD flicker.
Cutscene audio drift.
First-launch shader stall on Linux.
An NVIDIA device-lost crash was reported on build 93; the release says it is awaiting retest on this build.
Showing 1–10 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.