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-117 | runs with issues | Other / Apple M1 | 1 FPS | Open report |
Problems or notes: Boots and plays audio, but the image is completely black from startup; intermittent red/green block artifacts are reported. Approximately 1 FPS.
Current: build-117 (1 record); previous: build-116 (0 records).
| Build | Status | GPU / CPU | FPS | Details |
|---|---|---|---|---|
| build 115 | runs with issues | RTX 5070 / Ryzen 5700x | Not provided | Open report |
| build 116 (PGO) | runs with issues | RX 9070 XT / Not provided | 60 FPS | Open report |
Problems or notes: Grass vanishes when swinging the sword.
Problems or notes: User reports that after 9000-frame eviction of preloaded pipelines, runtime builds caused draws to be held for up to 8 seconds per 10-second window and a 19-second freeze. The user says disabling eviction locally kept the game smooth; this is a user workaround, not a confirmed fix.
| Build | Status | GPU / CPU | FPS | Details |
|---|---|---|---|---|
| build-83 | playable | RTX 4070 Ti / Ryzen 7 7700X | Not provided | Open report |
| 55532f2d814215aaf32a76c214cf129f2cb6282b | runs with issues | RTX 5060 Ti / Ryzen 7 7800X3D | 15–51 FPS | Open report |
Problems or notes: In a tested docked 2x gameplay run, haze was gone and Link and Kokiri Forest were clearly visible without shader rejections. FPS was described as low, with no value stated.
Problems or notes: Foliage, grass, shadows, and atmosphere were reported as substantially improved, and the Great Deku Tree exterior dialogue and interior corridor rendered visibly. Some eastern outdoor views remained severely white/yellow and washed out. Outdoor performance varied from 28–31 FPS in other views to about 15 FPS in problematic areas; the Deku Tree exterior dialogue showed 36 FPS and the interior showed 51 FPS. Texture-format and texture-index assertions were logged; one earlier Accurate attempt exited with code -1073740791, while a later session ran about 20m31s and exited normally. No causal link between assertions, lighting, or the earlier crash was established.
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 |
|---|---|---|---|---|
| 62ba83427e | runs with issues | Radeon 8060S / Ryzen AI MAX+ 395 | 31–37 FPS | Open report |
Problems or notes: In Kokiri Forest, haze, blotches, and a translucent band appear in a fullscreen pass. Rejecting shader 3ddfb1d7a854c849 removed the haze and blotches in that test, while rejecting 780c0536b89fc89e removed fog but left blotches; these workarounds also remove game effects. Two starts stayed black from the beginning, one with music. A reported 31–37 FPS comparison against build-75 used views that were not identical.
Also listed as: OOT Remake, OoT
| Build | Status | GPU / CPU | FPS | Details |
|---|---|---|---|---|
| 3724db9a5c | playable | RTX 4070 / i9-12900F | 16 FPS | Open report |
| b8c812b18 | runs with issues | RX 5700 / Not provided | Not provided | Open report |
| build 95 | playable | RX 7900 XTX / Ryzen 7 9800X3D | 60 FPS | Open report |
| nx2 @ 27226d2 plus two measurement-only commits | runs with issues | RTX 5060 Laptop (8 GB) / Ryzen AI 9 365 | Not provided | Open report |
Problems or notes: The tester reported visible grass and a clear view of the tree through grey fog in front of the Deku Tree. The in-game counter showed 16 FPS in that view; this was a single reading.
Problems or notes: A user reported a local ClangCL build stalled with no frames (maximum 8 presents); a local MSVC build also stalled and died within a minute. In comparison, the user's build-75 release run presented frames at 32 FPS. The maintainer said the report was from an old commit and may no longer apply.
Problems or notes: Not provided
Problems or notes: In the Kokiri Forest scene, disabling per-fence Preflushable downloads or batching them by 64 fences increased GPU back-thread draws per second but broke auto-exposure, leaving the scene overexposed. Default downloads preserved correct exposure. The issue reports measurements, not a gameplay FPS result.
Showing 1–10 of 194 reports
Known issues from Lichii sources
Frequent freezing is reported while running at about 30 FPS on Windows 10 with build 117.
The user reports very low FPS and rendering artifacts when running on an Intel Arc GPU under Windows 11 with Vulkan.
On an AYN Thor with Adreno 740 and Turnip, large native compute shaders cause pipeline compilation to consume substantial memory and pin Vulkan pipeline-builder threads; reports include black output, GPU device loss, or out-of-memory termination.
On ARM hosts using NCE, the built-in Dynamic FPS by Dark and Max Resolution patches together were reported to trigger an early SIGILL on builds 88 and 94.
Recorded fix: Disable both Dynamic FPS by Dark (built-in) and Max Resolution (built-in) in the game's Add-Ons.
Long shader and pipeline hitches while exploring; the user also reports texture flashes or freezes when new pipelines compile.
A user reports constant CPU-side coil whine while playing on a laptop.
Missing textures were reported on build 95; stuttering and long loading times were reported on build 117.
On build-117, the user reports nonstop freezes or frame drops during gameplay. They report occasional hangs on older builds.
A system-wide GPU error and crash after playing for a few minutes, reported with AMD RX 6000 series or older on Linux in Build 117 PGO.
Crashes during boot at an unimplemented nx2:vi2 function 201; the report also mentions a later unimplemented IGeneralService function 101 assert.
Showing 81–90 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-117 · Veröffentlicht am November 7, 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.