Ocarina of Time
A user reports approximately 23–25 FPS in Kokiri Forest on Fritchii v4, with CPU and GPU not saturated.
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 |
|---|---|---|---|---|
| Lichii 93 | unknown | AMD RX 9000 series / AMD Ryzen 7 5700X 8-Core Processor | Not provided | Open report |
| build-95 | runs with issues | NVIDIA RTX 30 series or older / Not provided | Not provided | Open report |
| latest | runs with issues | Intel Arc / Not provided | Not provided | Open report |
| build-117 Clang 22.1.8 | runs with issues | AMD RX 9000 series; RX 9060XT 16GB / Ryzen 7 5700X | 0–15 FPS | Open report |
Problems or notes: The reporter says this is what it looked like upon first arriving in Hyrule; the image is not described in text. A comment identifies white haze over Hyrule Field and the sky on AMD cards as the issue.
Problems or notes: The emulator reportedly crashed five times while walking from Hyrule Town to Hyrule Castle. A commenter says the issue occurred on a PGO build but not the normal build.
Problems or notes: The user reports that the game runs without crashing on Vulkan, but has very low FPS and rendering artifacts.
Problems or notes: Opening screen is reported smooth at 60 FPS. After loading a save, which reportedly takes 20–30 seconds, FPS drops to 0–15 during movement.
Current: build-93 (3 records); previous: build-88 (0 records).
| Build | Status | GPU / CPU | FPS | Details |
|---|---|---|---|---|
| build-88 | unknown | Other / Not provided | Not provided | Open report |
| build-88 | unknown | Other / Not provided | 20 FPS | Open report |
| build-75 | runs with issues | Other / Not provided | 20 FPS | Open report |
| build-75 | runs with issues | Other / Not provided | 20 FPS | Open report |
Problems or notes: User reports a crash when booting the game.
Problems or notes: The issue title reports 20 fps.
Problems or notes: Boots to a black screen with audio. A comment reports that clearing the cache and launching again fixes the black-screen issue, but the game runs at 20 fps.
Problems or notes: Audio randomly cuts in and out.
Current: build-88 (2 records); previous: build-83 (0 records).
| Build | Status | GPU / CPU | FPS | Details |
|---|---|---|---|---|
| build-93 | runs with issues | 6GB RTX 3050 / i7-13620H | Not provided | Open report |
Problems or notes: A commenter says they can control Link and do not experience white flashes on Linux, while white flashes occurred for them on Windows 11. They say build 93 runs better for them on Linux.
Current: build-93 (1 record); previous: build-88 (0 records).
| Build | Status | GPU / CPU | FPS | Details |
|---|---|---|---|---|
| build-93 | runs with issues | 6950XT / 5800x | Not provided | Open report |
Problems or notes: Bushes render correctly at a distance but appear dead up close.
Current: build-93 (1 record); previous: build-88 (0 records).
Showing 101–110 of 308 reports
Known issues from Lichii sources
A user reports approximately 23–25 FPS in Kokiri Forest on Fritchii v4, with CPU and GPU not saturated.
Gameplay graphics remain black while UI and button prompts work; the cutscene and opening title display correctly.
Foliage, leaves, walls, doors, and other geometry can be missing on GPUs without VK_EXT_mesh_shader because task/mesh shader draws are skipped.
A draft compute-based task/mesh shader fallback rendered some foliage on GTX 1070 but produced flickering geometry and still missed canopies, grass, and house walls.
The in-game language did not change to Portuguese (Brazil) after configuring the emulator system language to Portuguese.
On Linux with NVIDIA GPUs, gameplay can lead to a GPU hang after roughly five minutes. Reports include Xid 109 CTX SWITCH TIMEOUT or a GPU stuck at 100% utilization without an Xid.
Random white splotches appear in Hyrule Field after beating King Dodongo.
The whole PC crashes right after the intro movie on Linux with an AMD ATI Radeon RX 9060 XT.
White squares appear in Kakariko village.
On the reported NVIDIA systems using driver 581.29, the game crashes with Vulkan device loss during shader and pipeline compilation after the intro cinematic; reports include repeated Unmapped Device ReadBlock errors and Windows nvlddmkm Event ID 153.
Recorded fix: One user reports that updating to the official NVIDIA Game Ready 621.14 driver and rebooting resolved the issue on their system. Another comment says it started working after installing the latest Nvidia driver.
Showing 21–30 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
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.