The Legend of Zelda: Ocarina of Time (Switch 2)
User reports that rejecting shader programs containing native opcode 0x4a4 avoids a Metal page fault, but may leave the run stalled at the end of the video with semaphore waits and GPU-thread abort.
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.
| Build | Status | GPU / CPU | FPS | Details |
|---|---|---|---|---|
| 62ba83427e | runs with issues | Radeon 8060S / Ryzen AI MAX+ 395 | 31–37 FPS | Open report |
Problems or notes: In Kokiri Forest, haze, blotches, and a translucent band appear in a fullscreen pass. Rejecting shader 3ddfb1d7a854c849 removed the haze and blotches in that test, while rejecting 780c0536b89fc89e removed fog but left blotches; these workarounds also remove game effects. Two starts stayed black from the beginning, one with music. A reported 31–37 FPS comparison against build-75 used views that were not identical.
Also listed as: OOT Remake, OoT
| Build | Status | GPU / CPU | FPS | Details |
|---|---|---|---|---|
| 3724db9a5c | playable | RTX 4070 / i9-12900F | 16 FPS | Open report |
| b8c812b18 | runs with issues | RX 5700 / Not provided | Not provided | Open report |
| build 95 | playable | RX 7900 XTX / Ryzen 7 9800X3D | 60 FPS | Open report |
| nx2 @ 27226d2 plus two measurement-only commits | runs with issues | RTX 5060 Laptop (8 GB) / Ryzen AI 9 365 | Not provided | Open report |
| Lichii nx2 build 88 | boots | Intel Arc / Not provided | 1 FPS | Open report |
| nx2 build 88 | not booting | NVIDIA RTX 3060 / Ryzen 7 5700X | Not provided | Open report |
| Not provided | runs with issues | AMD Radeon RX 9070 XT / Not provided | Not provided | Open report |
| Build-93 MSVC 19.44.352995.0 | runs with issues | RX 9060XT 16GB / Ryzen 7 5700X | 1–30 FPS | Open report |
| nx2-9fa4a71fa0-nx2 | runs with issues | AMD Radeon RX 7600, 8 GB / AMD Ryzen 5 5500 | 15 FPS | Open report |
Problems or notes: The tester reported visible grass and a clear view of the tree through grey fog in front of the Deku Tree. The in-game counter showed 16 FPS in that view; this was a single reading.
Problems or notes: A user reported a local ClangCL build stalled with no frames (maximum 8 presents); a local MSVC build also stalled and died within a minute. In comparison, the user's build-75 release run presented frames at 32 FPS. The maintainer said the report was from an old commit and may no longer apply.
Problems or notes: Not provided
Problems or notes: In the Kokiri Forest scene, disabling per-fence Preflushable downloads or batching them by 64 fences increased GPU back-thread draws per second but broke auto-exposure, leaving the scene overexposed. Default downloads preserved correct exposure. The issue reports measurements, not a gameplay FPS result.
Problems or notes: The issue title reports about 1 FPS in the main menu and first cutscene. A comment reports about 9 FPS in the opening cutscene on an Intel Arc B580 with driver 101.9150 and Lichii v2.
Problems or notes: The user's .NUP dump remains on the Launching screen and does not start. Keys and firmware 23.0.1 were installed, but the issue persisted. The earlier launch log showed an ARM exception after unmapped memory accesses, but may have come from a separate troubleshooting launch and needs confirmation.
Problems or notes: In docked mode, a dotted cyan/magenta line appeared along mountain and sky silhouettes in Hyrule Field. The issue author reports that the line disappeared after the fix was tested.
Problems or notes: User reports occasional audio loss, frame-rate drops from 30 to 1 that recover to 30, a missing sky replaced by bright light, and a missing map. The report also lists AMD RX 9000 series as the graphics card.
Problems or notes: Gameplay and movies run, but movie voices intermittently pause while video continues, causing late or absent audio. Gameplay was reported at about 15 fps in one test; another report recorded 15.4–19.4 average FPS over three sessions on build 9991f27, with hitches of 2–4 seconds and worst frames of several seconds. No driver crash or visual problems were noticed in the tested forest areas. Movie audio was not evaluated in the 9991f27 sessions.
Showing 61–70 of 308 reports
Known issues from Lichii sources
User reports that rejecting shader programs containing native opcode 0x4a4 avoids a Metal page fault, but may leave the run stalled at the end of the video with semaphore waits and GPU-thread abort.
Dynamic FPS does not maintain normal game speed at 30-40 FPS; another report says gameplay speeds up at 30 FPS when CPU Clocks is set to Boost.
Recorded fix: Set CPU Clocks to Normal to resolve the sped-up gameplay reported with Boost enabled.
With an AMD RX 9000 series graphics card on Windows 11, the game crashes as the Great Deku Tree cutscene is about to begin, showing a black screen and an AMD driver timeout. A commenter reports a similar crash with AMD graphics on Linux.
Users report very low frame rates in the main menu and opening cutscene on Intel Arc GPUs; a Linux user also reports a prolonged shader stall on first boot and a frozen Kokiri intro cutscene.
A user reports a crash when launching the game; the log reports failed backing-memory and fallback-buffer allocation.
With GPU Mode: Accurate, gameplay runs at about 30 fps and in slow motion; the commenter attributes this to the GPU thread split not starting at high GPU accuracy. Shader pipeline builds can also cause stutter on new content.
Recorded fix: The commenter reports that changing GPU Mode to Fast resolved the slow-motion speed issue for them. For shader-build stutter, they report that an opt-in EDEN_NX2_ASYNC_DISCARD=1 skips draws while pipelines build.
Black video on the PGO build; the game works well on MSV.
A commenter reports crashes with AMD graphics cards related to mesh shaders and says a similar issue occurs on Windows and Linux.
Dialogue box background panel and hint strip flicker in about half of presented frames with EDEN_NX2_FRAMES_AHEAD=1; other HUD elements may also flicker.
Recorded fix: Set EDEN_NX2_FRAMES_AHEAD=0. The reporter found this stopped the dialogue panel flicker, with a frame-rate cost; another reporter said the remaining occasional flicker was rare and could not be reproduced on demand.
Black screen with visible UI during gameplay in stages past the first one, while the world renders in the background when paused.
Showing 291–300 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.