Compatibilidad de juegos

Compatibilidad de juegos con Lichii Emulator

¿Tienes un juego en mente? Comprueba cómo funciona en Lichii, revisa los problemas detectados y elige una versión para probar.

Ocarina of Time en funcionamiento en Lichii Emulator, de la incidencia n.º 201 en GitHub
Fuente: incidencia n.º 201 en GitHub. Ocarina of Time · Captura del juego hecha por la comunidad.
Latest recorded build build-117 Published November 7, 2026

Encuentra un juego

Buscar juegos compatibles con Lichii

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

Game Compatibility Results

Recorded performance

Performance by Build and Hardware

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.

The Legend of Zelda: Ocarina of Time (Switch 2) Reported platform: Windows not booting runs with issues playable 11 reports

Also listed as: OoT, Ocarina of Time

Lichii compatibility reports for The Legend of Zelda: Ocarina of Time (Switch 2)
Build Status GPU / CPU FPS Details
build-93 runs with issues RX 5700 (RDNA1) / Not provided 14–24 FPS Open report
build-93 runs with issues RX 7900XT / Ryzen 7 5700X3D 25–55 FPS Open report
build-93 runs with issues RX 9070 XT / Ryzen 7 9800X3D 14–37 FPS Open report
build-88 runs with issues RTX 4070 Ti 12 GB / Ryzen 7 5800X3D Not provided Open report
Not provided not booting 6700 xt / Not provided Not provided Open report
Not provided runs with issues AMD Radeon RX 6900 XT 16GB / Intel Xeon E5-2697v3 Not provided Open report
nx2-build-88 runs with issues RX 7800 XT / Not provided Not provided Open report
Not provided not booting RX 9060 XT 16gb / Not provided Not provided Open report
build-95 (the release tagged `build-94`) runs with issues RX 5700 / Not provided 14–24 FPS Open report
build-117 (PGO) playable RX 9070 XT / Ryzen 7 9800X3D Not provided Open report

build-93 report

Statusruns with issues
GPURX 5700 (RDNA1)
CPUNot provided
DriverAMD proprietary 2.0.353
Recorded FPS14–24 FPS

Problems or notes: Renders and runs without crash, device loss, or fence timeouts. Commenter reports 22–24 FPS indoors and 14–15 FPS in Kokiri Forest, with outdoor performance described as uncomfortable.

build-93 report

Statusruns with issues
GPURX 7900XT
CPURyzen 7 5700X3D
DriverAll drivers with their latest updates
Recorded FPS25–55 FPS

Problems or notes: Commenter reports stable 25–30 FPS and occasional indoor spikes around 55 FPS; no errors, crashes, or timeouts.

build-93 report

Statusruns with issues
GPURX 9070 XT
CPURyzen 7 9800X3D
DriverAMD Software 26.10.1
Recorded FPS14–37 FPS

Problems or notes: Boots to title and reaches gameplay without crashes or driver timeouts. Reported approximately 18 FPS on defaults, 17 FPS with async shaders on and GPU accuracy Normal, 14 FPS with async shaders on and GPU accuracy High, and approximately 29 FPS with defaults plus the stated logging, process-priority, and Xbox Game Bar capture changes in Kokiri Forest; intro cutscenes run 32–37 FPS. Gameplay is reported in slow motion. Heavy bloom and overexposure occur in bright areas, and the Great Deku Tree appears as a dark silhouette in its intro scene. One Lichii thread reaches 99% of a core.

build-88 report

Statusruns with issues
GPURTX 4070 Ti 12 GB
CPURyzen 7 5800X3D
Driver32.0.16.2101
Recorded FPSNot provided

Problems or notes: Vulkan reached cutscenes; a visible-window run lasted approximately five minutes without a reported TDR. Two hidden/minimized CLI launches crashed in nvoglv64.dll with exception 0xc0000094 at offset 0xEFC9BB. Pipeline-build stalls and cumulative draw-hold time were reported; the measurements are not frame times or FPS.

Not provided report

Statusnot booting
GPU6700 xt
CPUNot provided
DriverNot provided
Recorded FPSNot provided

Problems or notes: A commenter reports an instant crash after trying the EDEN_NX2_NO_MESH=1 workaround.

Not provided report

Statusruns with issues
GPUAMD Radeon RX 6900 XT 16GB
CPUIntel Xeon E5-2697v3
Driver32.0.21045.20006 (Adrenalin 26.10.2)
Recorded FPSNot provided

Problems or notes: On nx2-build-117, the user reports that EDEN_NX2_NO_MESH=1 avoided device loss for a session of about 176 seconds. The variable skipped 27 draws; the user noticed no obvious visual issues but could not rule out missing visuals.

nx2-build-88 report

Statusruns with issues
GPURX 7800 XT
CPUNot provided
Driver32.0.32015.7029
Recorded FPSNot provided

Problems or notes: Disabling mesh draws with EDEN_NX2_NO_MESH=1 did not prevent the device-loss crash on this configuration; it occurred after the intro cutscene.

Not provided report

Statusnot booting
GPURX 9060 XT 16gb
CPUNot provided
DriverNot provided
Recorded FPSNot provided

Problems or notes: Commenters report crashes when attempting the EDEN_NX2_NO_MESH=1 workaround; one says the screen goes black after the intro and the emulator closes. Game version 1.1.1 is stated by another commenter with a separate instant-crash report.

build-95 (the release tagged `build-94`) report

Statusruns with issues
GPURX 5700
CPUNot provided
DriverAMD 2.0.353
Recorded FPS14–24 FPS

Problems or notes: Short session in Kokiri Forest and the Deku Tree rendered correctly, with no crash, fence timeout, device loss, or compute rejections. Reported 14 FPS in Kokiri Forest and 22–24 FPS indoors; the commenter says outdoor performance was identical to build 93.

build-117 (PGO) report

Statusplayable
GPURX 9070 XT
CPURyzen 7 9800X3D
DriverAMD Software 26.10.1
Recorded FPSNot provided

Problems or notes: Commenter reports about 70 minutes of play through the Deku Tree and Gohma with zero blackouts and no Native compute shader rejected (per-tap gather) error, using game version 2.0.0 loaded from a .nup. The same user says blackouts and the log error occurred with extracted base-game version 1.0.0.

Related game issues

Compared with Previous Build

Current: build-93 (4 records); previous: build-88 (1 record).

Showing 261–270 of 308 reports

Known issues from Lichii sources

Known Game Issues

Ocarina of Time

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.

The Legend of Zelda: Ocarina of Time

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.

The Legend of Zelda: Ocarina of Time

Distant mountains remain overexposed with a white glow after the coloured blocks are removed; the source identifies this as a separate bloom/exposure issue.

Ocarina of Time

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.

The Legend of Zelda: Ocarina of Time

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.

Ocarina of Time

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.

Other / not listed

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.

Fire Emblem

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.

The Legend of Zelda: Ocarina of Time

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.

Ocarina of time SW2

AV1 cinematics are delayed, with audio playing faster.

Showing 161–170 of 361 issues

Notas de versiones recientes

Cambios de compatibilidad en las últimas versiones

Elegir una versión

¿Qué versión debo usar?

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

Preguntas frecuentes sobre compatibilidad de juegos

¿Cómo comparto un juego con estos filtros?

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.

¿Qué puedo probar si aparece una pantalla negra?

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.

¿Por qué puede dar resultados distintos la misma GPU?

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.

¿Dónde puedo aportar un resultado que no aparece?

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.