Zelda: Ocarina of Time
Slows when booting.
Compatibilidad de juegos
Compatibilidad de juegos con Lichii Emulator
¿Tienes un juego en mente? Comprueba cómo funciona en Lichii, revisa los problemas detectados y elige una versión para probar.
Latest recorded build
build-94
Pre-release
Published November 7, 2026
Encuentra un juego
Buscar juegos compatibles con Lichii
Los datos actuales incluyen 76 registros de juego y entorno y 175 informes sobre Lichii.
¿No encuentras un juego? Si no hay resultados, aún no se muestra ningún informe de Lichii sobre ese juego. No significa que haya fallado una prueba.
Fíjate en la plataforma indicada para distinguir entre distintas versiones de un juego.
Qué significa cada estado: «Unknown»: sin conclusión. «Not booting»: el juego no arrancó. «Boots»: solo se confirmó el arranque. «Runs with issues»: hubo problemas durante la partida. «Playable»: la persona que hizo la prueba pudo seguir jugando.
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.
Zelda: Ocarina of Time Reported platform: unknown
Also listed as: OoT
| Build | Status | GPU / CPU | FPS | Details |
|---|---|---|---|---|
| build-83 | unknown | AMD RX 6000 series or older; AMD Radion RX 6650 XT / AMD Ryzen 5 5600 | Not provided | Open report |
| build-83 | unknown | Not provided / Not provided | Not provided | Open report |
| build-75 | runs with issues | RTX 3080 / Ryzen 5900X | 12–22 FPS | Open report |
| Not provided | runs with issues | AMD Radeon RX 6600 XT 8 GB / Ryzen 5 5600X | 25–33 FPS | Open report |
| 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 |
build-83 report
Statusunknown
GPUAMD RX 6000 series or older; AMD Radion RX 6650 XT
CPUAMD Ryzen 5 5600
DriverNot provided
Recorded FPSNot provided
Problems or notes: Reported that the game slows when booting; the reporter restarted the emulator and game and changed settings, but did not state a resolution.
build-83 report
Statusunknown
GPUNot provided
CPUNot provided
DriverNot provided
Recorded FPSNot provided
Problems or notes: The release says the perf9 build was tested successfully in Ocarina of Time, but provides no gameplay duration or specific tested hardware.
build-75 report
Statusruns with issues
GPURTX 3080
CPURyzen 5900X
DriverNot provided
Recorded FPS12–22 FPS
Problems or notes: Outdoor areas have excessive fog and glow, performance is about 12–22 fps, and three rare shaders remain unsupported.
Not provided report
Statusruns with issues
GPUAMD Radeon RX 6600 XT 8 GB
CPURyzen 5 5600X
DriverAMD proprietary driver 2.0.353 (`amdvlk64.dll` 32.0.21045.16010)
Recorded FPS25–33 FPS
Problems or notes: On the reported Windows 11 setup, the intro freezes at 0 FPS while two compute pipelines compile, taking 6 and 18 minutes. After compilation and caching, the intro proceeds; reported scenes run at about 33 FPS. Disabling optimization builds the pipelines faster but reported scenes run at about 25 FPS. Rejecting the two shader hashes makes the intro play at 60 FPS but leaves parts of the picture black.
Not provided report
Statusruns with issues
GPURX 6650 XT (RDNA2)
CPUi5-10400F
DriverAMD proprietary driver 2.0.353 (`amdvlk64.dll` 32.0.21045.16010)
Recorded FPS25–27 FPS
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.
nx2 `5a50f50e0b` (official PGO artifact of build-80 and local non-PGO build of nx2-latest) report
Statusruns with issues
GPUAMD RX 9070 XT (RDNA4, 16 GB)
CPURyzen 7 5800X3D (8C/16T), 32 GB RAM
DriverMesa 26.x RADV
Recorded FPS28–35 FPS
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.
Not provided report
Statusruns with issues
GPUAMD RX 9070 XT
CPUNot provided
Driver26.10.2
Recorded FPSNot provided
Problems or notes: A commenter reports approximately 3 minutes of gameplay before a black screen, driver crash, and crash to desktop.
Not provided report
Statusplayable
GPURTX 5090
CPUNot provided
DriverNot provided
Recorded FPS40–60 FPS
Problems or notes: Gameplay testing in Kokiri Forest reported no crashes; normal game speed was below 60 FPS with #216. GPU accuracy was Low.
Not provided report
Statusunknown
GPUAMD 7600
CPUNot provided
DriverNot provided
Recorded FPSNot provided
Problems or notes: A commenter reports having the same issue without further details.
Not provided report
Statusruns with issues
GPURX 9070 XT
CPUNot provided
DriverNot provided
Recorded FPS10–60 FPS
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.
Related game issues
- [VBug] black screen amd (open)
- [GBug] Zelda: Ocarina of Time (0400486024DEC000): the audio plays a different part of the stream than the picture (open)
- [Crash] black screen when starting Zelda: Ocarina of Time on the latest build - Intel(R) HD Graphics 620 with vulkan and OpenGL GLS (open)
- [VBug] OoT (0400486024DEC000): world renders black except areas lit by Navi and around Link, AMD RX 9070 (closed)
- [VBug] [nx2-build-75] Zelda: Ocarina of Time (0400486024DEC000) black screen — no AV1 decoder (closed)
- [GBug] Ocarina of Time on RADV (RX 9070 XT): 28-35 fps, 35 ms frame with no saturated thread (translation/sync bound) (open)
- [VBug] Build 93 finaly has no major visual errors but has poor performance 9070xt (open)
- [Crash] Crash replicated multiple times when trying to enter Hyrule Market - The Legend of Zelda: Ocarina of Time (open)
- [Crash] (open)
- [Perf] OoT (0400486024DEC000): per-fence Preflushable buffer downloads (~430 MB/s) are the biggest GPU back-thread cost; batching them gives +55% draws/s but breaks exposure (open)
- [GBug] Ocarina of Time (0400486024DEC000): intro freezes for 6 to 18 minutes on AMD while the driver optimizes two compute shaders (open)
- [Crash] AMD Ocarina of time Doesn't Start (open)
- Ocarina of Time harvest fork: findings and open tasks (open)
- [GBug] OoT (0400486024DEC000): the same ~60 cached graphics pipelines are rebuilt on the GPU thread every boot (closed)
- macOS/MoltenVK: Ocarina of Time (0400486024DEC000) kills or hangs the Metal device at the intro-video boundary (open)
- [GBug] System language Portuguese (Brazil) doesn't change in-game language for the Remake of The Legend of Zelda: Ocarina of Time (closed)
- [VBug] Oot is in a "nightmare mode"? also gameplay speed is at like 30% (open)
- [VBug] OoT Slows when booting. (closed)
- [Crash] Ocarina of Time (0400486024DEC000): freezes in Hyrule Castle Town pot room near the guard (open)
- [Crash] Linux/RADV (RX 9070 XT): invalid SPIR-V fragment shader (depth image u32 sampled as f32) segfaults in VkPipelineBuild, Ocarina of Time (open)
- [Crash] AMD Crash/AudioDesync (open)
- [Crash] Ocarina of time crash on Linux AMD (open)
- [AMD RX 9070 XT] Black screen with UI visible and GPU driver timeout (Build 88) (open)
- [Bug] Windows build-83 can hang on Closing software after OoT gameplay (open)
- Release note: 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.
- Release note: Black screen or no video output while audio works or appears to work.
- Release note: Audio issues and occasional crash when launching another game without restarting after the game loads using Docked Mode and Accurate GPU.
- Release note: Clean audio from a different point of the game plays while the intro image is displayed; audio and picture are substantially out of sync.
- Release note: In gameplay, the world renders almost entirely black, with only the HUD and some areas near light sources visible; some shapes appear blown out with heavy bloom.
- Release note: PGO artifact crashes in dynarmic with Unhandled SIGSEGV after 2–10 minutes on the reported machine.
- Release note: Conflicting reports of low and high frame rates on an RX 9070 XT, with one comment suggesting Windows performance may be worse than Linux.
- Release note: The console restarts after the scene on Linux with a lenovo legion go 2 z2 and egpu 7600xt; the report names versions 83 et 93.
- Release note: In the measurement-only experiment, disabling per-fence Preflushable downloads or batching downloads by 64 fences caused overexposure in Kokiri Forest.
- Release note: 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.
- Release note: 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.
- Release note: 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.
- Release note: The issue reporter using an AMD RX 6600 8GB on Windows 10 reports that the emulator starts loading and then remains on a black screen.
- Release note: Commenters report rendering failures, black screens, and AMD driver crashes; one reports that audio continues while rendering is crashed.
- Release note: Community comments describe AMD black or corrupted-world output, fragment-pipeline compiler crashes on Windows, later timeouts or TFB stalls, corrupted output, and a RADV depth-image SPIR-V failure. These are separate reported cases; the comments do not establish a universal cause or resolution.
- Release note: Persistent graphics pipeline cache entries are reportedly rebuilt on the GPU thread during gameplay on repeated boots, causing a visible hitch.
- Release note: 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.
- Release note: 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.
- Release note: With GPU Mode: Accurate (High), gameplay may run in slow motion at about 30 FPS; shader compilation can cause stutter on new content.
- Release note: Slows when booting.
- Release note: User-reported reproducible freeze when walking deeper into the pot room in Hyrule Castle Town, near the guard.
- Release note: User reports a segfault during gameplay on Linux with an AMD RX 9000-series GPU and RADV, when a graphics pipeline is built for an invalid fragment shader.
- Release note: User reports audio/video desynchronization during the opening cutscene and a system freeze at the Deku Tree cutscene on Vulkan with an AMD RX 9000 series GPU. Comments report crashes on AMD GPUs, including while building shaders. One commenter reports that OpenGL GLSL stops the crashes but leaves only the UI visible.
- Release note: 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.
- Release note: On some AMD GPUs, the UI may remain visible while the 3D world is black; reports also describe AMD driver timeouts or crashes.
- Release note: On Windows build-83, shutdown can hang at “Closing software…” after gameplay. Some sessions completed shutdown successfully; the cause is undetermined.
Compared with Previous Build
Current: build-93 (1 record); previous: build-88 (1 record).
Showing 81–90 of 98 reports
Known issues from Lichii sources
Known Game Issues
Legend of Green hat boy
User reports the game crashes after about 15 to 20 minutes.
Kirby Air Riders
The emulator force quits after being stuck on the "Loading Shaders" screen for about 2 seconds.
Other / not listed
After the intro, the scene where the deku tree is talking is completely black with very slow, stuttery dialogue.
Other / not listed
After the startup screen, audio plays but the screen is black.
Other / not listed
Music disappears during the cutscene after booting the game.
Other / not listed
The game crashes while building shaders after the title card fades.
Hyrule Warriors
An error appears after the cinematic and remains on screen, blocking the view.
Other / not listed
Black screen during cinematic after the main menu appears; reported on Windows 11 with an AMD RX 6000 series or older GPU.
Other / not listed
Infinite startup launch loop when booting the .NUP version.
Showing 141–150 of 188 issues
Notas de versiones recientes
Cambios de compatibilidad en las últimas versiones
Versión build-94 · Ocarina of Time
Fixes near foliage disappearing, white flashes during camera movement, terrain drawn over the scene, a stale Z-target reticle, and several shader issues. The changes had only limited gameplay testing.
Versión build-94 · No indicado
Fixes a race-related random crash involving an unallocated SparseLargeVector region, which the release says can affect any game.
Versión build-94 · No indicado
Adds LayeredFS mod support for NUP titles.
Versión build-94 · No indicado
The migration prompt's Keep Old Data option now keeps data instead of moving it.
Versión build-94 · No indicado
Adds an experimental option to pin GPU threads to their own cores. It is off by default and requires 6 or more physical performance cores.
Elegir una versión
¿Qué versión debo usar?
build-93 · Publicada el November 6, 2026
Zelda: Ocarina of Time
- runs with issues · GPU RX 9060XT 16GB · CPU Ryzen 5 7600 · Controlador No indicado
7 archivos para descargar en esta versión.
build-88 · Publicada el November 6, 2026
Zelda: Ocarina of Time
- not booting · GPU AMD Radeon AI PRO R9700 (9070XT) · CPU No indicado · Controlador No indicado
7 archivos para descargar en esta versión.
build-83 · Publicada el November 6, 2026
Zelda: Ocarina of Time
- runs with issues · GPU RTX 4070 SUPER 12 GB · CPU i5-14600KF · Controlador 621.14
- unknown · GPU AMD RX 6000 series or older; AMD Radion RX 6650 XT · CPU AMD Ryzen 5 5600 · Controlador No indicado
- unknown · GPU No indicado · CPU No indicado · Controlador No indicado
12 archivos para descargar en esta versión.
Prueba la última versión disponible: build-94. Conserva una versión que funcione por si necesitas volver a ella durante las pruebas.
Dudas sobre compatibilidad
Preguntas frecuentes sobre compatibilidad de juegos
¿Cómo comparto un juego con estos filtros?
Aplica los filtros de juego, estado, GPU y versión y copia la URL de la página. Un enlace a un juego concreto abre su ficha de informes.
¿Qué puedo probar si aparece una pantalla negra?
Revisa en otros informes si el juego llega a los menús o permite jugar. Anota el controlador y el motor de renderizado y busca el juego o el error en la guía de solución de problemas.
¿Por qué puede dar resultados distintos la misma GPU?
La versión del controlador, los ajustes gráficos, la carga de la CPU y el tramo del juego que se prueba pueden cambiar el resultado. Compara estos detalles antes de cambiar tu configuración.
¿Dónde puedo aportar un resultado que no aparece?
Usa el gestor oficial de incidencias de Lichii. Indica el juego, la etiqueta de la versión, el hardware, el controlador, los ajustes y los pasos para reproducir lo que viste.