Other / not listed
Deku has black textures on some parts during the cinematic, with stuttering, bloom and artifacts when jumping. Dynamic FPS makes the game run too fast (about 2x speed); without it, gameplay is almost in slow motion.
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 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
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 |
|---|---|---|---|---|
| build-75 | runs with issues | NVIDIA GeForce RTX 5080 (16 GB) / Intel Core Ultra 7 270K Plus (24 threads) | 28–29 FPS | Open report |
Problems or notes: User report: Docked mode was required to render; Handheld showed a black 3D screen. Gameplay settled at 28–29 FPS, while menus and loading screens ran at 53–59 FPS. The report attributes the limit to CPU load. No attempted settings changes improved the gameplay ceiling.
Current: build-75 (1 record); previous: build-70 (0 records).
| Build | Status | GPU / CPU | FPS | Details |
|---|---|---|---|---|
| build-75 | runs with issues | NVIDIA RTX 3050 Laptop / AMD Ryzen 7 5800H | 30 FPS | Open report |
Problems or notes: User report: The game boots and presents frames at a steady 30 FPS, but remains on a black screen after its AV1 video streams fail because FFmpeg has no decoder for "video/av1". NVDEC Off and Gpu reportedly make no difference; the same result was reported on an AMD Radeon iGPU. Vulkan was used.
Current: build-75 (1 record); previous: build-70 (0 records).
| Build | Status | GPU / CPU | FPS | Details |
|---|---|---|---|---|
| 75 (`nx2-build-75`, Linux x86_64 PGO AppImage) | runs with issues | AMD RX 7000 series (Radeon RX 7600, RADV 26.2.5, Vulkan 1.4.354) / Not provided | Not provided | Open report |
Problems or notes: During the intro AV1 cutscene, the video area is solid green; audio and subtitles work. The report says decoded frames are produced at 60 fps, but the image does not reach the screen.
| Build | Status | GPU / CPU | FPS | Details |
|---|---|---|---|---|
| `nx2-build-75`, MSVC x86_64 (`lichii-windows-x86_64.zip`) | runs with issues | AMD Radeon RX 6700 XT 8 GB, AMD driver 2.0.353, Vulkan 1.4.315 / AMD Ryzen 7 5800X, 32 GB RAM | Not provided | Open report |
Problems or notes: The game renders normally before the intro AV1 cutscene, but the video layer is black while audio and subtitles work, then the emulator hangs indefinitely. The report says the freeze starts when the AV1 decoder opens.
Also listed as: OoT
| Build | Status | GPU / CPU | FPS | Details |
|---|---|---|---|---|
| Not provided | playable | RTX 4070 SUPER / Not provided | 59.3–60 FPS | Open report |
Problems or notes: A commenter reports no texture flicker during roughly six minutes of gameplay with Low GPU accuracy and EDEN_NX2_SPLIT=2; light scenes reached the game's 60 FPS cap.
| Build | Status | GPU / CPU | FPS | Details |
|---|---|---|---|---|
| build-75 | runs with issues | Adreno 740 / Snapdragon 8 Gen 2 | Not provided | Open report |
Problems or notes: Black screen despite booting to the AV1 video stage; pipeline-builder threads remain busy compiling large compute shaders, with memory exhaustion or GPU hangs reported in tests. Audio was intermittent. In a separate Eglantine PR #614 test, it reached the title screen and New Game, then went black at the first in-game frame at about 60 FPS.
Current: build-75 (1 record); previous: build-70 (0 records).
| Build | Status | GPU / CPU | FPS | Details |
|---|---|---|---|---|
| build-93 | runs with issues | AMD RX 9000 series / Not provided | Not provided | Open report |
| build-93 | runs with issues | RTX 3060 Ti / Intel Core i7-12700 | 19–31 FPS | Open report |
| build-93 | runs with issues | NVIDIA RTX 50 series; AMD RX 9060 XT 16gb graphics card / Not provided | Not provided | Open report |
| build-75 | not booting | AMD Radeon RX 6750 XT (RDNA2) / Intel Core i7-11700F | Not provided | Open report |
Problems or notes: The emulator closes when loading Hyrule Market after the user exits Kokiri Forest and enters Hyrule Castle.
Problems or notes: About 31 FPS on average, down to about 19 FPS, with short freezes while attacking in crowded scenes. The report attributes performance stalls to front/back GPU thread serialization. With EDEN_NX2_PRELOAD_ALL_PIPELINES=1, runtime pipeline builds fell from 942 to 65 and frames over 100 ms fell from 77 to 40 during the reported session.
Problems or notes: The user reports textures not working properly, slow frame rate, and a shield glitch. They also report that trying a '.dat' file did not work. The issue body gives conflicting GPU details.
Problems or notes: On Windows 11 25H2, the game passes the initial launching stage but becomes unresponsive at “Building 9 shaders”; audio continues and it does not reach gameplay. The report identifies the game as Switch 2 version 1.1.1.
Current: build-93 (3 records); previous: build-88 (0 records).
Showing 1–10 of 58 reports
Known issues from Lichii sources
Deku has black textures on some parts during the cinematic, with stuttering, bloom and artifacts when jumping. Dynamic FPS makes the game run too fast (about 2x speed); without it, gameplay is almost in slow motion.
User reports the emulator hangs and crashes at 11/14 shaders loaded on Linux with AMD graphics when booting the game in Build-88 or Build-93.
User reports a performance regression in Build 75 on Linux with an AMD RX 6000 series or older GPU: around 10 FPS on the title screen, barely reaching 15 FPS with constant stuttering, GPU usage at 100%, and RAM usage increasing nonstop.
In the shield tutorial, holding ZL is not detected and the tutorial loops. The user reports the same issue after rebinding ZL to L or switching to keyboard.
Black screen and GPU deadlock after an unsupported native QMD compute dispatch; GPU channels wait on the semaphore the QMD was supposed to release.
Shrubbery, bushes, and grass turn dead-looking when approached in Hyrule Castle, especially in Zelda's garden. A user reports that it still occurs in build 83.
White haze over Hyrule Field and the sky on AMD cards, attributed by a commenter to froxel fog reading light probes beyond a 64 MiB read-only storage binding.
Recorded fix: A commenter says the issue was fixed in #351.
On Windows 11 with an AMD Radeon RX 6700 XT and AMD Software (Adrenalin) 26.10.2, Lichii closes during shader rebuilding with an access violation in amdvlk64.dll.
In build 93, the user reports controller input is hijacked about every 30 seconds, causing the character to run into a wall. The user says this did not happen in build 92.
Poor frame rates; the issue says performance is worse than on most other forks.
Showing 91–100 of 188 issues
Notas de versiones recientes
Versión build-94 · Ocarina of Time
Versión build-94 · No indicado
Versión build-94 · No indicado
Versión build-94 · No indicado
Versión build-94 · No indicado
Elegir una versión
build-93 · Publicada el November 6, 2026
7 archivos para descargar en esta versión.
build-75 · Publicada el November 5, 2026
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
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.