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 | 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 |
| Not provided | unknown | RTX 5060 / Not provided | Not provided | Open report |
| Not provided | playable | RTX 4090 / Ryzen 9 7950x3D | Not provided | Open report |
| Not provided | runs with issues | Integrated graphics AMD (Radeon 860M, Ryzen AI 7 350, RADV / Mesa) / Ryzen AI 7 350 | 22–23 FPS | Open report |
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.
Problems or notes: The user says the game cannot run at 60 fps in the base village; no actual FPS or gameplay-start status is stated.
Problems or notes: A commenter reports freezes of about 3 seconds with each step due to shader compilation. Another commenter says the game is completely playable for them and describes shader-compilation stuttering; no performance or sustained-play details are provided.
Problems or notes: During gameplay, the texture collector remains in aggressive mode, causing heavy image creation/deletion churn and frequent full GPU waits. Reporter measured 22.3 fps in two default runs and 22.5 fps in two override runs; these are standing FPS measurements, not a general performance result.
Current: build-117 (2 records); previous: build-116 (0 records).
Also listed as: OoT
| Build | Status | GPU / CPU | FPS | Details |
|---|---|---|---|---|
| build-93 | runs with issues | AMD Radeon RX 6900 XT / AMD Ryzen 9 5900X | 24–30 FPS | Open report |
| chuppatricky-amd-testbuild-v13 | not booting | AMD Radeon RX 6700 XT (12 GB) / AMD Ryzen 9 5900X | Not provided | Open report |
| build 97 | runs with issues | AMD RX 9000 series / Not provided | ?–20 FPS | Open report |
| Frizti v3 (tag: frizti-v3, based on Lichii nx2) | runs with issues | NVIDIA RTX 30 series or older / Not provided | Not provided | Open report |
| build 95 (222877d) | unknown | AMD RX 9000 series / Not provided | Not provided | Open report |
Problems or notes: Severe lighting flickering and overexposure or corrupted lighting effects; significant slowdowns in some sequences; audio desynchronization during cinematics; initial shader compilation takes considerable time. The user reports approximately 24 FPS in Kokiri Forest and approximately 30 FPS in menus and some cinematics.
Problems or notes: User reports the emulator closes without an error message after about 9–10 minutes of shader rebuilding on first launch. Windows reports exception code 0xc0000005 in amdvlk64.dll. The user says the same fault offset occurred across several launches.
Problems or notes: Around 20 FPS with large variance, bright light/haze-like artifacts, and desynchronized, stuttering audio after gameplay starts. The steps specify Lichii build 93 (MSVC Windows package), while the emulator build field says build 97.
Problems or notes: A massive white bloom streak blows out the upper-left quadrant of the screen in Kakariko Village during daytime; a commenter reports similar effects in the well, later areas, and frozen Zora's domain.
Problems or notes: Extract NUP fails when the output path is 264 characters long, reporting Extraction Failed.
Current: build-93 (1 record); previous: build-88 (0 records).
Showing 41–50 of 132 reports
Known issues from Lichii sources
On AMD Radeon RX 9070 XT with driver 2.0.416, a dotted cyan/magenta line appeared along mountain and sky silhouettes in Hyrule Field.
Recorded fix: Zero the color write mask of render targets the fragment shader does not store; the issue comment says this fix landed in build 95.
Coloured blocks or a magenta line along the Hyrule Field mountain ridge on AMD GPUs; the original report described NaNs in the scene target that bloom spread into a coloured band.
Recorded fix: The #353 per-component write-mask fix was reported to remove the coloured blocks or line. A temporary workaround is to set EDEN_NX2_REJECT_HASH=fe1f903f1bf52a9d,4f5673eca06ebecb, which drops the draw and loses its far-distance effect.
Distant mountains remain overexposed with a white glow after the coloured blocks are removed; the source identifies this as a separate bloom/exposure issue.
On Linux with AMD RX 9000-series graphics using RADV, an invalid SPIR-V fragment shader can cause a segfault during Vulkan graphics-pipeline construction during gameplay.
Recorded fix: Fixed in build 93 and later releases.
On AMD's proprietary Windows Vulkan driver, the intro could freeze while two compute shaders were optimized, taking 6–18 minutes; long graphics-pipeline builds can also cause substantial in-game stalls.
Recorded fix: Build 93 and later build the two identified compute shaders without driver optimization on AMD's proprietary Vulkan driver. The source says long graphics-pipeline builds are a separate matter and are not covered.
On earlier builds, small details such as leaves, pebbles, and grass flickered or appeared black with Low GPU accuracy and the split GPU thread enabled.
Recorded fix: Update to build 95 or later; the source attributes the fix to buffer usage tracking changes, with additional near-foliage fixes. EDEN_NX2_PERF_VERIFY=1 was an earlier workaround but was reported as no longer needed on build 95.
A user reports that games do not work on a Lenovo Legion Go 2 Z2 with an eGPU 7600xt on Version 95; on Version 93 or earlier, they can see the scene.
On Linux with AMD graphics, Fire Emblem: Fortune's Weave can crash after a black screen with VK_ERROR_DEVICE_LOST and a GPU reset.
On Windows 11, extracting a NUP to a path longer than 260 characters fails even when LongPathsEnabled is set. The issue reports a malformed longPathAware manifest entry as the probable cause.
AV1 cinematics are delayed, with audio playing faster.
Showing 161–170 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
build-117 · Publicada el November 7, 2026
12 archivos para descargar en esta versión.
build-93 · Publicada el November 6, 2026
7 archivos para descargar en esta versión.
build-88 · Publicada el November 6, 2026
7 archivos para descargar en esta versión.
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.