Ocarina of Time
On Linux with AMD RX 9000-series graphics using RADV, an invalid SPIR-V fragment shader can cause a segfault during Vulkan graphics-pipeline construction during gameplay.
Recorded fix: Fixed in build 93 and later releases.
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.
| Build | Status | GPU / CPU | FPS | Details |
|---|---|---|---|---|
| nx2-build-117 | runs with issues | Radeon RX 6600M / Xeon E5-2666 v3 | Not provided | Open report |
Problems or notes: A user reports frequent shader-building notifications and stutter, including when revisiting areas. Their capture showed runtime pipeline creation but no eviction entries; they say they cannot yet determine how much persists on a second launch.
| Build | Status | GPU / CPU | FPS | Details |
|---|---|---|---|---|
| 75 (`nx2-build-75`) | runs with issues | AMD Radeon RX 6700 XT 8 GB, Vulkan 1.4.315 / AMD Ryzen 7 5800X | Not provided | Open report |
Problems or notes: The game renders normally before the AV1 intro cutscene. At the cutscene, the video layer is black while audio and subtitles work, then the emulator hangs indefinitely in a single-thread spin.
Also listed as: Ocarina of Time
| Build | Status | GPU / CPU | FPS | Details |
|---|---|---|---|---|
| build-88 | runs with issues | Adreno 740 / Snapdragon 8 Gen 2 | Not provided | Open report |
| build-75 | runs with issues | Adreno 740 / Snapdragon 8 Gen 2 | Not provided | Open report |
Problems or notes: User reports NCE SIGILL about 5 seconds after launch; with Dynarmic there was no crash, but memory use rose substantially and the run stalled. A later comment says the SIGILL occurs when both built-in Dynamic FPS by Dark and Max Resolution patches are enabled; disabling both avoids it, but the run remains unplayable due to memory pressure and sparse frame captures.
Problems or notes: User reports that the game boots but remains black on this device. Large compute-shader compilation pins pipeline-builder threads and drives memory use toward exhaustion. Some runs have audio; others do not. Later comments report title-screen and intro progress on other builds, but black gameplay frames, memory pressure, intermittent crashes, or freezes remain.
Current: build-88 (1 record); previous: build-83 (0 records).
| Build | Status | GPU / CPU | FPS | Details |
|---|---|---|---|---|
| build 117 (Windows PGO) | runs with issues | NVIDIA GeForce RTX 4070 Laptop GPU / AMD Ryzen 7 7745HX (laptop CPU) | Not provided | Open report |
Problems or notes: The user reports constant coil whine from the CPU area while playing; GPU usage is around 25-35% and CPU usage around 40-50%.
Also listed as: Ocarina of Time, OoT
| Build | Status | GPU / CPU | FPS | Details |
|---|---|---|---|---|
| build-93 | playable | AMD Radeon RX 9060 XT 16 GB / Intel i7-9700K | 36 FPS | Open report |
| build-88 | runs with issues | AMD Radeon RX 7900 XTX / Not provided | Not provided | Open report |
| build-88 | playable | AMD Radeon RX 7900 XTX / Ryzen 9 3950X | 24–44 FPS | Open report |
| build-83 | runs with issues | AMD Radeon RX 9060 XT 16 GB / Intel i7-9700K | Not provided | Open report |
| build-75 | runs with issues | AMD Radeon RX 7900 XTX / Not provided | 12 FPS | Open report |
Problems or notes: CPU-bound performance was reported. The tester separately reported an incorrect near-white image with frame_gen and game_dlss_network enabled; setting both to false produced a correct image.
Problems or notes: The device was lost about two minutes after boot when the save loaded.
Problems or notes: Reported performance varied with settings; GPU accuracy Low, reactive flushing off, and asynchronous shaders on improved performance.
Problems or notes: The GPU device was lost when gameplay started.
Problems or notes: The 3D scene was black with only the HUD visible.
Current: build-93 (1 record); previous: build-88 (2 records).
Showing 181–190 of 275 reports
Known issues from Lichii sources
On Linux with AMD RX 9000-series graphics using RADV, an invalid SPIR-V fragment shader can cause a segfault during Vulkan graphics-pipeline construction during gameplay.
Recorded fix: Fixed in build 93 and later releases.
On AMD's proprietary Windows Vulkan driver, the intro could freeze while two compute shaders were optimized, taking 6–18 minutes; long graphics-pipeline builds can also cause substantial in-game stalls.
Recorded fix: Build 93 and later build the two identified compute shaders without driver optimization on AMD's proprietary Vulkan driver. The source says long graphics-pipeline builds are a separate matter and are not covered.
On earlier builds, small details such as leaves, pebbles, and grass flickered or appeared black with Low GPU accuracy and the split GPU thread enabled.
Recorded fix: Update to build 95 or later; the source attributes the fix to buffer usage tracking changes, with additional near-foliage fixes. EDEN_NX2_PERF_VERIFY=1 was an earlier workaround but was reported as no longer needed on build 95.
On Linux with AMD graphics, Fire Emblem: Fortune's Weave can crash after a black screen with VK_ERROR_DEVICE_LOST and a GPU reset.
On Windows 11, extracting a NUP to a path longer than 260 characters fails even when LongPathsEnabled is set. The issue reports a malformed longPathAware manifest entry as the probable cause.
AV1 cinematics are delayed, with audio playing faster.
A user reports a black screen with title music and unresponsive controls until shaders loaded; after entering gameplay, they reported severe glitches and lag, freezes lasting about 20 seconds during shader building, and a steady 18 FPS.
On an RX 6900 XT with AMD proprietary driver 2.0.353, the driver crashes while compiling shaders during gameplay; rejecting one shader hash does not prevent a subsequent crash at the same driver fault offset. The reject check may not help when the shader is already in the disk cache.
A user reports the frame rate drops to 2.5 FPS when shader loading begins, after the initial cutscene runs at 50–60 FPS.
The game cover/icon is missing among the collection covers when the emulator is opened with the game in the ROM path.
Showing 131–140 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
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.