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
| 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.
| Build | Status | GPU / CPU | FPS | Details |
|---|---|---|---|---|
| build-93 | runs with issues | RX 9060 XT 16 GB / i7-9700K | 19–36 FPS | Open report |
Problems or notes: A user reports that frame_gen and game_dlss_network enabled caused a near-white presented frame; setting both to false produced a correct image. White flashes were associated with async_presentation=true; async_presentation=false reduced white pixels in a 40-frame capture to 0.2% but lowered performance to about 19-25 FPS in a heavy Kokiri scene. The approximately 36 FPS result required async presentation, which flashed.
Current: build-93 (1 record); previous: build-88 (0 records).
| Build | Status | GPU / CPU | FPS | Details |
|---|---|---|---|---|
| nx2-build-75 [PGO] | not booting | AMD Radeon RX 6650 XT (RDNA2) / Intel Core i5-10400F | Not provided | Open report |
| nx2-build-83 | runs with issues | Radeon RX 6800 / Not provided | 43–47 FPS | Open report |
Problems or notes: The render area stays black after boot in both handheld and docked modes. The reporter also tried build 75 and pre-release #80; the black screen persisted. The associated comment describes the game ID as 0400486024DEC000.
Problems or notes: The reporter says the game renders correctly in a screen capture, including the title screen, logo, and menu, but the presented display is solid green. They report about 43 fps from presents and a 47 fps OSD in the capture.
| Build | Status | GPU / CPU | FPS | Details |
|---|---|---|---|---|
| build-83 | runs with issues | RX 9060 XT 16 GB / Not provided | Not provided | Open report |
| build-75 | not booting | AMD RX 6000 series or older / Not provided | Not provided | Open report |
Problems or notes: The reporter says the black-screen issue is gone and the game reaches gameplay, but the device is lost at gameplay start with VK_ERROR_DEVICE_LOST, followed by a crash.
Problems or notes: The reporter says the game boots with sound and the Zelda logo, then remains on a black screen.
Current: build-83 (1 record); previous: build-75 (1 record).
Showing 1–6 of 6 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
build-83 · Veröffentlicht am November 6, 2026
12 veröffentlichte Downloaddateien für diesen Build.
build-75 · Veröffentlicht am November 5, 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.