The Legend of Zelda: Ocarina of Time
A user reports a black screen and around 2 FPS on macOS with build 95 on an Apple M1 Pro; shader compilation eventually finishes, but no title screen or gameplay is visible.
ゲーム互換性
Lichii Emulator のゲーム互換性
遊びたいゲームはありますか？ Lichii での動作や報告されている問題を確認し、試すビルドを選びましょう。
Latest recorded build
build-117
Published November 7, 2026
ゲームを探す
Lichii で動作するゲームを検索
現在のデータには、ゲームと動作環境の組み合わせが 108 件、Lichii のレポートが 308 件あります。
ゲームが見つからない場合、Lichii でのレポートがまだ掲載されていないということです。テストに失敗したという意味ではありません。
同じゲームの異なるバージョンは、プラットフォームの表示で見分けられます。
動作状況の見方： 「Unknown」は未判定、「Not booting」は起動しなかった、「Boots」は起動のみ確認、「Runs with issues」はプレイ中に問題が発生、「Playable」はテストでプレイを続けられたことを示します。
Compatibility results
Game Compatibility Results
Recorded performance
Performance by Build and Hardware
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.
Donkey Kong Bananza Reported platform: unknown
Also listed as: dkb
| Build | Status | GPU / CPU | FPS | Details |
|---|---|---|---|---|
| build-70 | playable | Not provided / Not provided | Not provided | Open report |
| Not provided | runs with issues | Not provided / 9900X | Not provided | Open report |
| 31 | runs with issues | RX 6600 / i5-12400 | Not provided | Open report |
| Not provided | runs with issues | 5070ti / 9800x3d | Not provided | Open report |
| nx2 build 65 (3bdd53d) | runs with issues | Sapphire nitro+ 7900XTX / 9800x3D | Not provided | Open report |
| Not provided | unknown | RX 9070 XT / Not provided | Not provided | Open report |
| Not provided | not booting | AMD RX 6000 series or older / Not provided | Not provided | Open report |
build-70 report
Statusplayable
GPUNot provided
CPUNot provided
DriverNot provided
Recorded FPSNot provided
Problems or notes: Runs well, though not at a locked 60 fps.
Not provided report
Statusruns with issues
GPUNot provided
CPU9900X
Driver615.74
Recorded FPSNot provided
Problems or notes: Purple screen when entering the game.
31 report
Statusruns with issues
GPURX 6600
CPUi5-12400
DriverNot provided
Recorded FPSNot provided
Problems or notes: Crashes when loading after the main menu. A commenter speculated that the issue involved shader cache; this was not confirmed.
Not provided report
Statusruns with issues
GPU5070ti
CPU9800x3d
Driver621.01
Recorded FPSNot provided
Problems or notes: The DK character appears all black during the banana-collection cutscene, then returns to normal. The reporter said the issue persisted when retested on build-70.
nx2 build 65 (3bdd53d) report
Statusruns with issues
GPUSapphire nitro+ 7900XTX
CPU9800x3D
Driver26.10.1
Recorded FPSNot provided
Problems or notes: A black rectangle appears in what should be a mini-example guide; the reporter says the issue also occurs on build 70.
Not provided report
Statusunknown
GPURX 9070 XT
CPUNot provided
DriverNot provided
Recorded FPSNot provided
Problems or notes: The issue's reproduction text says it has worse FPS than most other forks; no specific FPS or separate test details are given.
Not provided report
Statusnot booting
GPUAMD RX 6000 series or older
CPUNot provided
DriverNot provided
Recorded FPSNot provided
Problems or notes: User reports that the game crashes when the loading screen appears on Windows 10.
Related game issues
- [Crash] (open)
- [Crash] Bananza runs at ~57 fps then aborts silently, 0xC0000409 at +0x2ecd3bd (closed)
- Black DK when finding banana (closed)
- [Crash] rx 6800xt all emulators crash on loading screen (open)
- [VBug] Build 93 finaly has no major visual errors but has poor performance 9070xt (open)
- [UIBug] Bananza — build 93 (open)
- [Crash] donkey kong and ocarina crash on AMD 6800xt (open)
- Donkey Kong Bananza (040074A01BF12000): fatal 2111-3604 right after a VP9 video reaches end of stream (nx2:vdecsvc) (closed)
- [GBug] Donkey Kong Bananza locked at 20 fps (open)
- Donkey kong bananza Crash loading (closed)
- [VBug] Shadow artifacts (closed)
- [GBug] Donkey kong bananza, black rectangle (closed)
- Donkey Kong Bananza: terrain missing (white/black) on builds 70 and 75, renders correctly on build 65 (open)
- donkey kong bananza purple screen issue (closed)
- Release note: Crashes after the continue-game loading screen.
- Release note: 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.
- Release note: DK appears all black during the cutscene when finding or collecting a banana, then returns to normal.
- Release note: User reports the game crashes when the loading screen appears on Windows 10 with an AMD RX 6000 series or older graphics card.
- Release note: The issue says FPS is worse than on most other forks.
- Release note: On build 93, FPS fluctuates approximately between 20 and 60, with frequent periods around 30 and drops to 25–28 FPS in the Dragon Layer; GameSir G7 Pro rumble can be excessive, occur without an obvious trigger, or continue longer than expected.
- Release note: User reports a crash when loading a save on AMD RX 6000 series or older under Windows 11.
- Release note: A VP9 video reaching end of stream triggers error 2111-3604 and freezes emulation; the video panel appears as a solid yellow box in stable-1.0.0.
- Release note: User reports the game is locked at 20 FPS, including menus and title screen, on Windows 11.
- Release note: Crashes when loading after the main menu on build 31.
- Release note: User reports the picture is covered with artifacts, especially on shadows.
- Release note: A black rectangle appears in what should be a mini-example guide; the reporter says it also occurs on build 70.
- Release note: On Windows builds 70 and 75, terrain/world renders solid white while the HUD and characters still render. On build 75, EDEN_NX2_RESETFIX=0 changes the ground to black with no texture or lighting.
- Release note: Purple screen after starting the game and entering it.
Compared with Previous Build
Current: build-70 (2 records); previous: build-65 (0 records).
Donkey Kong Bananza Reported platform: Windows x86_64
| Build | Status | GPU / CPU | FPS | Details |
|---|---|---|---|---|
| nx2-20261031 | boots | Not provided / Not provided | Not provided | Open report |
nx2-20261031 report
Statusboots
GPUNot provided
CPUNot provided
DriverNot provided
Recorded FPSNot provided
Problems or notes: Completed a 180-second GUI check; long-term memory stability and broader game compatibility remain unverified.
Related game issues
- [Crash] (open)
- [Crash] Bananza runs at ~57 fps then aborts silently, 0xC0000409 at +0x2ecd3bd (closed)
- Black DK when finding banana (closed)
- [Crash] rx 6800xt all emulators crash on loading screen (open)
- [VBug] Build 93 finaly has no major visual errors but has poor performance 9070xt (open)
- [UIBug] Bananza — build 93 (open)
- [Crash] donkey kong and ocarina crash on AMD 6800xt (open)
- Donkey Kong Bananza (040074A01BF12000): fatal 2111-3604 right after a VP9 video reaches end of stream (nx2:vdecsvc) (closed)
- [GBug] Donkey Kong Bananza locked at 20 fps (open)
- Donkey kong bananza Crash loading (closed)
- [VBug] Shadow artifacts (closed)
- [GBug] Donkey kong bananza, black rectangle (closed)
- Donkey Kong Bananza: terrain missing (white/black) on builds 70 and 75, renders correctly on build 65 (open)
- donkey kong bananza purple screen issue (closed)
- Release note: Crashes after the continue-game loading screen.
- Release note: 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.
- Release note: DK appears all black during the cutscene when finding or collecting a banana, then returns to normal.
- Release note: User reports the game crashes when the loading screen appears on Windows 10 with an AMD RX 6000 series or older graphics card.
- Release note: The issue says FPS is worse than on most other forks.
- Release note: On build 93, FPS fluctuates approximately between 20 and 60, with frequent periods around 30 and drops to 25–28 FPS in the Dragon Layer; GameSir G7 Pro rumble can be excessive, occur without an obvious trigger, or continue longer than expected.
- Release note: User reports a crash when loading a save on AMD RX 6000 series or older under Windows 11.
- Release note: A VP9 video reaching end of stream triggers error 2111-3604 and freezes emulation; the video panel appears as a solid yellow box in stable-1.0.0.
- Release note: User reports the game is locked at 20 FPS, including menus and title screen, on Windows 11.
- Release note: Crashes when loading after the main menu on build 31.
- Release note: User reports the picture is covered with artifacts, especially on shadows.
- Release note: A black rectangle appears in what should be a mini-example guide; the reporter says it also occurs on build 70.
- Release note: On Windows builds 70 and 75, terrain/world renders solid white while the HUD and characters still render. On build 75, EDEN_NX2_RESETFIX=0 changes the ground to black with no texture or lighting.
- Release note: Purple screen after starting the game and entering it.
Compared with Previous Build
Fast Fusion Reported platform: Windows 11
| Build | Status | GPU / CPU | FPS | Details |
|---|---|---|---|---|
| release-binaries #80 | unknown | NVIDIA RTX 50 series / Not provided | 23–24 FPS | Open report |
release-binaries #80 report
Statusunknown
GPUNVIDIA RTX 50 series
CPUNot provided
DriverNot provided
Recorded FPS23–24 FPS
Problems or notes: User reports that the game runs at a maximum of 23–24 FPS.
Related game issues
Compared with Previous Build
Fire Emblem Reported platform: unknown
| Build | Status | GPU / CPU | FPS | Details |
|---|---|---|---|---|
| build-70 | runs with issues | NVIDIA RTX 40 series / Not provided | Not provided | Open report |
build-70 report
Statusruns with issues
GPUNVIDIA RTX 40 series
CPUNot provided
DriverNot provided
Recorded FPSNot provided
Problems or notes: A user reported that Fortunes Weave skips pre-rendered videos, including the opening cut-scene, and proceeds to the in-engine scene.
Related game issues
- DLSS does not work in FE Fortune's Weave - no Game DLSS Network detection (open)
- [Crash] VK_ERROR_DEVICE_LOST, FEFW (Linux + AMD) (open)
- [GBug] Fire Emblem Fortunes Weave - FMVs Skipped/Do not play. (closed)
- Screen Shaking (Fire Emblem Fortune's Weave) (closed)
- Release note: A user reports that DLSS replacement does not detect the game's DLSS evaluation in Fire Emblem: Fortune's Weave: no Game DLSS network or NVIDIA DLSS (Streamline) line appears, while guest tensor operations run on cooperative matrices and GPU usage is high.
- Release note: 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.
- Release note: A user reported that Fortunes Weave skips pre-rendered videos, including the opening cut-scene.
- Release note: Screen and camera shaking during play on build 65.
Compared with Previous Build
Current: build-70 (1 record); previous: build-65 (1 record).
Showing 11–20 of 308 reports
Known issues from Lichii sources
Known Game Issues
Other / not listed
A user reports that in build 93 the controller periodically takes over and moves the character into a wall, roughly every 30 seconds.
Ocarina of Time
During movies, including the title-screen background, the six movie audio voices can pause while the picture continues, resulting in late or silent audio. The issue varied between sessions and was also reported on builds without the movie-sync patch.
Zelda Ocarina remake
Town vegetation and small clutter render at a distance but disappear when approached; reports also mention tree leaves vanishing up close and changing shadows.
green-hat game
ZL input is not detected during the shield tutorial, leaving the tutorial stuck in a loop.
Recorded fix: Fixed in build 95.
Splatoon Raiders
User reports pixelated, blurry graphics and somewhat slow FPS on integrated AMD graphics in Windows 11.
Other / not listed
The user reports shader-cache compilation problems, stuttering, Hyrule Field visual bugs and frame-rate instability, and occasional cinematic cutscene audio bugs. A commenter reports that the shader pipeline cache does not persist across runs and that cutscene music is missing or mismatched.
The Legend of Zelda: Ocarina of Time (Switch 2)
On an AMD RX 6750 XT, the emulator freezes at “Building 9 shaders” after launching; background audio continues and the game does not progress.
Ocarina of Time
On an RX 6650 XT setup, asynchronous shader compilation on was associated with a black screen or a freeze while building shaders; asynchronous shader compilation off allowed the game to load and play on that setup.
Ocarina of Time
A commenter reports a freeze with background music on an AMD Ryzen 5 5500U with Radeon Graphics, regardless of the asynchronous shader compilation toggle.
Showing 131–140 of 361 issues
最近のリリースノート
最新ビルドでの互換性の変化
ビルド build-117 · Ocarina of Time
Fixed a crash during shader building on Windows drivers for RX 6000 (RDNA2), RX 5000 (RDNA1), Vega, and Polaris cards. The faster matrix path now runs only on RDNA3 and newer.
ビルド build-116 · Zelda: Ocarina of Time
Ocarina of Time is described as very stable; foliage and Hyrule Field grass rendering are fixed, and many users get 60+ fps.
ビルド build-116 · Zelda: Ocarina of Time
NVIDIA DLSS Super Resolution can replace the game's own upscaler on RTX cards; the setting is experimental.
ビルド build-116 · Zelda: Ocarina of Time
A new option turns off the game's sharpening anti-aliasing; the default Game setting behaves as before, and DLSS takes priority if both are enabled.
ビルド build-116 · Mario Tennis Fever
The game runs fully at 60 fps, and texture glitches are fixed.
ビルドの選び方
どのビルドを使えばいい？
上でゲームを選ぶと、動作テスト済みのビルドのうち、ダウンロードできるものを確認できます。ゲームを選ぶ前は、最新の公開ファイルを使い、リリースノートを確認してください。
最新のダウンロード可能なリリースを試す： build-117。テスト中に戻せるよう、動作するビルドも残しておいてください。
互換性について
ゲーム互換性に関するよくある質問
この絞り込み条件でゲームを共有するには？
ゲーム、動作状況、GPU、ビルドで絞り込み、ページの URL をコピーしてください。ゲームを指定したリンクを開くと、そのレポートカードが表示されます。
画面が真っ黒になったら何を試せばいい？
ほかのレポートで、メニューまで進めたか、プレイできたかを確認してください。ドライバーとレンダラーを控えて、 トラブルシューティングでゲーム名やエラーを検索してください。
同じ GPU で結果が異なるのはなぜ？
ドライバーのバージョン、グラフィック設定、CPU 負荷、テストした場面によって結果が変わります。設定を変える前に、これらの条件を比べてください。
まだ掲載されていない結果を報告するには？
Lichii の公式 Issue トラッカーを利用してください。ゲーム名、ビルドタグ、ハードウェア、ドライバー、設定、結果を再現する手順を記載してください。