The Legend of Zelda: Ocarina of Time
User reports include indefinite launching, white graphics, and a black screen in handheld mode or past the title screen. A separate report says it boots past the intro FMV in docked mode.
ゲーム互換性
遊びたいゲームはありますか? Lichii での動作や報告されている問題を確認し、試すビルドを選びましょう。
ゲームを探す
現在のデータには、ゲームと動作環境の組み合わせが 108 件、Lichii のレポートが 308 件あります。
ゲームが見つからない場合、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: Ocarina of Time, Zelda: Ocarina of Time, OoT, Zelda OoT, TLoZ: OoT
| Build | Status | GPU / CPU | FPS | Details |
|---|---|---|---|---|
| Not provided | playable | Not provided / Not provided | Not provided | Open report |
| Not provided | runs with issues | 1080 Ti / Ryzen 5600X | Not provided | Open report |
| Not provided | runs with issues | GTX 1050 Ti / 7th gen i5 | 18–27 FPS | Open report |
| Not provided | playable | RTX 3070 Ti / Ryzen 7 2700X | Not provided | Open report |
| build-95 (`nx2-build-95`) | runs with issues | RTX 4060 Laptop, 8 GB, 45 W max power limit / Intel Core i7-12650H (6P+4E, 16 threads) | 9.4–51.4 FPS | Open report |
| build 95 | runs with issues | Radeon 890M / Ryzen AI Z2 Extreme | 23–25 FPS | Open report |
| build 117 (PGO) | runs with issues | Radeon 890M / Ryzen AI Z2 Extreme | 42–44 FPS | Open report |
| nx2-build-95 | runs with issues | NVIDIA GeForce RTX 2070 / Intel Core i7-12700KF | Not provided | Open report |
| Not provided | not booting | NVIDIA GeForce RTX 3050 / Not provided | Not provided | Open report |
| build 88 and 93 | runs with issues | GTX 1060 6gb / Ryzen 5 5600 | Not provided | Open report |
Problems or notes: A commenter says everything works on their Mac with the latest main branch; hardware and build details are not stated.
Problems or notes: A commenter reports objects and doors failing to appear.
Problems or notes: A commenter reports invisible push blocks, making progress difficult.
Problems or notes: A commenter reports testing the draft shader warm-up and says first-visit freezes were gone. The comment gives no broader gameplay or session-duration evidence.
Problems or notes: User reports multi-second stalls while draws are held for unbuilt pipelines with async shaders enabled; in about 8 minutes, mean performance was 25.8 fps and six present windows had a maximum frame time over 1 s (worst 4.9 s). A fresh config used slow defaults and ran at 10–15 fps with stalls up to 8.9 s and blurry/pixelated Handheld resolution. Settings for the measured build-95 session were GPU accuracy Low, async shaders and async presentation enabled, Docked, 8 GB memory layout, and NVDEC GPU. The report also describes Frizti v3 behavior separately: it skipped draws with no pipeline, averaging 26.0 fps in 30-fps mode (range 16.4–30), with revisits at 30.0 fps and no frames over 100 ms.
Problems or notes: The intro, Deku Tree cutscene, and initial gameplay rendered correctly, but the game froze at 0 FPS when Navi passed the Kokiri guard on the path to the Deku Tree. The report mentions texture format asserts and Unmapped Device ReadBlock errors.
Problems or notes: The intro and cutscenes ran at 42–44 FPS and the game reached Kokiri Forest, but Unmapped Device ReadBlock errors and multi-second stalls were followed by a hard freeze before Navi reached the guard. The same errors occurred with memory layout set to both 12 GB and 4 GB.
Problems or notes: User reports that after the Kaepora Gaebora cutscene near Hyrule Castle, the area appears empty and foggy, Link falls through the world, and repeated void-outs prevent progression. Reported on Windows 11 25H2 in Handheld mode with Vulkan. The user says the issue reproduces 100% with the same save; listed configuration changes and disabling a built-in patch did not fix it.
Problems or notes: Crashes during boot about 9–13 seconds after launch, after presenting its first frame, at an unimplemented nx2:vi2 function 201. The same crash is reported on builds 93 and 95.
Problems or notes: A commenter reports missing textures in the Deku Tree after loading a save, across two game versions and builds 88 and 93. They also report that it worked the first time.
Current: build-117 (2 records); previous: build-116 (0 records).
Showing 171–180 of 308 reports
Known issues from Lichii sources
User reports include indefinite launching, white graphics, and a black screen in handheld mode or past the title screen. A separate report says it boots past the intro FMV in docked mode.
A user reported that Fortunes Weave skips pre-rendered videos, including the opening cut-scene.
A user reports a crash after brief rendering while loading on Windows 10.
A user reports infinite loading while loading on Windows 10.
On build 70 (286117c), the MSVC package reportedly aborted after about 133.8 seconds of gameplay with 0xC0000409; the MinGW PGO package reportedly aborted on the intro screen with the same offset.
A user reported GPU crashes when booting on Bazzite with Mesa 26.2.4; the report was later said to concern an older nx2 build.
DK appears all black during the cutscene when finding or collecting a banana, then returns to normal.
Washed-out, low-saturation colors with a purple/lavender haze at the normal camera angle; colors become nearly normal when looking straight down. A user reported the haze remained on build-70.
User reports the game crashes when the loading screen appears on Windows 10 with an AMD RX 6000 series or older graphics card.
Deku has black textures on some parts during the cinematic, with stuttering, bloom and artifacts when jumping. Dynamic FPS makes the game run too fast (about 2x speed); without it, gameplay is almost in slow motion.
Showing 241–250 of 361 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。テスト中に戻せるよう、動作するビルドも残しておいてください。
互換性について
ゲーム、動作状況、GPU、ビルドで絞り込み、ページの URL をコピーしてください。ゲームを指定したリンクを開くと、そのレポートカードが表示されます。
ほかのレポートで、メニューまで進めたか、プレイできたかを確認してください。ドライバーとレンダラーを控えて、 トラブルシューティングでゲーム名やエラーを検索してください。
ドライバーのバージョン、グラフィック設定、CPU 負荷、テストした場面によって結果が変わります。設定を変える前に、これらの条件を比べてください。
Lichii の公式 Issue トラッカーを利用してください。ゲーム名、ビルドタグ、ハードウェア、ドライバー、設定、結果を再現する手順を記載してください。