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 |
|---|---|---|---|---|
| build-75 | runs with issues | RTX 5070 Ti / Not provided | Not provided | Open report |
| 99ac3d595 plus listed cherry-picked commits | playable | RTX 5070 Ti / Not provided | 38 FPS | Open report |
Problems or notes: Docked, 1x. User reported missing vegetation, heavy white glow, and visual blotches in tested scenes. Rejecting shaders with EDEN_NX2_REJECT_HASH visibly improved Link and the foreground, but removed bloom accumulation and the river surface.
Problems or notes: Docked, 1x, in front of the Deku Tree in Kokiri Forest. Grass and ferns drew and the heavy haze was gone in a short, still-camera test. Other areas, interiors, cutscenes, long sessions, river rendering, and blotches were not verified. User reported about 38 FPS.
Current: build-75 (1 record); previous: build-70 (0 records).
| Build | Status | GPU / CPU | FPS | Details |
|---|---|---|---|---|
| Frizti v2 (oot-gather-fix @ 765659a) plus port of #204 | runs with issues | NVIDIA RTX 3090 / Ryzen 9 9950X3D | Not provided | Open report |
Problems or notes: Linux 7.0, Vulkan, GPU accuracy Low, docked, 1x, async shaders on. User reported river-water flicker that depended on the sun's position relative to the camera.
| Build | Status | GPU / CPU | FPS | Details |
|---|---|---|---|---|
| nx2 with extra PRs | runs with issues | RX 6650 XT / Not provided | Not provided | Open report |
Problems or notes: Handheld, 1x. During gameplay, user observed zero-format texture assertions and Unmapped Device ReadBlock errors; terrain and subtitles flickered. The user did not establish whether the assertions caused the flicker.
| Build | Status | GPU / CPU | FPS | Details |
|---|---|---|---|---|
| build-83 | playable | RTX 4070 Ti / Ryzen 7 7700X | Not provided | Open report |
| 3724db9a5c | playable | RTX 4070 / i9-12400F | 16 FPS | Open report |
Problems or notes: Vulkan, docked, 2x, GPU accuracy Low, game version 1.1. User reported haze gone and Link and Kokiri Forest clearly visible in gameplay, but FPS was described as low. Handheld mode was not tested.
Problems or notes: Vulkan, docked, 1x. User reported grass visible and the tree clearly visible through grey fog in front of the Deku Tree; 16 FPS was a single in-game counter reading.
From build-75 to build-83: follow the gameplay changes described for these two builds.
Before: Missing vegetation and incorrect material data; affected lighting and colours; a glowing doorway; one-frame white flashes; and on AMD, shaders could produce a black 3D scene.
After: Additional shader pointers and storage-buffer bindings, corrected buffer tracking and mesh-shader register handling, fixed occlusion-query and nested-return handling, and added the Max Resolution add-on and frame-ahead presentation tuning.
build-75 → build-83
| Build | Status | GPU / CPU | FPS | Details |
|---|---|---|---|---|
| 8813b44 | runs with issues | RX 6800 XT / Not provided | Not provided | Open report |
Problems or notes: At 1x in Link's house and Kokiri Forest, user reported blotches from a half-resolution layer. A diagnostic depth-clear change removed the blotches in Link's house, but the river water remained dark with ripples and no visible lit contribution.
| Build | Status | GPU / CPU | FPS | Details |
|---|---|---|---|---|
| build-80 | runs with issues | AMD RX 6700 XT / Not provided | Not provided | Open report |
Problems or notes: Docked, 1x. The opening cinematic and title screen rendered correctly, but the Deku Tree exterior cutscene remained black except for Navi's light radius. User also reported a deterministic AMD driver crash while building graphics pipelines in that scene.
| Build | Status | GPU / CPU | FPS | Details |
|---|---|---|---|---|
| 62ba83427e | runs with issues | Radeon 8060S / Ryzen AI MAX+ 395 | 31–37 FPS | Open report |
Problems or notes: Docked, 1x, Kokiri Forest. User reported haze, blotches, and a translucent band. Rejecting fog and layer shaders removed some artifacts but also removed in-game fog and darkened the river. Two starts remained black from launch, one with music playing; closing and reopening cleared the black screen.
| Build | Status | GPU / CPU | FPS | Details |
|---|---|---|---|---|
| b4716fc | runs with issues | RX 6700 XT / Not provided | Not provided | Open report |
Problems or notes: Docked, 1x. The Deku Tree exterior cutscene showed a black screen except for a small circle around Navi; the title screen and earlier cinematics rendered correctly.
Showing 1–10 of 77 reports
Known issues from Lichii sources
Boots to a black screen with audio on macOS.
Recorded fix: Clear the cache and launch again.
On Radeon RX 580, hangs at a black screen at 0 FPS while building compute pipelines as the intro video starts.
Black screen after starting a new game, with audio continuing; a commenter also reports an FFmpeg error stating there is no decoder for video/av1.
Recorded fix: A commenter reports that using the MSVC build instead of the PGO build worked for them. Other commenters report that shared settings resolved the black screen, and one reports that switching from handheld to docked mode resolved it.
Very low FPS and graphics problems, including missing textures, lighting or ambient occlusion issues, and a blown-out white image.
With use_disk_shader_cache = true, subsequent boots hang indefinitely at Loading Shaders 25 / 27.
Recorded fix: Delete cache/shader/0400486024dec000 and set use_disk_shader_cache = false; the reporter says this resolves the startup freeze.
Black screen after the intro on AMD RX 9070 XT; the game's 1080p upscaler shader is rejected.
Recorded fix: Comment reports that #112 fixes the shader rejection; its CI build is fix/oot-upscaler-gathers / 7459f10 (build-80), and the fix is on nx2, but not in a release yet.
On AMD, the world is black except around Navi and Link; an RX 6800 XT reporter says the workaround still leaves all 3D geometry black.
Recorded fix: Comment reports that #127 fixes AMD-only demote reordering. Before it is merged, setting EDEN_NX2_REJECT_HASH=e40561a7a0f7a0b3 in %APPDATA%\eden\nx2_switches.txt makes the world visible on the RX 9070 XT report; another reporter says it does not resolve 3D rendering on the RX 6800 XT.
Texture flicker with Low GPU accuracy and GPU thread split on AMD RX 9070 XT.
Handheld mode is reported as much brighter and blurrier than Docked mode.
User reports heavily distorted speech, music, and effects (“robot voice”) on build 70. Comments clarify that the approximately 0.7032 accepted/copied ratio reflects retries rather than lost samples; possible causes discussed include emulated time running ahead of wall time or slow host audio draining, but the cause is not confirmed.
Showing 61–70 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-75 · Publicada el November 5, 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.