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-75 | runs with issues | AMD Radeon RX 6800 XT (16 GB, RDNA 2) / AMD Ryzen 5 9600X | Not provided | Open report |
Problems or notes: A commenter reports that entering gameplay gives a completely black screen for all 3D geometry. With use_disk_shader_cache = true, subsequent boots hang at Loading Shaders 25 / 27.
Current: build-75 (1 record); previous: build-70 (0 records).
| Build | Status | GPU / CPU | FPS | Details |
|---|---|---|---|---|
| 75 (`nx2-build-75`) | runs with issues | AMD RX 7000 series (Radeon RX 7600, RADV 26.2.5, Vulkan 1.4.354) / Not provided | Not provided | Open report |
Problems or notes: During the AV1 intro cutscene, the video area is solid green while audio and subtitles work. The report says frames decode at 60 fps, but this is not a gameplay FPS measurement.
Also listed as: Ocarina of Time
| Build | Status | GPU / CPU | FPS | Details |
|---|---|---|---|---|
| d8ad4787 | runs with issues | Adreno 740 / Snapdragon 8 Gen 2 | Not provided | Open report |
Problems or notes: User reports that this desktop build of pavelgajdo/Lichii-Android nx2 avoids the early NCE SIGILL with both built-in patches enabled, renders the 3D field behind the title logo, and plays the full intro. Loading gameplay then causes memory exhaustion on the 11.2 GiB device; lowering scale did not prevent it.
| Build | Status | GPU / CPU | FPS | Details |
|---|---|---|---|---|
| nx2-build-95 | runs with issues | AMD Radeon RX 6800 XT / AMD Ryzen 5 5600 | 15–29 FPS | Open report |
Problems or notes: User report: With async GPU emulation enabled, the game stalls after the first AV1 frame with a black screen and audio but no input response. With async GPU emulation disabled, it boots and plays, but cutscenes run at about 29 fps and gameplay at about 15–22 fps; the game froze while walking in the first area about 5.7 minutes after launch.
| Build | Status | GPU / CPU | FPS | Details |
|---|---|---|---|---|
| build-88 | runs with issues | AMD RX 9000 series / Not provided | Not provided | Open report |
Problems or notes: The game shows video and music during the intro, then crashes after Ganondorf makes Link wake up. A commenter reports delayed video followed by an emulator crash with an AMD RX 9060 XT 16gb graphics card. Another report says a suggested procedure did not work on Win11 with an RX 9070 XT 16 GB and Ryzen 7 7700, and that a driver crash remained.
Current: build-88 (1 record); previous: build-83 (0 records).
| Build | Status | GPU / CPU | FPS | Details |
|---|---|---|---|---|
| chuppatricky-amd-testbuild-v13-windows-x86_64.zip | runs with issues | AMD RX 6000 series or older / Not provided | Not provided | Open report |
Problems or notes: Crashes at the same moment as it flies under the user's feet.
| Build | Status | GPU / CPU | FPS | Details |
|---|---|---|---|---|
| Lichii nx2-build-75 | not booting | Radeon RX 580 (Polaris / GCN4), 8 GB / Intel Xeon E5-2667 v4 (8C/16T, AVX2) | 0 FPS | Open report |
Problems or notes: The game boots and the intro AV1 video begins decoding, but the screen remains black and FPS stays at 0 while compute pipelines are built. The report says this persists for over five minutes. Multiple settings and cache-clearing attempts made no difference.
Also listed as: OoT, Ocarina of Time
| Build | Status | GPU / CPU | FPS | Details |
|---|---|---|---|---|
| build-117 | playable | Radeon RX 9070 XT / AMD Ryzen 7 5700X | 19–65 FPS | Open report |
| nx2-build-92 | runs with issues | RX 7800 XT (RADV) / Ryzen 7 7700X | 35–59 FPS | Open report |
| 95 Non-PGO | not booting | AMD Radeon RX 9070 XT / AMD Ryzen 7 5700X (AM4) | Not provided | Open report |
Problems or notes: The user reports rendering works again. In Wayland, around 19–25 FPS, fluctuating. In XWayland with QT_QPA_PLATFORM=xcb, Kokiri Village measured 25–54 FPS, usually around 30 FPS; inside the Deku Tree usually 30–45 FPS while idle, occasional peaks to 65 FPS, and recurring drops to 19 FPS. The user reports normal game speed despite frame drops and says the game is playable; FPS/frametime variability remains substantial.
Problems or notes: Ubuntu 26.04, Docked, GPU accuracy Low. Without EDEN_NX2_NO_MESH=1, device loss occurs while loading a save. With the variable, a single 337-second session ran until the user closed it; approximately 59 FPS with dips to 35–50 and some stutter, 47 draws skipped, and a door was transparent at the start. This was not tested in a new game.
Problems or notes: The game displays a completely black screen while intro audio continues, after shader compilation. The report says this also occurs in native Wayland, XWayland with QT_QPA_PLATFORM=xcb, with EDEN_NX2_NO_MESH=1 alone, and with both environment variables together. Removing Vulkan Pipeline Cache and Cache Storage and recompiling shaders did not resolve it.
Current: build-117 (1 record); previous: build-116 (0 records).
Showing 241–250 of 308 reports
Known issues from Lichii sources
On the reported Radeon 890M system, the game freezes during early Kokiri Forest gameplay, accompanied by Unmapped Device ReadBlock errors; a later report on build 117 also describes pipeline-building stalls and a hard freeze.
Stutters or freezes and drops to 15 or fewer FPS while shaders are building.
First-visit shader stutter.
Hard lag or freezes when shaders are being built, mostly on first visits to areas, as reported by the issue author.
In build 117, the reporter experienced pervasive shader stutter and repeated shader rewriting, instability and choppiness, and broken frame generation. A commenter separately reports freezes when entering new areas.
Long freezes while entering new areas, according to a commenter.
In Build 117, pre-rendered cutscenes reportedly run at 28 FPS in slow motion and fall out of sync with audio, while gameplay is unaffected.
A commenter reports slow motion in Build 93.
On Linux using a Steam Deck, the reporter describes a main-menu performance regression in build 117, from 60 FPS with some drops on the prior legacy build to 10 FPS, with audio out of sync. The non-PGO version reportedly had the same problem.
Shader stutter and multi-second freezes while shaders are being built, including during first visits.
Recorded fix: A commenter reports the stutter was resolved for them on a fork built with PR #579 by running the one-time shader warm-up from the game files; it took about 23 minutes on their CPU.
Showing 51–60 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.