Ocarina of Time
User reports random freezes after 5–15 minutes of play on Linux with an AMD RX 6000 series or older GPU, followed by I/O spikes up to 6GB/s, rising RAM use, and an out-of-memory emulator crash.
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: dkb
| Build | Status | GPU / CPU | FPS | Details |
|---|---|---|---|---|
| build-70 | runs with issues | NVIDIA GeForce RTX 4060 Laptop, 8 GB / Intel Core i7-13650HX | 20 FPS | Open report |
Problems or notes: Terrain/world renders solid white while the HUD and characters still draw.
Current: build-70 (1 record); previous: build-65 (1 record).
Also listed as: dkb
| Build | Status | GPU / CPU | FPS | Details |
|---|---|---|---|---|
| build-70 | runs with issues | NVIDIA RTX 40 series / Not provided | Not provided | Open report |
| build-70 | playable | Not provided / Not provided | Not provided | Open report |
Problems or notes: User reports visual artifacts, especially on shadows.
Problems or notes: Runs well, though not at a locked 60 fps.
Current: build-70 (2 records); previous: build-65 (0 records).
| Build | Status | GPU / CPU | FPS | Details |
|---|---|---|---|---|
| build-70 | runs with issues | NVIDIA RTX 40 series / Not provided | Not provided | Open report |
Problems or notes: A user reported that Fortunes Weave skips pre-rendered videos, including the opening cut-scene, and proceeds to the in-engine scene.
Current: build-70 (1 record); previous: build-65 (1 record).
| Build | Status | GPU / CPU | FPS | Details |
|---|---|---|---|---|
| build-70 | runs with issues | Not provided / Not provided | Not provided | Open report |
Problems or notes: Some races still stall while shaders build.
Current: build-70 (1 record); previous: build-65 (0 records).
| Build | Status | GPU / CPU | FPS | Details |
|---|---|---|---|---|
| build-70 | playable | Not provided / M4 Pro | 30–38 FPS | Open report |
Problems or notes: The report says races measured 30–38 fps after macOS performance work.
Current: build-70 (1 record); previous: build-65 (0 records).
| Build | Status | GPU / CPU | FPS | Details |
|---|---|---|---|---|
| build-70 | not booting | Adreno 740 / Snapdragon 8 Gen 2 | Not provided | Open report |
Problems or notes: On the PGO AppImage, ZBIC NSO decompression logs six `assert r > 0` failures and the game remains stuck without presenting a frame. The non-PGO AppImage of the same commit has no such assertions and boots, though another panic or black-screen report is mentioned afterward.
Current: build-70 (1 record); previous: build-65 (0 records).
Also listed as: StarFox
| Build | Status | GPU / CPU | FPS | Details |
|---|---|---|---|---|
| build-70 | runs with issues | Not provided / Not provided | ?–30 FPS | Open report |
Problems or notes: Gameplay is capped at about 30 fps despite the game asking for 60. On RTX 50-series GPUs (5070 Ti, 5090), the GPU device can be lost shortly after a scene change.
Current: build-70 (1 record); previous: build-65 (0 records).
| Build | Status | GPU / CPU | FPS | Details |
|---|---|---|---|---|
| build-70 | runs with issues | Not provided / Not provided | Not provided | Open report |
Problems or notes: Some textures are still black, and it can crash later in play.
Current: build-70 (1 record); previous: build-65 (0 records).
Showing 1–9 of 9 reports
Known issues from Lichii sources
User reports random freezes after 5–15 minutes of play on Linux with an AMD RX 6000 series or older GPU, followed by I/O spikes up to 6GB/s, rising RAM use, and an out-of-memory emulator crash.
Crashes during play with VK_ERROR_OUT_OF_DEVICE_MEMORY on 8 GB AMD GPUs; reports describe unhandled Vulkan exceptions.
A user reports a reproducible crash to desktop within a few seconds of entering the Guardhouse in Hyrule Castle Town.
The game freezes or crashes in the Hyrule Castle Town guard house when moving deeper into the room, talking to the guard, or looking toward the windowed wall while panning the camera.
On Frizti v3, performance in the guard house remains low after the freeze is addressed, with about 20 fps reported as the floor after additional texture-cache changes.
Black 3D content in docked mode on Linux, while the GUI overlay and main menu render; switching to handheld mode allows the game to render.
A user reports performance of up to 6 FPS and a crash at Kokiri Tree after removing the pipeline cache.
With Switch 2 draws with unbuilt pipelines set to Bounded and an 8 ms wait, the image washed out to white and orange and parts of the scene rendered as large flat polygons while pipelines were building.
The user reports that characters have no shadows.
With a Steam Controller (2026) connected through its wireless dongle, motion mapping via Configure → Controls does not detect shaking, and gyro/accelerometer input stops after the controller reconnects or after a few seconds with Steam running.
Showing 71–80 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.