After: Dynamic FPS mod bundled and enabled by default; automatic patching is restricted to the supported game build and checks for patch conflicts.
build-83 → build-88
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 58 registros de juego y entorno y 114 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 |
|---|---|---|---|---|
| Lichii nx2-build-83 | not booting | AMD Radeon RX 6650 XT (RDNA2) / Intel Core i5-10400F | Not provided | Open report |
| nx2-build-83 | runs with issues | Radeon RX 6800 / Not provided | 43–47 FPS | Open report |
Problems or notes: User reports the render area remains black after booting, in both handheld and docked modes. Updating the AMD driver, clearing the shader cache, changing listed settings, and trying other builds did not change the result.
Problems or notes: User reports the game renders correctly in a screen capture at about 47 fps, but the displayed image is solid green. The report states about 43 fps during presentation.
Also listed as: OoT
| Build | Status | GPU / CPU | FPS | Details |
|---|---|---|---|---|
| nx2 @ 27226d2 plus two measurement-only commits | runs with issues | RTX 5060 Laptop (8 GB) / Ryzen AI 9 365 | Not provided | Open report |
Problems or notes: In Kokiri Forest, disabling per-fence Preflushable downloads or batching them by 64 fences caused overexposure. Default per-fence downloads preserved correct exposure. The report measures GPU back-thread draws/s, not game FPS.
Also listed as: OoT
| Build | Status | GPU / CPU | FPS | Details |
|---|---|---|---|---|
| build-88 | runs with issues | AMD Radeon RX 9070 XT / AMD Ryzen 7 7800X3D | Not provided | Open report |
| Not provided | runs with issues | NVIDIA RTX 30 series or older / Not provided | Not provided | Open report |
| Not provided | runs with issues | AMD RX 9060 XT / Not provided | Not provided | Open report |
| nx2-build-83 | runs with issues | AMD RX 9000 series / Not provided | 41 FPS | Open report |
Problems or notes: The logo, text, and UI are visible, but the 3D environment and background remain black; audio continues. AMD driver timeouts or crashes sometimes occur. The issue persists after updating and rolling back the driver and restarting. The issue author says graphics displayed previously, but the issue appeared afterward.
Problems or notes: Audio plays a different part of the game than the image during the intro; the audio is clean but out of sync by a scene. A follow-up report says the game uses StreamType::Render and that traced sink appends were complete with no samples dropped. Another user reports the same issue with a 7800X3D, RTX 5070, and 32gb DDR5.
Problems or notes: A commenter reports a driver crash and black screen after the intro on the MSVC build. The PGO build reportedly shows only 2D elements such as the logo or menu.
Problems or notes: User reports audio running ahead of video, cutting out and repeating during the opening cutscene, followed by a system freeze at the Deku Tree cutscene requiring a forced shutdown. Settings reported: Vulkan, GPU Mode Fast, Docked, Bilinear window adapting filter, and no anti-aliasing.
From build-83 to build-88: follow the gameplay changes described for these two builds.
After: Dynamic FPS mod bundled and enabled by default; automatic patching is restricted to the supported game build and checks for patch conflicts.
build-83 → build-88
Showing 11–17 of 17 reports
Known issues from Lichii sources
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.
PGO artifact crashes in dynarmic with Unhandled SIGSEGV after 2–10 minutes on the reported machine.
After the startup screen, audio plays but the screen is black.
The emulator closes while loading shaders before a game is opened; the report says it used 20GB of RAM. Reports mention Windows 11 and Linux, and AMD GPUs.
User reports the game crashes after about 15 to 20 minutes.
User reports the game blacks out when booted in build 83; they state it worked in build 75.
The emulator crashes after 5 to 10 minutes of gameplay on Linux with an AMD RX 9000 series GPU.
Clean audio from a different point of the game plays while the intro image is displayed; audio and picture are substantially out of sync.
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.
Textures and surfaces flicker with Low GPU accuracy and EDEN_NX2_SPLIT=2 on Radeon RX 9070 XT; some surfaces remain white temporarily.
Showing 41–50 of 98 issues
Notas de versiones recientes
Versión build-88 · No indicado
Versión build-88 · No indicado
Versión build-88 · No indicado
Versión build-88 · Zelda: Ocarina of Time
Versión build-83 · Ocarina of Time
Elegir una versión
build-83 · Publicada el November 6, 2026
12 archivos para descargar en esta versión.
Prueba la última versión disponible: build-88. 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.