The Legend of Zelda: Ocarina of Time
The emulator closes when loading Hyrule Market after the user exits Kokiri Forest and enters Hyrule Castle.
Compatibilidad de juegos
¿Tienes un juego en mente? Comprueba cómo funciona en Lichii, revisa los problemas detectados y elige una versión para probar.
Encuentra un juego
Los datos actuales incluyen 108 registros de juego y entorno y 308 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
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: Ocarina of Time, Zelda: Ocarina of Time, OoT, Zelda OoT, TLoZ: OoT
| Build | Status | GPU / CPU | FPS | Details |
|---|---|---|---|---|
| Not provided | playable | Not provided / Not provided | Not provided | Open report |
| Not provided | runs with issues | 1080 Ti / Ryzen 5600X | Not provided | Open report |
| Not provided | runs with issues | GTX 1050 Ti / 7th gen i5 | 18–27 FPS | Open report |
| Not provided | playable | RTX 3070 Ti / Ryzen 7 2700X | Not provided | Open report |
| build-95 (`nx2-build-95`) | runs with issues | RTX 4060 Laptop, 8 GB, 45 W max power limit / Intel Core i7-12650H (6P+4E, 16 threads) | 9.4–51.4 FPS | Open report |
| build 95 | runs with issues | Radeon 890M / Ryzen AI Z2 Extreme | 23–25 FPS | Open report |
| build 117 (PGO) | runs with issues | Radeon 890M / Ryzen AI Z2 Extreme | 42–44 FPS | Open report |
| nx2-build-95 | runs with issues | NVIDIA GeForce RTX 2070 / Intel Core i7-12700KF | Not provided | Open report |
| Not provided | not booting | NVIDIA GeForce RTX 3050 / Not provided | Not provided | Open report |
| build 88 and 93 | runs with issues | GTX 1060 6gb / Ryzen 5 5600 | Not provided | Open report |
Problems or notes: A commenter says everything works on their Mac with the latest main branch; hardware and build details are not stated.
Problems or notes: A commenter reports objects and doors failing to appear.
Problems or notes: A commenter reports invisible push blocks, making progress difficult.
Problems or notes: A commenter reports testing the draft shader warm-up and says first-visit freezes were gone. The comment gives no broader gameplay or session-duration evidence.
Problems or notes: User reports multi-second stalls while draws are held for unbuilt pipelines with async shaders enabled; in about 8 minutes, mean performance was 25.8 fps and six present windows had a maximum frame time over 1 s (worst 4.9 s). A fresh config used slow defaults and ran at 10–15 fps with stalls up to 8.9 s and blurry/pixelated Handheld resolution. Settings for the measured build-95 session were GPU accuracy Low, async shaders and async presentation enabled, Docked, 8 GB memory layout, and NVDEC GPU. The report also describes Frizti v3 behavior separately: it skipped draws with no pipeline, averaging 26.0 fps in 30-fps mode (range 16.4–30), with revisits at 30.0 fps and no frames over 100 ms.
Problems or notes: The intro, Deku Tree cutscene, and initial gameplay rendered correctly, but the game froze at 0 FPS when Navi passed the Kokiri guard on the path to the Deku Tree. The report mentions texture format asserts and Unmapped Device ReadBlock errors.
Problems or notes: The intro and cutscenes ran at 42–44 FPS and the game reached Kokiri Forest, but Unmapped Device ReadBlock errors and multi-second stalls were followed by a hard freeze before Navi reached the guard. The same errors occurred with memory layout set to both 12 GB and 4 GB.
Problems or notes: User reports that after the Kaepora Gaebora cutscene near Hyrule Castle, the area appears empty and foggy, Link falls through the world, and repeated void-outs prevent progression. Reported on Windows 11 25H2 in Handheld mode with Vulkan. The user says the issue reproduces 100% with the same save; listed configuration changes and disabling a built-in patch did not fix it.
Problems or notes: Crashes during boot about 9–13 seconds after launch, after presenting its first frame, at an unimplemented nx2:vi2 function 201. The same crash is reported on builds 93 and 95.
Problems or notes: A commenter reports missing textures in the Deku Tree after loading a save, across two game versions and builds 88 and 93. They also report that it worked the first time.
Current: build-117 (2 records); previous: build-116 (0 records).
Showing 171–180 of 308 reports
Known issues from Lichii sources
The emulator closes when loading Hyrule Market after the user exits Kokiri Forest and enters Hyrule Castle.
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.
Two hidden/minimized Windows CLI launches crashed in nvoglv64.dll with exception 0xc0000094 at offset 0xEFC9BB. Static findings identify stale SDL visibility state and no zero-extent guard as possible leads, but neither is proven to cause the crash.
An AMD Linux report describes GPU/display blackout and VK_ERROR_DEVICE_LOST on entering gameplay without EDEN_NX2_NO_MESH=1; the user reports at least five minutes of gameplay with the option enabled. Another AMD Linux report describes intermittent SIGSEGV crashes that occur with or without the option.
Random dynarec crashes during gameplay, reported on Linux with AMD graphics cards; one report specifies an AMD RX 7000 series GPU.
Overexposure in specific areas, including the lower part of Saria's house and the right side of the entrance to hyrule castle.
Audio and video become desynchronized on the title screen, intro, and initial dream cutscene; a commenter reports slow-motion live-rendered video and an audio lead of approximately 3 seconds.
On an AMD Radeon RX 6700 XT with AMD Software (Adrenalin) 26.10.2, Lichii closes during the first shader rebuild after about 9-10 minutes; Event Viewer reports an access violation in amdvlk64.dll.
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.
Constant 4 FPS in-game on AMD Radeon RX 570 4GB.
Showing 261–270 of 361 issues
Notas de versiones recientes
Versión build-117 · Ocarina of Time
Versión build-116 · Zelda: Ocarina of Time
Versión build-116 · Zelda: Ocarina of Time
Versión build-116 · Zelda: Ocarina of Time
Versión build-116 · Mario Tennis Fever
Elegir una versión
Elige un juego arriba para ver qué versiones probadas puedes descargar. Mientras tanto, usa la descarga más reciente y lee sus notas.
Prueba la última versión disponible: build-117. Conserva una versión que funcione por si necesitas volver a ella durante las pruebas.
Dudas sobre compatibilidad
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.
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.
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.
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.