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: 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
Day-only garbage graphics in the Bombchu Bowling Alley: stones and ovens flash pink, yellow, red, or black, and the sign displays garbage, noise, and fragments of another image. It looks correct at night after leaving and returning, and was still present in build-117.
After outdoor play, the sky becomes flat yellow-white and water shimmers green until reboot, due to NaNs spreading through bloom. The report says the NaNs probably originate from fog/foliage probe reads beyond the 64 MiB graphics table-pointer cap.
Recorded fix: Use NaN-safe min/max/clamp handling and fix table-pointer reads beyond the old 64 MiB cap; the reporter confirmed normal visuals after both fixes.
Foliage and vegetation near the player may turn into dead-looking variants or lose leaves up close, including hedges and plants in Hyrule Castle; reports also mention trees, Kokiri Forest bushes, Castle Town hedges, and Hyrule Field grass. One user describes the behavior as an inverted LOD.
On macOS/MoltenVK with an Apple M1, the Switch 2 NSO version boots and plays audio but presents a black image from startup, with approximately 1 FPS and occasional red/green block artifacts.
On AMD GPUs, Ocarina of Time's compute shaders can fail compilation with VK_ERROR_OUT_OF_HOST_MEMORY or cause the AMD driver to crash. The issue report describes missing intro video and an eventual process crash; a later user reports an access violation inside amdvlk64.dll.
OpenGL is reported not to work for this game because GLSL task and mesh programs are not implemented, resulting in repeated errors and an emulator hang.
Rejecting shader hashes before translation skips their dispatches and can result in missing output or a black screen; a user reports the environment switch did not affect the tested Vulkan compute-pipeline path.
Recorded fix: For testing shader rejection, keep the disk shader cache off or delete it before each run; the maintainer says cached shaders are loaded without checking the rejection list.
Performance slows in crowded or busy areas, with front/back GPU-thread synchronization drains and waits; short freezes while attacking are also reported.
Shader compilation can cause freezes of about 3 seconds with each step, according to a user report.
On integrated AMD graphics, device-memory thresholds can keep the texture cache collector in aggressive mode even though deleting all images cannot reduce total usage below the threshold. This causes extensive image churn and GPU waits during gameplay.
Showing 31–40 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.