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
98 Einträge zu Spielen und Testumgebungen sowie 275 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 |
|---|---|---|---|---|
| build-94 | runs with issues | RX 7900 XTX / I7 13700KF | Not provided | Open report |
Problems or notes: User reports excessive brightness and overexposure: the sky appears completely white, and the horizon and distant scenery are washed out by a white glow or fog effect.
Current: build-94 (1 record); previous: build-93 (0 records).
Also listed as: OoT, Ocarina of Time
| Build | Status | GPU / CPU | FPS | Details |
|---|---|---|---|---|
| build-83 | runs with issues | RTX 5090 / Ryzen 7 9800X3D | Not provided | Open report |
| build-78 | runs with issues | NVIDIA RTX 30 series or older / Not provided | Not provided | Open report |
| Not provided | runs with issues | RTX 5070 / 7800X3D | Not provided | Open report |
Problems or notes: Opening rendered and controllable Kokiri Forest gameplay was reached. Some sessions hung at “Closing software…” during shutdown, while others exited successfully. The source does not establish a cause or fix.
Problems or notes: Audio plays from a different point in the game than the picture, including Ganondorf intro audio while Link is waking up. A user comment also reports audio leading video in other scenes, with around 50 FPS in cutscenes and 35-45 FPS in-game; another reports the same intro desynchronization.
Problems or notes: A user comment reports audio playing far ahead of video in the intro scene. The user also reports 32GB DDR5.
From build-75 to build-83: follow the gameplay changes described for these two builds.
Before: Missing vegetation and incorrect material data; affected lighting and colours; a glowing doorway; one-frame white flashes; and on AMD, shaders could produce a black 3D scene.
After: Additional shader pointers and storage-buffer bindings, corrected buffer tracking and mesh-shader register handling, fixed occlusion-query and nested-return handling, and added the Max Resolution add-on and frame-ahead presentation tuning.
build-75 → build-83
| Build | Status | GPU / CPU | FPS | Details |
|---|---|---|---|---|
| build-93 | runs with issues | RX 5700 XT 8GB / Ryzen 5 5600 | Not provided | Open report |
| build-93 | runs with issues | AMD Radeon 9070XT / Intel Core I5 | Not provided | Open report |
| Not provided | unknown | GTX 1070 8GB / Ryzen 5 5500 | Not provided | Open report |
| Not provided | runs with issues | rx7600xt 16gb / ryzen 5 5600 | Not provided | Open report |
Problems or notes: User reports excessive bloom outside the Great Deku Tree, returning to normal after defeating Gohma, and invisible boxes and walls inside it. Windows 10.
Problems or notes: Shaders load slowly and significantly slow gameplay, rebuilding when entering the same area. In the Kokiri Sword area, Link and most surroundings turn solid black; white flickers also occur.
Problems or notes: Commenter reports the same issue; Windows and build are not stated.
Problems or notes: Commenter says the game runs pretty well and posts an image, but is unsure whether it relates to bloom. No specific issue is identified.
Current: build-93 (2 records); previous: build-88 (0 records).
| Build | Status | GPU / CPU | FPS | Details |
|---|---|---|---|---|
| build-93 | runs with issues | rx 6900xt / Not provided | Not provided | Open report |
Problems or notes: User reports the same vegetation disappearance issue on default settings.
Current: build-93 (1 record); previous: build-88 (0 records).
| Build | Status | GPU / CPU | FPS | Details |
|---|---|---|---|---|
| build-88 | runs with issues | NVIDIA GeForce RTX 4070 Ti / Intel Core i5-13490F | Not provided | Open report |
Problems or notes: User reports that town vegetation and small clutter objects render at a distance but disappear when approached.
Current: build-88 (1 record); previous: build-83 (0 records).
Showing 261–270 of 275 reports
Known issues from Lichii sources
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.
Gameplay performance is CPU-bound on the reported Ryzen 7 2700X; resolution scale changes and switching to Handheld did not improve performance.
On build 93 with RX 9070 XT, gameplay is slow-motion at reported frame rates, with heavy bloom and overexposure in bright areas and the Great Deku Tree rendered as a dark silhouette in its intro scene.
On RX 5700 (RDNA1), Kokiri Forest performance is reported at 14–15 FPS, compared with 22–24 FPS indoors; build 95 is reported to have the same outdoor performance as build 93.
On Lichii-AMD 2026.11.07 with RX 9070 XT using GPU Mode Fast, repeated rolling and jumping triggered black game frames while the HUD remained visible; the game continued running. Blackouts recurred in Kokiri Forest and were not accompanied by log output during the reported black periods.
Recorded fix: Switching GPU Mode from Fast to Accurate at runtime restored the picture without restarting; the commenter reports stutter afterward. Accurate mode was also reported to avoid blackouts but cause heavy stutter.
With an older configuration retaining GPU accuracy High, GPU thread splitting did not start, leaving work on one GPU thread. The commenter also reports long hitches while native pipelines were built, even with async shaders on.
On RX 9070 XT with extracted base-game version 1.0.0, the commenter reports blackouts and a Native compute shader rejected (per-tap gather) log error. They report no blackouts or such error during about 70 minutes of play using version 2.0.0 from a .nup on build 117 PGO.
User reports random freezes after 5–15 minutes of play on Linux with an AMD RX 6000 series or older GPU, followed by I/O spikes up to 6GB/s, rising RAM use, and an out-of-memory emulator crash.
Crashes during play with VK_ERROR_OUT_OF_DEVICE_MEMORY on 8 GB AMD GPUs; reports describe unhandled Vulkan exceptions.
Showing 51–60 of 287 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.