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.
ゲーム互換性
遊びたいゲームはありますか? Lichii での動作や報告されている問題を確認し、試すビルドを選びましょう。
ゲームを探す
現在のデータには、ゲームと動作環境の組み合わせが 98 件、Lichii のレポートが 275 件あります。
ゲームが見つからない場合、Lichii でのレポートがまだ掲載されていないということです。テストに失敗したという意味ではありません。
同じゲームの異なるバージョンは、プラットフォームの表示で見分けられます。
動作状況の見方: 「Unknown」は未判定、「Not booting」は起動しなかった、「Boots」は起動のみ確認、「Runs with issues」はプレイ中に問題が発生、「Playable」はテストでプレイを続けられたことを示します。
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: OoT, Ocarina of Time, OOT REMAKE
| Build | Status | GPU / CPU | FPS | Details |
|---|---|---|---|---|
| a7a281757da390ce45070e772784e0333831bb25 | runs with issues | NVIDIA GeForce GTX 1080 / AMD Ryzen 9 3900X | Not provided | Open report |
| build-95 | runs with issues | RTX 4070 Ti SUPER / Not provided | Not provided | Open report |
| 95 | not booting | AMD Radeon RX 7900 XTX (RADV) / Intel Core i7-11700K | 0 FPS | Open report |
| Build 95 | not booting | AMD Radeon RX 5700 XT (RADV NAVI10) / AMD Ryzen 5 3600 6-Core Processor | Not provided | Open report |
| Build 95 | not booting | NVIDIA GeForce RTX 3050 Laptop GPU / i5-12500H | Not provided | Open report |
| nx2 @ 89440b29a9 | runs with issues | Not provided / Not provided | Not provided | Open report |
Problems or notes: Missing leaves, foliage, walls, textures, and other geometry. The report says attempted recompilation and builds 78, 88, 92, Fritzi v2, and perf/Fritzi-Intergrated did not resolve the issue; comments report that #395, #434, and #430 did not restore the geometry.
Problems or notes: Large flat red patches appear across the wet stream bed by the road from Castle Town Market to Hyrule Castle. Another user later reported that stream as clean with their build, attributing the earlier difference possibly to missing #432 and #351; this report's setup used build-95.
Problems or notes: Stalls at a black screen; repeated native MME macro execution failures are reported. Enabling compute pipelines, clearing pipeline caches, and disabling implicit Vulkan layers did not resolve the issue.
Problems or notes: A user-provided build-95 log shows the game loading, followed by a compute pipeline compilation error and an unhandled SIGSEGV. The user later supplied crash details indicating a null-pointer dereference. The log identifies KDE neon User Edition as the host OS.
Problems or notes: Black screen at the intro video after the loading shaders screen; music continues, FPS counter stays at 0, and GPU channels wait on unreleased semaphores. Build 93 reaches gameplay on the same machine. Two other users report the same build 95 hang on Linux with NVIDIA RTX 3060 and RTX 3090 systems. Two users say EDEN_NX2_SPLIT=1 makes the game work.
Problems or notes: User reports that motion controls are affected: Motion 1/Motion 2 mapping does not detect shaking, and gyro/accelerometer input stops after the controller reconnects or after a few seconds with Steam running.
Current: build-93 (3 records); previous: build-88 (0 records).
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 |
|---|---|---|---|---|
| 75 (`nx2-build-75`) | runs with issues | AMD RX 7000 series (Radeon RX 7600, RADV 26.2.5, Vulkan 1.4.354) / Not provided | Not provided | Open report |
Problems or notes: During the AV1 intro cutscene, the video area is solid green while audio and subtitles work. The report says frames decode at 60 fps, but this is not a gameplay FPS measurement.
Also listed as: OoT, Zelda, Ocarina of Time
| Build | Status | GPU / CPU | FPS | Details |
|---|---|---|---|---|
| build-93 | boots | RX 9060XT 16GB / Ryzen 5 7600 | Not provided | Open report |
Problems or notes: A commenter reports that starting with Accurate GPU enabled loaded the main menu; audio had issues. They say settings could sometimes be changed back, but the issue could recur.
Current: build-93 (1 record); previous: build-88 (0 records).
Showing 11–20 of 24 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
最近のリリースノート
ビルド build-117 · Ocarina of Time
ビルド build-116 · Zelda: Ocarina of Time
ビルド build-116 · Zelda: Ocarina of Time
ビルド build-116 · Zelda: Ocarina of Time
ビルド build-116 · Mario Tennis Fever
ビルドの選び方
build-117 · 公開日: November 7, 2026
このビルドでは 12 件のファイルがダウンロード用に公開されています。
最新のダウンロード可能なリリースを試す: build-117。テスト中に戻せるよう、動作するビルドも残しておいてください。
互換性について
ゲーム、動作状況、GPU、ビルドで絞り込み、ページの URL をコピーしてください。ゲームを指定したリンクを開くと、そのレポートカードが表示されます。
ほかのレポートで、メニューまで進めたか、プレイできたかを確認してください。ドライバーとレンダラーを控えて、 トラブルシューティングでゲーム名やエラーを検索してください。
ドライバーのバージョン、グラフィック設定、CPU 負荷、テストした場面によって結果が変わります。設定を変える前に、これらの条件を比べてください。
Lichii の公式 Issue トラッカーを利用してください。ゲーム名、ビルドタグ、ハードウェア、ドライバー、設定、結果を再現する手順を記載してください。