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: OoT
| Build | Status | GPU / CPU | FPS | Details |
|---|---|---|---|---|
| local non-PGO nx2 @ 4c173bb792 with PR #345 merged (4647895acc) | playable | Radeon RX 9070 XT (RADV GFX1201) / Ryzen 7 5800X3D (8C/16T) | Not provided | Open report |
| Lichii nx2 build 93, Windows release | runs with issues | RX 9070 XT 16 GB / Ryzen 7 7800X3D (8C/16T) | 18 FPS | Open report |
| Lichii nx2-build-83 non-PGO AppImage | runs with issues | RX 9070 XT 16 GB (RADV GFX1201) / Ryzen 7 5700X (AM4, 8C/16T, non-X3D) | 20–35 FPS | Open report |
Problems or notes: In a Deku Tree interior test, the reporter measured 16.8-18.6 ms frame times and reported the area was at the present cap. White flashes were confirmed gone there. Kokiri Village and Hyrule Field remained untested, and runtime pipeline builds caused isolated frame spikes.
Problems or notes: On Windows 11 Enterprise LTSC 2024, gameplay was reported at about 18 fps (about 56 ms per frame) with no saturated thread. New-content pipeline compilation caused first-visit hitches. A later follow-up on Frizti v3 reported about 20 fps in a busy view and about 60 fps looking at the floor; the reporter attributed the heavy-view limit to host GPU load, but that follow-up did not identify the build as build 93.
Problems or notes: On CachyOS, gameplay commonly ran at 20-35 FPS and in slow motion; menus were about 60 FPS and intro video/audio stuttered. The non-PGO AppImage rendered and reached gameplay. The PGO AppImage produced audio but no video output, and clearing the shader cache did not resolve it. The stated FPS range is the reporter's gameplay observation, not the table's median window FPS.
Also listed as: OoT
| Build | Status | GPU / CPU | FPS | Details |
|---|---|---|---|---|
| b4716fc | runs with issues | RX 6700 XT / Not provided | Not provided | Open report |
| nx2 c9bdbaa | runs with issues | RX 6600 XT / Not provided | 24–48 FPS | Open report |
Problems or notes: The title screen, intro, and cinematics before the Deku Tree exterior cutscene render correctly. That cutscene is black except for a small circle around Navi where the world renders.
Problems or notes: A commenter reports 24–25 FPS at the Deku Tree web after watching the New Game intro, versus 44–46 FPS when loading the same save without the intro. With the reported storage-write extent branch, the intro-first sequence gave 44–47 FPS, gameplay about 35–48 FPS, and auto-exposure stayed correct. These are user-reported test results.
Also listed as: OoT
| Build | Status | GPU / CPU | FPS | Details |
|---|---|---|---|---|
| build 95 | runs with issues | RX 7600 (RADV) / Ryzen 7 7700 | 15–20 FPS | Open report |
Problems or notes: The report says open areas remain CPU-bound at about 15–20 FPS; indoor and small areas were fine.
| Build | Status | GPU / CPU | FPS | Details |
|---|---|---|---|---|
| build-75 | runs with issues | NVIDIA RTX 50 series / Not provided | Not provided | Open report |
Problems or notes: The issue reports a hard black screen outside captions in handheld mode and a vaseline-like image in docked mode. Comments report black screens during gameplay and the introductory cinematic, intermittent black flashes, excessively bright and low-resolution handheld visuals, and audio playing ahead of the video.
Current: build-75 (1 record); previous: build-70 (0 records).
| Build | Status | GPU / CPU | FPS | Details |
|---|---|---|---|---|
| Not provided | runs with issues | NVIDIA RTX 30 series or older / Not provided | Not provided | Open report |
Problems or notes: User reports significantly worse performance and that parts of the game are broken in build 117 compared with build 93.
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 |
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.
Current: build-117 (2 records); previous: build-116 (0 records).
Showing 11–20 of 142 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-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.