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 |
|---|---|---|---|---|
| build-116 | playable | Not provided / Not provided | 60 FPS | Open report |
Problems or notes: Not provided
Current: build-116 (1 record); previous: build-94 (0 records).
| Build | Status | GPU / CPU | FPS | Details |
|---|---|---|---|---|
| build-116 | runs with issues | NVIDIA RTX 30 series or older; 306012gb / 3600x | Not provided | Open report |
Problems or notes: The user reports broken frame generation, general lag and stuttering, a 10–12 FPS drop compared with build 93, and texture-cache data being overwritten. They say the game became unplayable for them.
Current: build-116 (1 record); previous: build-94 (0 records).
| Build | Status | GPU / CPU | FPS | Details |
|---|---|---|---|---|
| build-116 | runs with issues | Not provided / Not provided | Not provided | Open report |
Problems or notes: Characters look too dark, there is a green tint, and FPS is lower than in earlier builds; the issue is being investigated.
Current: build-116 (1 record); previous: build-94 (0 records).
Also listed as: OoT, Ocarina of Time
| Build | Status | GPU / CPU | FPS | Details |
|---|---|---|---|---|
| build-116 | playable | Not provided / Not provided | 60–? FPS | Open report |
Problems or notes: The release says many users get 60+ fps. With DLSS on, Navi, fireflies, and smoke can leave trails at night. AMD Radeon RX 6000 series and older on Windows crash while building shaders after boot; the release says this is fixed in build 117.
Current: build-116 (1 record); previous: build-94 (0 records).
Showing 1–4 of 4 reports
Known issues from Lichii sources
When fastmem could not be created, guest code ran about 1.4x slower; Kokiri Forest ran at 22.2–26.6 FPS rather than 28.5–33.8 FPS. The report attributes the slow boots to failure to allocate 14336 MiB of backing memory.
Recorded fix: Change #645 retries the section after a private commit that grows the page file; in eight back-to-back boots, all three initial failures recovered on the second attempt and none ran slowly.
Graphics fail to load in the Water Temple; a commenter describes the area as unplayable.
Recorded fix: A commenter reports resolving the issue by using a NUP containing the missing texture files, described as 23.8 GB rather than 23.3 GB.
Many Water Temple rooms are invisible, with transparent walls. A comment attributes this to a damaged texture file in the game dump; another user reports the issue was resolved by making a fresh dump with a NUP with a higher file size.
On AMD Windows proprietary drivers, older builds can lose the GPU device when gameplay or a save starts; build-83 and build-88 reports include this problem.
Recorded fix: A Windows RX 9060 XT report found the issue absent in build-93. A Windows RX 7900 XTX report also found it absent in the CI build at 18cfe85.
On AMD RADV Mesa 26.2.4, task/mesh shader use can hang the GPU and cause device loss during 3D gameplay.
Recorded fix: The reporter found that updating to Mesa RADV 26.2.6 avoided the hang on the same GPU with the same build. If using a distrobox in gamescope gaming mode, the reporter says to install the gamescope package in the container so its Vulkan WSI layer is present.
On build-95, the user reports draws held while unbuilt pipelines are being built, causing multi-second stalls, even with async shaders enabled.
The user reports that a fresh build-95 config starts with slow defaults, including High GPU accuracy, asynchronous shaders off, async presentation off, Handheld mode, 4 GB memory layout, and CPU NVDEC; the game ran at 10–15 fps with stalls up to 8.9 s and blurry/pixelated Handheld resolution.
Recorded fix: The user reports that writing the six listed settings before launch helped: gpu_accuracy=0, use_asynchronous_shaders=true, async_presentation=true, nvdec_emulation=2, memory_layout_mode=2, and use_docked_mode=1; set each key's \default= line to false as well.
User reports a black-screen stall after the first AV1 frame with async GPU emulation enabled on AMD Radeon RX 6800 XT; with async GPU emulation disabled, the game later froze during gameplay.
Users report failure to start, black screens with 0 FPS, or emulator crashes in builds 88–95, including a build-95 Linux report with an unhandled SIGSEGV and null-pointer dereference. The comments caution that the reports may have different causes.
The user reports performance remaining at 20 FPS with music glitches on macOS.
Showing 121–130 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.