ゲーム互換性
遊びたいゲームはありますか？ 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: OoT, Ocarina of Time, OOT REMAKE
| Build | Status | GPU / CPU | FPS | Details |
|---|---|---|---|---|
| build-93 | boots | AMD Radeon RX 7900 XTX (RADV) / Intel Core i7-11700K | Not provided | Open report |
Problems or notes: Not provided
Current: build-93 (3 records); previous: build-88 (0 records).
| Build | Status | GPU / CPU | FPS | Details |
|---|---|---|---|---|
| build-93 | runs with issues | AMD Radeon RX 9070 XT / Not provided | Not provided | Open report |
Problems or notes: Severe bright pink, cyan, and white lines appear along mountain silhouettes, especially where mountains meet the sky, in Kakariko Village. Shader compilation continues during gameplay, especially when moving or rotating the camera.
Current: build-93 (1 record); previous: build-88 (0 records).
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 |
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.
Current: build-93 (1 record); previous: build-88 (2 records).
Also listed as: OoT, Ocarina of Time
| Build | Status | GPU / CPU | FPS | Details |
|---|---|---|---|---|
| build-93 | runs with issues | RTX 5070 Laptop / i7-13650HX | Not provided | Open report |
| build-93 | runs with issues | RX 5700 (RDNA1) / Not provided | 14–24 FPS | Open report |
| build-93 | runs with issues | RX 7900XT / Ryzen 7 5700X3D | 25–55 FPS | Open report |
| build-93 | runs with issues | RX 9070 XT / Ryzen 7 9800X3D | 14–37 FPS | Open report |
Problems or notes: Local clang-cl Release nx2 build at 91d1aada6, not PGO. GPU accuracy High prevented GPU thread splitting and ran the work on one busy GPU thread. With GPU mode Fast, async shaders and async presentation on, and NVDEC GPU, splitting was enabled; the reporter notes the second run had a warmer shader cache, so the performance difference is not directly comparable. Profiling also showed GPU idle waits and long hitches while native pipelines were built.
Problems or notes: Renders and runs without crash, device loss, or fence timeouts. Commenter reports 22–24 FPS indoors and 14–15 FPS in Kokiri Forest, with outdoor performance described as uncomfortable.
Problems or notes: Commenter reports stable 25–30 FPS and occasional indoor spikes around 55 FPS; no errors, crashes, or timeouts.
Problems or notes: Boots to title and reaches gameplay without crashes or driver timeouts. Reported approximately 18 FPS on defaults, 17 FPS with async shaders on and GPU accuracy Normal, 14 FPS with async shaders on and GPU accuracy High, and approximately 29 FPS with defaults plus the stated logging, process-priority, and Xbox Game Bar capture changes in Kokiri Forest; intro cutscenes run 32–37 FPS. Gameplay is reported in slow motion. Heavy bloom and overexposure occur in bright areas, and the Great Deku Tree appears as a dark silhouette in its intro scene. One Lichii thread reaches 99% of a core.
Current: build-93 (4 records); previous: build-88 (1 record).
| Build | Status | GPU / CPU | FPS | Details |
|---|---|---|---|---|
| build-93 | runs with issues | RX 9060 XT 16 GB / i7-9700K | 19–36 FPS | Open report |
Problems or notes: A user reports that frame_gen and game_dlss_network enabled caused a near-white presented frame; setting both to false produced a correct image. White flashes were associated with async_presentation=true; async_presentation=false reduced white pixels in a 40-frame capture to 0.2% but lowered performance to about 19-25 FPS in a heavy Kokiri scene. The approximately 36 FPS result required async presentation, which flashed.
Current: build-93 (1 record); previous: build-88 (0 records).
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).
Also listed as: OoT, Ocarina of Time
| Build | Status | GPU / CPU | FPS | Details |
|---|---|---|---|---|
| build-93 | boots | RX 9070 XT / Ryzen 7 7800X3D | Not provided | Open report |
Problems or notes: A commenter says video worked on build 93 with the same configuration, keys, firmware, and game files used for build 95.
Current: build-93 (1 record); previous: build-88 (0 records).
Showing 21–30 of 35 reports
Known issues from Lichii sources
On Windows 11, connecting an official Nintendo Switch Pro Controller while Lichii is open reportedly floods the host OS with phantom inputs, making desktop mouse clicks unresponsive and keyboard typing erratic. Unplugging the controller reportedly restores normal input.
With Dual Joy-Cons, the game remains on the “Playing with 1 Joy-Con” screen and reports a lost connection, preventing a two-player motion game from starting. The issue reporter's log includes an unsupported controller type disconnection and a Joy-Con sub-command timeout.
Walls and objects are missing/not rendered inside the Deku tree.
The official PGO artifact of build-80 / nx2-latest crashed in dynarmic with Unhandled SIGSEGV after 2-10 minutes on the reporting machine; another report found a PGO AppImage produced audio but no video output.
White flashes were reported before PR #345 in the Deku Tree interior; the sky/lighting colour result from a separate misaligned 64/128-bit SSBO split fix was not verified.
Recorded fix: Use a local non-PGO build with PR #345 merged; the reporter confirmed white flashes were gone after several minutes in the Deku Tree interior.
In a Windows AMD-driver follow-up on Frizti v3, performance was about 20 fps in a busy view and about 60 fps looking at the floor; the reporter said keeping float16 on improved the busy-view result from about 20 to 24-25 fps.
Recorded fix: The reporter found that keeping float16 on improved the measured busy-view performance; this is a user-reported workaround.
User reports heavily distorted speech, music, and effects (“robot voice”) on build 70. Comments clarify that the approximately 0.7032 accepted/copied ratio reflects retries rather than lost samples; possible causes discussed include emulated time running ahead of wall time or slow host audio draining, but the cause is not confirmed.
On a GPU without VK_EXT_mesh_shader, mesh-shader draws may be skipped, resulting in missing scene geometry. The reported log labels skipped draws as "no pipeline" and caps the warning entries at 64.
Plants and bushes in the Castle appear dead up close, while bushes render correctly at a distance.
On Linux, the game froze near the title screen, followed by pixel artefacts and a system crash.
Recorded fix: The user reported that EDEN_NX2_NO_MESH=1 allowed the game to reach the menus, but Grand Prix did not start successfully.
Showing 181–190 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 トラッカーを利用してください。ゲーム名、ビルドタグ、ハードウェア、ドライバー、設定、結果を再現する手順を記載してください。