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-83 | playable | RTX 4070 Ti / Ryzen 7 7700X | Not provided | 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.
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
Also listed as: Ocarina of Time, Zelda: Ocarina of Time, OoT, Zelda OoT, TLoZ: OoT
| Build | Status | GPU / CPU | FPS | Details |
|---|---|---|---|---|
| build-83 | runs with issues | AMD RX 9000 series / Not provided | Not provided | Open report |
Problems or notes: The issue reporter says the game reaches the end of the introductory cutscene, turns black while loading gameplay, then crashes with an AMD TDR. Comments report similar crashes on RX 9060 XT, RX 9070/9070 XT, and RX 7900 XTX. One user says EDEN_NX2_NO_MESH=1 stops the Windows driver crash but leaves the game black-screened or crashing while loading gameplay. Reports on Build 93 conflict: one user reports an early GPU crash without the variable, another reports playing through Kokiri Forest without crashes, and another says the issue remains and visual bugs occur during gameplay.
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
Also listed as: Ocarina of Time, OoT
| Build | Status | GPU / CPU | FPS | Details |
|---|---|---|---|---|
| build-83 | runs with issues | AMD Radeon RX 9060 XT 16 GB / Intel i7-9700K | Not provided | Open report |
Problems or notes: The GPU device was lost when gameplay started.
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-83 | runs with issues | RX 9060 XT 16 GB / 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.
Current: build-83 (1 record); previous: build-75 (1 record).
Also listed as: OoT
| Build | Status | GPU / CPU | FPS | Details |
|---|---|---|---|---|
| build-83 | runs with issues | RTX 3090 24 GB / Ryzen 9 5900X | Not provided | Open report |
Problems or notes: The user reported repeated GPU-thread graphics-pipeline builds during gameplay across boots, causing a visible hitch and about 943–998 ms of GPU-thread time in the first 10 seconds. A later user comment reported the issue fixed for them on build-88 (MSVC), which includes #194; that report is not maintainer-confirmed.
Current: build-83 (1 record); previous: build-75 (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 |
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.
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
Also listed as: OoT, Ocarina of Time
| Build | Status | GPU / CPU | FPS | Details |
|---|---|---|---|---|
| build-83 | unknown | Not provided / Not provided | Not provided | Open report |
Problems or notes: The release says the perf9 build was tested successfully in Ocarina of Time, but provides no gameplay duration or specific tested hardware.
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
Showing 1–7 of 7 reports
Known issues from Lichii sources
Fairy-light flickering and flashing white sky, reported in Sacred Grove and other locations; may occur randomly without clear reproduction steps.
On AMD RDNA2 GPUs, the 16x16x16 VK_KHR_cooperative_matrix HMMA pipeline path can cause an access violation in amdvlk64.dll during shader or pipeline compilation, typically 30–90 seconds after game startup.
Recorded fix: The source reports that EDEN_NX2_NO_COOP_MATRIX=1 avoids the crash. A later comment states that merged PR #657 fixes it.
The underground fairy fountain has no environment.
Recorded fix: A commenter says the issue is caused by a dump missing textures and advises using a NUP dumped without missing textures.
On Linux, a black screen can occur with the Native MME error "instruction outside uploaded RAM". One report says shaders load and menu music is audible; another says the game opens, reaches 0 FPS, and freezes.
Recorded fix: A comment reports that setting DMA accuracy to Safe works as a workaround. Another comment attributes the error to a GCC 13 miscompile and says a fix was merged but was not yet in a published release.
Cutscenes play in slow motion, lagging behind audio; the report describes them as locked to 49fps with 99% GPU usage.
The same slow-motion cutscene problem is reported.
The same slow-motion cutscene problem is reported.
After the Kaepora Gaebora cutscene near Hyrule Castle, the scene appears empty and foggy and Link repeatedly falls through the world and voids out, preventing progression.
User reports 17–23.8 FPS in 3D races on build-95, compared with 40.0–54.1 FPS on build-93 under the same reported test conditions.
Black screen when starting in build 95 on Linux; a commenter reports black screen with music. The commenter says build 93 loads normally on their system.
Showing 111–120 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
Für Ocarina of Time ist kein getesteter Build mit verfügbarem Download verknüpft. Sieh dir die aktuellen Releases oder die Diskussion zum Spiel im Issue-Tracker an.
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.