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: Ocarina of Time, OoT
| Build | Status | GPU / CPU | FPS | Details |
|---|---|---|---|---|
| official build88 (55532f2), standard MSVC package | playable | RTX 5090 / Ryzen 7 9800X3D | 47.64–59.9 FPS | Open report |
| 95 | playable | NVIDIA RTX 3070 8 GB / Ryzen 7 5700X (8C/16T) | 32.82–40.75 FPS | Open report |
| Not provided | runs with issues | NVIDIA RTX 3060 12 GB / i5-13600KF | Not provided | Open report |
| Not provided | runs with issues | RTX 4080 SUPER / Not provided | 20 FPS | Open report |
| Not provided | runs with issues | RTX 5080 / Ryzen 9 9950X3D | Not provided | Open report |
| Not provided | runs with issues | RX 6700 XT / Not provided | Not provided | Open report |
| Not provided | not booting | RX 5700 / Not provided | Not provided | Open report |
| nx2-build-88 (55532f2) | runs with issues | NVIDIA GeForce RTX 5060 (8 GB VRAM) / AMD Ryzen 5 5600G (6C/12T) | Not provided | Open report |
| nx2-build-93 | runs with issues | RTX 2060 6 GB / Xeon E5-1620 v3 (4C/8T) | Not provided | Open report |
| nx2-build-117 | runs with issues | AMD Radeon RX 580 8 GB (Polaris, GCN 4) / i3-8100 | Not provided | Open report |
Problems or notes: A user comment reports local native-present averages of 59.90 FPS at the Mido viewpoint at 1X, 49.53 FPS in a central village tree view at 1X, and 47.64 FPS in that view at 2X. New-area shader hitches occurred. The village/pond check retained three hearts, but the Training Grounds/maze transition and later game were not verified.
Problems or notes: User reports 32.82 / 34.09 FPS with pinning disabled and 40.75 / 39.84 FPS with pinning enabled; no crash in 2,383 recorded intervals. The user reports that sustained 60 FPS was not achieved. Testing used Vulkan, Fast GPU accuracy, Docked, 1x resolution, and 100% speed.
Problems or notes: Freezes in the Hyrule Castle Town guard house when walking toward the guard or looking toward the wall with windows. The report reproduces on multiple builds and GPUs. A commenter reports that a texture pool patch in Frizti v3 stopped the freeze, but the room still had low performance after further texture-cache changes.
Problems or notes: A commenter reports the guard-house freeze on Frizti v3. A texture pool patch reportedly stopped the freeze, but the room's performance remained low, with a floor of about 20 fps after additional texture-cache changes.
Problems or notes: A commenter reports the same guard-house freeze, both while talking to the guard and while moving around inside.
Problems or notes: A commenter reports crashes in the guard house, reproduced 5/5 times while looking toward the wall with windows and panning the camera. A reported VRAM allocation burst preceded the crashes; whether memory pressure caused them was unclear.
Problems or notes: A commenter reports black 3D graphics with working UI and attributes this to a possible DemoteCombinationPass issue; this is a user-provided analysis, not a confirmed fix.
Problems or notes: In a 1h 49m gameplay session, the reporter observed severe 1.3–6.59 second freezes, continuous frame-time micro-stutters, repeated GPU-thread shader translation stalls, and 579,265+ synchronous OnCPURead waits. The session had 0 crashes. Vulkan, 1x, GPU Mode Accurate, Async GPU and async shader compilation enabled, and Enable Reactive Flushing enabled.
Problems or notes: A user follow-up reports FPS averages falling from 53 in the first 10-minute bucket to about 23 in the 80–90-minute bucket during a 98-minute session with Reactive Flushing enabled, alongside 365,889 OnCPURead events and stalls over 2 seconds. In additional roughly 100-minute sessions, OnCPURead growth occurred with Reactive Flushing both on and off; with it off, FPS averages were 16–33 after the first 10 minutes and stalls reached 12 seconds, with one around 49 seconds. The reporter notes the comparison is not conclusive.
Problems or notes: A user reports the AMD Vulkan driver faults with exception 0xc0000005 during compute-pipeline compilation. Two shader pipelines repeatedly fail to finish; the same was reproduced on nx2-build-95. OpenGL was also reported to fail because GLSL task and mesh programs are not implemented.
Current: build-93 (1 record); previous: build-88 (2 records).
Showing 121–130 of 194 reports
Known issues from Lichii sources
White streaks or trails at night, including around Navi, fireflies, and smoke.
Recorded fix: Turn off Emulation → Configure → Graphics → Use NVIDIA DLSS in place of a game's DLSS. The source attributes the issue to DLSS and says a fix is being tested.
Characters look too dark, there is a green tint, and FPS is lower than in earlier builds.
With DLSS on, Navi, fireflies, and smoke can leave trails at night. A fix is being tested.
AMD Radeon RX 6000 series and older on Windows crash while building shaders after boot. The release says this is fixed in build 117; RX 7000/9000 and NVIDIA are not affected.
Recorded fix: Update to build 117.
Characters look too dark, there is a green tint, and FPS is lower than in earlier builds. The issue is being investigated.
AMD black foliage and haze.
HUD flicker.
Cutscene audio drift.
First-launch shader stall on Linux.
An NVIDIA device-lost crash was reported on build 93; the release says it is awaiting retest on this build.
Showing 1–10 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
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.