Zelda: Ocarina of Time
Outdoor areas have far too much fog and glow compared with console; performance is about 12–22 fps on a Ryzen 5900X with an RTX 3080, and three rare shaders remain unsupported.
Compatibilité des jeux
Compatibilité des jeux avec Lichii Emulator
Vous avez un jeu en tête ? Voyez comment il tourne dans Lichii, repérez les problèmes et choisissez une version à essayer.
Latest recorded build
build-88
Pre-release
Published November 6, 2026
Trouver un jeu
Rechercher des jeux compatibles avec Lichii
Les données actuelles comptent 58 entrées par jeu et environnement, et 114 rapports sur Lichii.
Un jeu manque ? Un résultat vide indique qu’aucun rapport sur ce jeu n’est encore répertorié pour Lichii. Cela ne signifie pas que le jeu a échoué à un test.
Consultez la plateforme indiquée pour distinguer les différentes versions d’un jeu.
Signification des statuts : « Unknown » : aucune conclusion. « Not booting » : le jeu ne démarre pas. « Boots » : seul le démarrage a été constaté. « Runs with issues » : des problèmes surviennent en jeu. « Playable » : la personne ayant testé le jeu a pu continuer à jouer.
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.
Starfox Reported platform: Windows 11
| Build | Status | GPU / CPU | FPS | Details |
|---|---|---|---|---|
| Lichii nx2 build 75 (c9ebb5c) | runs with issues | NVIDIA RTX 40 series / Not provided | Not provided | Open report |
Lichii nx2 build 75 (c9ebb5c) report
Statusruns with issues
GPUNVIDIA RTX 40 series
CPUNot provided
DriverNot provided
Recorded FPSNot provided
Problems or notes: Console spam of Unmapped Write64 errors; the reporter believes these may cause audio popping. Closing the game appears to cause an emulation crash.
Related game issues
- [GBug] StarFox: nx2_sysmix accepts a constant 70.32% of mixer output, so audio plays as "robot voice" (open)
- [Crash] StarFox, Device loss occurred! (open)
- [Crash] Starfox is crashing right before the training mission begins. I got it to pass one time havent been able to get it work again. (open)
- [GBug] Starfox - Unmapped write64 error spam in console (open)
- Release note: Users report crashes before the training mission begins and during the campaign.
- Release note: A user reports repeated Unmapped Write64 errors, possible audio popping, and an emulation crash when closing the game.
Compared with Previous Build
Star Fox Reported platform: unknown
| Build | Status | GPU / CPU | FPS | Details |
|---|---|---|---|---|
| build-75 | runs with issues | NVIDIA RTX 50 series / Not provided | Not provided | Open report |
| build-75 | runs with issues | Not provided / Not provided | 60 FPS | Open report |
| build-70 | runs with issues | Not provided / Not provided | ?–30 FPS | Open report |
build-75 report
Statusruns with issues
GPUNVIDIA RTX 50 series
CPUNot provided
DriverNot provided
Recorded FPSNot provided
Problems or notes: The emulator closes about a minute after gameplay begins.
build-75 report
Statusruns with issues
GPUNot provided
CPUNot provided
DriverNot provided
Recorded FPS60 FPS
Problems or notes: On RTX 50-series GPUs, the GPU device can be lost after a scene change.
build-70 report
Statusruns with issues
GPUNot provided
CPUNot provided
DriverNot provided
Recorded FPS?–30 FPS
Problems or notes: Gameplay is capped at about 30 fps despite the game asking for 60. On RTX 50-series GPUs (5070 Ti, 5090), the GPU device can be lost shortly after a scene change.
Related game issues
- [GBug] StarFox: nx2_sysmix accepts a constant 70.32% of mixer output, so audio plays as "robot voice" (open)
- [Crash] StarFox, Device loss occurred! (open)
- Release note: On RTX 50-series GPUs, the GPU device can still be lost after a scene change.
- Release note: Gameplay is capped at about 30 fps, even though the game asks for 60.
- Release note: On RTX 50-series GPUs (5070 Ti, 5090), the GPU device can be lost shortly after a scene change.
- Release note: 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.
- Release note: The emulator closes about a minute after gameplay begins on Windows 11 with an NVIDIA RTX 50 series GPU.
Compared with Previous Build
Current: build-75 (2 records); previous: build-70 (1 record).
Star Fox Reported platform: Linux AppImage (PGO)
| Build | Status | GPU / CPU | FPS | Details |
|---|---|---|---|---|
| Lichii nx2 build 70 (`286117c`) | runs with issues | integrated RDNA2, RADV, reports as `GFX1013` / AMD BC-250 (Oberon APU), 7 cores / 14 threads, AVX2 + FMA | Not provided | Open report |
Lichii nx2 build 70 (`286117c`) report
Statusruns with issues
GPUintegrated RDNA2, RADV, reports as `GFX1013`
CPUAMD BC-250 (Oberon APU), 7 cores / 14 threads, AVX2 + FMA
DriverNot provided
Recorded FPSNot provided
Problems or notes: User reports heavily distorted speech, music, and effects (“robot voice”). Comments clarify that the approximately 0.7032 accepted/copied ratio reflects retries, not audio loss at that point; they discuss possible timebase or host-drain causes without confirming which applies. The user also says build 75 does not reach gameplay, instead hitting a guest Userspace PANIC (`debug_buffer_err_code=40299`) about 29 seconds in and presenting a static black frame at 59.9 FPS.
Related game issues
- [GBug] StarFox: nx2_sysmix accepts a constant 70.32% of mixer output, so audio plays as "robot voice" (open)
- [Crash] StarFox, Device loss occurred! (open)
- Release note: On RTX 50-series GPUs, the GPU device can still be lost after a scene change.
- Release note: Gameplay is capped at about 30 fps, even though the game asks for 60.
- Release note: On RTX 50-series GPUs (5070 Ti, 5090), the GPU device can be lost shortly after a scene change.
- Release note: 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.
- Release note: The emulator closes about a minute after gameplay begins on Windows 11 with an NVIDIA RTX 50 series GPU.
Compared with Previous Build
The Legend of Zelda: Ocarina of Time Reported platform: Windows
| Build | Status | GPU / CPU | FPS | Details |
|---|---|---|---|---|
| build-83 | runs with issues | AMD Radeon RX 9060 XT 16 GB / Intel i7-9700K | Not provided | Open report |
| build-75 | runs with issues | RX 5700 / Not provided | 32 FPS | Open report |
| build-75 | runs with issues | AMD Radeon RX 7900 XTX / Not provided | 12 FPS | Open report |
| build-70 | not booting | NVIDIA GeForce RTX 3070 / AMD Ryzen 7 5800X 8-Core Processor | Not provided | Open report |
| R75 MSVC | boots | Not provided / Not provided | Not provided | Open report |
build-83 report
Statusruns with issues
GPUAMD Radeon RX 9060 XT 16 GB
CPUIntel i7-9700K
DriverAMD proprietary driver 32.0.32015.7029
Recorded FPSNot provided
Problems or notes: User reports say the game reaches gameplay and then loses the GPU device. The report also mentions black output after rejecting selected shaders and a later device loss. All tried settings and environment-variable changes still resulted in device loss.
build-75 report
Statusruns with issues
GPURX 5700
CPUNot provided
Driveramdvlk 32.0.21045.16010
Recorded FPS32 FPS
Problems or notes: The comment reports 4800 to 16800 presents and 32 FPS, and says the game presents frames. This is compared with local builds of commit b8c812b18 that stalled at max present 8 and showed no frames; the difference's cause is unresolved.
build-75 report
Statusruns with issues
GPUAMD Radeon RX 7900 XTX
CPUNot provided
DriverAMD proprietary driver 2.0.416
Recorded FPS12 FPS
Problems or notes: User reports no hang, but the 3D scene is black with HUD only.
build-70 report
Statusnot booting
GPUNVIDIA GeForce RTX 3070
CPUAMD Ryzen 7 5800X 8-Core Processor
DriverNVIDIA 621.1.0.0
Recorded FPSNot provided
Problems or notes: Issue reporter says the game remains on "Launching..." indefinitely; the log shows the emulated program breaking execution with error F001. Additional user reports mention infinite launch screens. Other users report that R75 MSVC boots past the intro FMV in docked mode, but describes severe white/black-screen graphics problems in other builds or modes.
R75 MSVC report
Statusboots
GPUNot provided
CPUNot provided
DriverNot provided
Recorded FPSNot provided
Problems or notes: A user reports booting and working past the intro FMV in docked mode; no sustained gameplay is stated.
Related game issues
- [GBug] Ocarina of Time (0400486024DEC000): gameplay settles at ~29 fps, CPU-bound on two cores (build 75) (open)
- Ocarina of Time (Switch 2) gets stuck at "Building 9 shaders" on AMD RX 6750 XT (open)
- [Crash] Ocarina of Time: AMD RX 7900 XTX driver timeout / device lost at gameplay start, gone with #150 reverted (open)
- Ocarina of Time (0400486024DEC000) build-75: macro parameter desync + unknown texture format 100, broken lighting/bloom and corrupted textures (open)
- [VBug] OoT (0400486024DEC000): textures flicker with Low GPU accuracy + EDEN_NX2_SPLIT=2 on AMD RX 9070 XT; High fixes it but turns the split off (~9 fps) (open)
- [GBug] Ocarina of Time: black 3D gameplay screen; HUD remains visible (Lichii build 75) (closed)
- [VBug] Doesn't work for AMD GPU - 9070 XT (The Legend of Boy in Green Hat) (open)
- [VBug] Ocarina of Time: AV1 cutscenes render solid green on AMD/RADV (audio and subtitles OK) (open)
- [Build] Tree does not compile with clang-cl on Windows (NOMINMAX and FARPROC casts) (open)
- [GBug] Ocarina of Time / Audio Desync (open)
- [VBug] [nx2-build-75] Zelda: Ocarina of Time (0400486024DEC000) black screen — no AV1 decoder (open)
- [GBug] Ocarina of Time (0400486024DEC000): black screen on Adreno 740/Turnip, pipeline builders stuck in driver until memory runs out (open)
- [GBug] Zelda OOTR Won't Load (open)
- [GBug] (closed)
- Release note: User reports describe gameplay performance below 60 FPS on multiple systems and builds. One report also describes a black 3D screen in Handheld mode; switching to Docked allowed rendering.
- Release note: A user report says resolution 2X caused flicker or line artifacts; a separate candidate-build report says the release's overexposure warning was not cleared by its limited test.
- Release note: 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.
- Release note: User reports GPU driver timeout or device loss when gameplay starts on AMD Windows systems, including RX 7900 XTX and RX 9060 XT. Reports associate the issue with #150 pointer-binding changes, but this is an unconfirmed hypothesis.
- Release note: On build-75, user reports over-bright bloom/glow, overly dense fog, incorrect lighting, and some textures decoded as garbage; logs include macro-parameter assertions and an unknown texture format 100.
- Release note: Textures and surfaces flicker with Low GPU accuracy and EDEN_NX2_SPLIT=2 on Radeon RX 9070 XT; some surfaces remain white temporarily.
- Release note: Outdoor haze is very strong, and the river surface can appear dark or black.
- Release note: A commenter reports being unable to load a save, with the PC hard-locking or freezing before recovering after a driver crash or timeout; same GPU, 32GB RAM, and i7 9700K.
- Release note: The 3D gameplay scene can appear black while the HUD remains visible.
- Release note: A commenter reported stuttering, FPS drops, and overexposure after switching to Docked mode.
- Release note: A commenter reported flickering shadows and trees with no leaves.
- Release note: A commenter reported audio playing ahead of the video during the intro.
- Release note: With use_disk_shader_cache = true, subsequent boots hang indefinitely at Loading Shaders 25 / 27.
- Release note: Black screen after the intro on AMD RX 9070 XT; the game's 1080p upscaler shader is rejected.
- Release note: On AMD, the world is black except around Navi and Link; an RX 6800 XT reporter says the workaround still leaves all 3D geometry black.
- Release note: Texture flicker with Low GPU accuracy and GPU thread split on AMD RX 9070 XT.
- Release note: Handheld mode is reported as much brighter and blurrier than Docked mode.
- Release note: On Linux with AMD/RADV, AV1 intro cutscene video renders solid green while audio and subtitles work.
- Release note: On Windows 10 with AMD, the intro AV1 cutscene shows a black video layer with working audio and subtitles, then the emulator hangs indefinitely.
- Release note: A local ClangCL build of b8c812b18 stalled at max present 8 and showed no frames; a local MSVC build of the same commit stalled at max present 8 and died within a minute, unlike the reported build-75 release.
- Release note: User reports audio/video desynchronization on the title screen and intro; a commenter reports slow-motion live-rendered title-screen video with audio leading by approximately three seconds, worsening by the initial dream cutscene.
- Release note: User reports a black screen after the game's AV1 video streams fail to decode; FFmpeg reports no decoder for "video/av1". The game idles indefinitely on a black frame.
- Release note: 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.
- Release note: Issue reporter says Zelda Ocarina Of Time Remake stays on "Launching..." indefinitely; the log records an emulated program break with error F001. Other reports mention an infinite launch screen.
- Release note: A user reports severe shader problems with white visuals; handheld mode shows a black screen.
- Release note: A user reports a black screen past the title screen.
- Release note: The 3D gameplay scene is black while HUD elements remain visible; menus and item preview can render correctly.
Compared with Previous Build
Current: build-83 (1 record); previous: build-75 (2 records).
Showing 41–50 of 114 reports
Known issues from Lichii sources
Known Game Issues
Star Fox
On RTX 50-series GPUs, the GPU device can still be lost after a scene change.
Recorded fix: Try NVIDIA driver 610.88.
Star Fox
Gameplay is capped at about 30 fps, even though the game asks for 60.
Star Fox
On RTX 50-series GPUs (5070 Ti, 5090), the GPU device can be lost shortly after a scene change.
Recorded fix: Try NVIDIA driver 610.88.
Yoshi and the Mysterious Book (demo)
Some textures are still black, and the game can crash later in play.
Kirby Air Riders
Some races still stall while shaders build.
Zelda: Ocarina of Time
On macOS arm64 through MoltenVK, the Metal device may be lost or the GPU thread may hang at the intro-video/gameplay boundary. A commenter attributes the device loss to an attachment-less framebuffer reaching 32768×32768, above the stated Apple GPU limit of 16384.
Zelda: Ocarina of Time
After a local workaround for device loss, a commenter reports that the 3D scene remains black while sound and subtitles work on an older Eglantine fork; current nx2 behavior was not yet checked.
Hyrule Warriors
In stages past the first one, the gameplay screen is black while the UI remains visible; pausing shows the world rendered in the background.
Zelda: Ocarina of Time
User reports a crash when opening the game on Arch Linux with an AMD Radeon AI PRO R9700 (9070XT); the console reports a segmentation fault.
Showing 1–10 of 98 issues
Notes de version récentes
Changements de compatibilité dans les dernières versions
Version build-88 · Non renseigné
Integrated performance ports and reduced unnecessary writer tracking; added explicit GPU-to-host visibility before buffer readback and submitted native desktop GPU work earlier while preserving conservative synchronization for macro reads and semaphore waits.
Version build-88 · Non renseigné
Added bounded background preparation of cached graphics pipelines and persistent task/mesh shader state. Updated the Vulkan cache to v53 while preserving compatible v52 caches, and made interrupted cache migrations retryable.
Version build-88 · Non renseigné
Fixed temporal history, motion interpolation, image transitions, and descriptor retirement for FSR3 frame generation; frame generation remains off by default.
Version build-88 · Zelda: Ocarina of Time
Bundled Dark's Dynamic FPS mod, enabled by default for Ocarina of Time. Disable it independently in the game's Add-Ons settings. Max Resolution remains a separate Add-On. CPU Clock Normal is recommended when evaluating the mod; Boost/Overclock can affect game speed. Full gameplay timing has not been verified.
Version build-83 · Ocarina of Time
Fixed missing vegetation, incorrect materials and lighting, a glowing doorway, one-frame white flashes, and an AMD black 3D scene. Added Max Resolution (built-in), enabled by default for the supported game build, and Ocarina-specific frame-ahead presentation tuning.
Choix d’une version
Quelle version utiliser ?
Choisissez un jeu ci-dessus pour voir quelles versions testées sont disponibles au téléchargement. En attendant, utilisez la dernière version disponible et lisez ses notes.
Essayez la dernière version disponible : build-88. Gardez une version fonctionnelle sous la main pendant vos essais.
Questions sur la compatibilité
FAQ sur la compatibilité des jeux
Comment partager un jeu avec ces filtres ?
Appliquez les filtres de jeu, de statut, de GPU et de version, puis copiez l’URL de la page. Un lien vers un jeu précis ouvre sa fiche.
Que faire si j’obtiens un écran noir ?
Vérifiez dans d’autres rapports si le jeu atteint les menus ou une partie jouable. Notez votre pilote et le moteur de rendu, puis recherchez le jeu ou l’erreur dans le guide de dépannage.
Pourquoi un même GPU peut-il donner des résultats différents ?
La version du pilote, les réglages graphiques, la charge du processeur et la partie du jeu testée peuvent influer sur le résultat. Comparez ces détails avant de modifier votre configuration.
Où puis-je soumettre un résultat manquant ?
Utilisez le suivi officiel des tickets de Lichii. Indiquez le jeu, le tag de la version, le matériel, le pilote, les réglages et les étapes pour reproduire ce que vous avez observé.