Starfox
A user reports repeated Unmapped Write64 errors, possible audio popping, and an emulation crash when closing the game.
ゲーム互換性
遊びたいゲームはありますか? Lichii での動作や報告されている問題を確認し、試すビルドを選びましょう。
ゲームを探す
現在のデータには、ゲームと動作環境の組み合わせが 76 件、Lichii のレポートが 175 件あります。
ゲームが見つからない場合、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 |
|---|---|---|---|---|
| Not provided | runs with issues | RX 6650 XT (RDNA2) / i5-10400F | 25–27 FPS | Open report |
| nx2 `5a50f50e0b` (official PGO artifact of build-80 and local non-PGO build of nx2-latest) | runs with issues | AMD RX 9070 XT (RDNA4, 16 GB) / Ryzen 7 5800X3D (8C/16T), 32 GB RAM | 28–35 FPS | Open report |
| Not provided | runs with issues | AMD RX 9070 XT / Not provided | Not provided | Open report |
| Not provided | playable | RTX 5090 / Not provided | 40–60 FPS | Open report |
| Not provided | unknown | AMD 7600 / Not provided | Not provided | Open report |
| Not provided | runs with issues | RX 9070 XT / Not provided | 10–60 FPS | Open report |
| Not provided | unknown | intel arc b580 / Not provided | 10 FPS | Open report |
| 95 | not booting | AMD RX 9000 series / Not provided | Not provided | Open report |
Problems or notes: A user comment reports that with three shaders built unoptimized, the intro plays and the game reaches Kokiri Forest, with cutscenes at about 25 to 27 FPS. With `EDEN_NX2_NOOPT_SHADERS=all`, it ran at about 16 to 17 FPS. With asynchronous shader compilation on, this build showed a black screen with audio or stayed at “Loading Shaders” at 0 FPS; the user had not waited long enough to determine whether it would finish.
Problems or notes: User reports gameplay at 28–35 fps with 31–36 ms frame time and no saturated thread. The PGO artifact crashes in dynarmic with Unhandled SIGSEGV after 2–10 minutes on this machine; a local non-PGO build was stable over several sessions.
Problems or notes: A commenter reports approximately 3 minutes of gameplay before a black screen, driver crash, and crash to desktop.
Problems or notes: Gameplay testing in Kokiri Forest reported no crashes; normal game speed was below 60 FPS with #216. GPU accuracy was Low.
Problems or notes: A commenter reports having the same issue without further details.
Problems or notes: Comments conflict: one reports 50–60 FPS in Kokiri Forest and Deku Tree on Linux using default/auto/safe/accurate/normal settings, Docked mode, and 1x resolution; another reports at most 25 FPS in open areas and 60 FPS in dungeons, and says performance is poor. A further comment says open areas are generally below 45 FPS while shaders are not loading and suggests Windows performance may be worse.
Problems or notes: User reports the game runs at 10 FPS.
Problems or notes: The reporter says the game hangs on a black screen while outputting normal audio. They report it used to boot on 88 with launch parameters, but no longer does. A commenter reports no video output on build 95 after video output on build 93, and another says Docked Mode with Accurate GPU loads the main menu but audio gets issues again.
Current: build-93 (1 record); previous: build-88 (1 record).
Also listed as: OoT
| Build | Status | GPU / CPU | FPS | Details |
|---|---|---|---|---|
| nx2 @ 27226d2 plus two measurement-only commits | runs with issues | RTX 5060 Laptop (8 GB) / Ryzen AI 9 365 | Not provided | Open report |
Problems or notes: In Kokiri Forest, disabling per-fence Preflushable downloads or batching them by 64 fences caused overexposure. Default per-fence downloads preserved correct exposure. The report measures GPU back-thread draws/s, not game FPS.
Also listed as: OoT
| Build | Status | GPU / CPU | FPS | Details |
|---|---|---|---|---|
| Not provided | unknown | RTX 3080 Ti / i9-12900K | 46–47.8 FPS | Open report |
Problems or notes: A user comment reports same-binary, 300-second headless-harness measurements in Kokiri Forest: median FPS was 46.0 in Full mode and 47.8 in Auto mode. The comment reports correct auto-exposure in both modes and identifies readback bandwidth and stale-constants flicker as visible concerns; no sustained gameplay validation is stated.
Showing 101–110 of 114 reports
Known issues from Lichii sources
A user reports repeated Unmapped Write64 errors, possible audio popping, and an emulation crash when closing the game.
Terrain is visible through solid objects after getting past the intro.
Users report crashes before the training mission begins and during the campaign.
Weird artifacts, especially on shadows.
User reports a black screen while loading in Build 65.
A black rectangle appears in a mini-example guide; the reporter says it persists on build-70.
Freezes while menu preview videos play on build 65. A comment reports a custom kirby-test build log showing the game aborting (2162-0001) during menu videos.
User-reported reproducible freeze when walking deeper into the pot room in Hyrule Castle Town, near the guard.
On Adreno 740 with Turnip, large native compute-shader pipelines can keep Vulkan pipeline-builder workers busy, consume substantial memory, and result in a black screen; some tests also reported GPU hangs or device loss.
Black screen or intermittent black-screen flashes during gameplay and GDT; additional reports describe distorted docked rendering, overly bright and low-resolution handheld rendering, and intro audio ahead of video.
Showing 151–160 of 188 issues
最近のリリースノート
ビルド build-94 · Ocarina of Time
ビルド build-94 · 記載なし
ビルド build-94 · 記載なし
ビルド build-94 · 記載なし
ビルド build-94 · 記載なし
ビルドの選び方
build-75 · 公開日: November 5, 2026
このビルドでは 12 件のファイルがダウンロード用に公開されています。
最新のダウンロード可能なリリースを試す: build-94。テスト中に戻せるよう、動作するビルドも残しておいてください。
互換性について
ゲーム、動作状況、GPU、ビルドで絞り込み、ページの URL をコピーしてください。ゲームを指定したリンクを開くと、そのレポートカードが表示されます。
ほかのレポートで、メニューまで進めたか、プレイできたかを確認してください。ドライバーとレンダラーを控えて、 トラブルシューティングでゲーム名やエラーを検索してください。
ドライバーのバージョン、グラフィック設定、CPU 負荷、テストした場面によって結果が変わります。設定を変える前に、これらの条件を比べてください。
Lichii の公式 Issue トラッカーを利用してください。ゲーム名、ビルドタグ、ハードウェア、ドライバー、設定、結果を再現する手順を記載してください。