After: Dynamic FPS mod bundled and enabled by default; automatic patching is restricted to the supported game build and checks for patch conflicts.
build-83 → build-88
ゲーム互換性
遊びたいゲームはありますか? Lichii での動作や報告されている問題を確認し、試すビルドを選びましょう。
ゲームを探す
現在のデータには、ゲームと動作環境の組み合わせが 58 件、Lichii のレポートが 114 件あります。
ゲームが見つからない場合、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
| Build | Status | GPU / CPU | FPS | Details |
|---|---|---|---|---|
| nx2-build-83 | runs with issues | AMD RX 9000 series / Not provided | 41 FPS | Open report |
Problems or notes: User reports audio running ahead of video, cutting out and repeating during the opening cutscene, followed by a system freeze at the Deku Tree cutscene requiring a forced shutdown. Settings reported: Vulkan, GPU Mode Fast, Docked, Bilinear window adapting filter, and no anti-aliasing.
From build-83 to build-88: follow the gameplay changes described for these two builds.
After: Dynamic FPS mod bundled and enabled by default; automatic patching is restricted to the supported game build and checks for patch conflicts.
build-83 → build-88
Showing 61–61 of 61 reports
Known issues from Lichii sources
A half-resolution layer drawn by pixel shader c72b6ea746c00433 causes dark blotches and translucent patches over objects in reported scenes. Users traced the issue to an occlusion-depth copy being wiped by deferred clears before the layer samples it.
Recorded fix: A user-reported workaround is EDEN_NX2_REJECT_HASH=c72b6ea746c00433; it removes the blotches in tested scenes but removes the river's visible water surface. Another user described PR #185 as fixing the ordering issue, but did not provide a tested result for that fix.
The Deku Tree exterior cutscene can render black except for a small area around Navi; a user also reported an AMD graphics-driver crash while building graphics pipelines in that scene.
Users reported missing grass, ferns, and broadleaf vegetation, with associated haze or overexposure in Kokiri Forest. A user reported that a local build with listed rendering commits restored grass and ferns and removed heavy haze in one location; a later comment proposed PR #204 for stale occlusion-query reads, but did not report a test result for that PR.
A user reported river-water flicker depending on sun direction relative to the camera; the proposed link to lighting or light volumes was unconfirmed.
A user reported zero-format texture assertions, Unmapped Device ReadBlock errors, and flickering terrain and subtitles; causation was not established.
On AMD RDNA2 GPUs, the game may freeze during shader or pipeline building, sometimes with background audio continuing. A commenter also reports black-screen or shader-building hangs with asynchronous shader compilation enabled.
On AMD's proprietary Windows driver, two compute pipelines can take 6 to 18 minutes to compile during the intro, leaving the game at 0 FPS while audio continues. Rejecting the shader hashes avoids the wait but causes black areas in the intro, title, and castle scenes.
Recorded fix: Leave the game at the intro for about 20 minutes once so both pipelines finish and are cached; later boots reportedly pass the intro immediately until the driver or Lichii is updated. Alternatively, set `EDEN_NX2_REJECT_HASH=eff3ccbe1438679d,f9ea14a22394f5b1`; this avoids the wait but leaves parts of the picture black.
In the measurement-only experiment, disabling per-fence Preflushable downloads or batching downloads by 64 fences caused overexposure in Kokiri Forest.
A commenter reports that an experimental compute storage write-extent analysis reduced marked GPU-written data and fence copies while preserving correct auto-exposure. It was described as code on a user's branch, not as an upstream or validated release fix.
Static review and a separate research comment describe read-trap bookkeeping and dirty-state issues that can leave stale GPU-written data when per-fence downloads are disabled; proposed corrections and batching remain untested or local experiments.
Showing 21–30 of 98 issues
最近のリリースノート
ビルド build-88 · 記載なし
ビルド build-88 · 記載なし
ビルド build-88 · 記載なし
ビルド build-88 · Zelda: Ocarina of Time
ビルド build-83 · Ocarina of Time
ビルドの選び方
build-83 · 公開日: November 6, 2026
このビルドでは 12 件のファイルがダウンロード用に公開されています。
build-75 · 公開日: November 5, 2026
このビルドでは 12 件のファイルがダウンロード用に公開されています。
build-70 · 公開日: November 4, 2026
このビルドでは 12 件のファイルがダウンロード用に公開されています。
最新のダウンロード可能なリリースを試す: build-88。テスト中に戻せるよう、動作するビルドも残しておいてください。
互換性について
ゲーム、動作状況、GPU、ビルドで絞り込み、ページの URL をコピーしてください。ゲームを指定したリンクを開くと、そのレポートカードが表示されます。
ほかのレポートで、メニューまで進めたか、プレイできたかを確認してください。ドライバーとレンダラーを控えて、 トラブルシューティングでゲーム名やエラーを検索してください。
ドライバーのバージョン、グラフィック設定、CPU 負荷、テストした場面によって結果が変わります。設定を変える前に、これらの条件を比べてください。
Lichii の公式 Issue トラッカーを利用してください。ゲーム名、ビルドタグ、ハードウェア、ドライバー、設定、結果を再現する手順を記載してください。