Instalación y solución de problemas
Desde la descarga hasta el primer inicio, configura los controles, añade tus juegos y resuelve los problemas que te impidan continuar.
Tres plataformas
Elige tu plataforma para seguir la instalación paso a paso.
¿Necesitas otro paquete? Ver descargas para windows.
¿Necesitas otro paquete? Ver descargas para linux.
¿Necesitas otro paquete? Ver descargas para macos.
Primer inicio
Configura Lichii desde el primer inicio: elige una asignación de botones que te resulte cómoda, ajusta los gráficos y prepara tu biblioteca de juegos.
Empieza con los ajustes gráficos que indican las notas de tu versión. Cambia un solo ajuste cada vez y anota la etiqueta de la versión junto con cualquier resultado que registres.
Para tener un punto de partida para un juego concreto, consulta su informe de compatibilidad.
Conecta el mando, asigna los botones y guarda el perfil. Si algún botón no funciona, busca el modelo de tu mando y la versión de Lichii en la sección de solución de problemas.
Añade los juegos que hayas obtenido legalmente desde la biblioteca o con la opción de abrir archivos de juego de Lichii. Los juegos, las claves y el firmware se obtienen por separado.
Vuelve a jugar
128 registros de problemas
Ningún problema coincide con la búsqueda. Consulta las notas de la versión o prueba con el texto exacto del error.
GitHub issue · open
On macOS arm64 through MoltenVK, the Metal device may be lost or the GPU thread may hang at the intro-video/gameplay boundary. A commenter attributes the device loss to an attachment-less framebuffer reaching 32768×32768, above the stated Apple GPU limit of 16384.
GitHub issue · open
After a local workaround for device loss, a commenter reports that the 3D scene remains black while sound and subtitles work on an older Eglantine fork; current nx2 behavior was not yet checked.
GitHub issue · open
In stages past the first one, the gameplay screen is black while the UI remains visible; pausing shows the world rendered in the background.
GitHub issue · open
User reports a crash when opening the game on Arch Linux with an AMD Radeon AI PRO R9700 (9070XT); the console reports a segmentation fault.
GitHub issue · open
User reports audio/video desynchronization during the opening cutscene and a system freeze at the Deku Tree cutscene on Vulkan with an AMD RX 9000 series GPU. Comments report crashes on AMD GPUs, including while building shaders. One commenter reports that OpenGL GLSL stops the crashes but leaves only the UI visible.
GitHub issue · open
On some AMD GPUs, the UI may remain visible while the 3D world is black; reports also describe AMD driver timeouts or crashes.
GitHub issue · open
A user reports black visuals except for the UI after starting a new game, while audio is audible.
GitHub issue · open
A commenter reports that the PGO build produces a black screen in both docked and handheld modes.
GitHub issue · open
While booting an unidentified "little green hat adventure game," the emulator reports an error initializing the video core, suggesting outdated GPU drivers. On OpenGL, the game launches but shows a black screen while sound works. The reporter says their RX 9070XT drivers are updated; a commenter reports the same problem with a 7000 series GPU.
GitHub issue · closed
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.
GitHub issue · open
Only character outlines and UI are visible after launching the game.
GitHub issue · open
User-reported reproducible freeze when walking deeper into the pot room in Hyrule Castle Town, near the guard.
GitHub issue · open
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.
GitHub issue · open
User reports describe gameplay performance below 60 FPS on multiple systems and builds. One report also describes a black 3D screen in Handheld mode; switching to Docked allowed rendering.
GitHub issue · open
A user report says resolution 2X caused flicker or line artifacts; a separate candidate-build report says the release's overexposure warning was not cleared by its limited test.
GitHub issue · open
The issue reporter using an AMD RX 6600 8GB on Windows 10 reports that the emulator starts loading and then remains on a black screen.
GitHub issue · open
Commenters report rendering failures, black screens, and AMD driver crashes; one reports that audio continues while rendering is crashed.
GitHub issue · open
A half-resolution layer drawn by pixel shader c72b6ea746c00433 causes dark blotches and translucent patches over objects in reported scenes. Users traced the issue to an occlusion-depth copy being wiped by deferred clears before the layer samples it.
Solución sugerida: A user-reported workaround is EDEN_NX2_REJECT_HASH=c72b6ea746c00433; it removes the blotches in tested scenes but removes the river's visible water surface. Another user described PR #185 as fixing the ordering issue, but did not provide a tested result for that fix.
GitHub issue · open
The Deku Tree exterior cutscene can render black except for a small area around Navi; a user also reported an AMD graphics-driver crash while building graphics pipelines in that scene.
GitHub issue · open
Users reported missing grass, ferns, and broadleaf vegetation, with associated haze or overexposure in Kokiri Forest. A user reported that a local build with listed rendering commits restored grass and ferns and removed heavy haze in one location; a later comment proposed PR #204 for stale occlusion-query reads, but did not report a test result for that PR.
GitHub issue · open
A user reported river-water flicker depending on sun direction relative to the camera; the proposed link to lighting or light volumes was unconfirmed.
GitHub issue · open
A user reported zero-format texture assertions, Unmapped Device ReadBlock errors, and flickering terrain and subtitles; causation was not established.
GitHub issue · open
On AMD RDNA2 GPUs, the game may freeze during shader or pipeline building, sometimes with background audio continuing. A commenter also reports black-screen or shader-building hangs with asynchronous shader compilation enabled.
GitHub issue · open
On AMD's proprietary Windows driver, two compute pipelines can take 6 to 18 minutes to compile during the intro, leaving the game at 0 FPS while audio continues. Rejecting the shader hashes avoids the wait but causes black areas in the intro, title, and castle scenes.
Solución sugerida: Leave the game at the intro for about 20 minutes once so both pipelines finish and are cached; later boots reportedly pass the intro immediately until the driver or Lichii is updated. Alternatively, set `EDEN_NX2_REJECT_HASH=eff3ccbe1438679d,f9ea14a22394f5b1`; this avoids the wait but leaves parts of the picture black.
GitHub issue · open
In the measurement-only experiment, disabling per-fence Preflushable downloads or batching downloads by 64 fences caused overexposure in Kokiri Forest.
GitHub issue · open
A commenter reports that an experimental compute storage write-extent analysis reduced marked GPU-written data and fence copies while preserving correct auto-exposure. It was described as code on a user's branch, not as an upstream or validated release fix.
GitHub issue · open
Static review and a separate research comment describe read-trap bookkeeping and dirty-state issues that can leave stale GPU-written data when per-fence downloads are disabled; proposed corrections and batching remain untested or local experiments.
GitHub issue · open
Slows when booting.
GitHub issue · open
Community comments describe AMD black or corrupted-world output, fragment-pipeline compiler crashes on Windows, later timeouts or TFB stalls, corrupted output, and a RADV depth-image SPIR-V failure. These are separate reported cases; the comments do not establish a universal cause or resolution.
GitHub issue · open
User reports a segfault during gameplay on Linux with an AMD RX 9000-series GPU and RADV, when a graphics pipeline is built for an invalid fragment shader.
GitHub issue · open
GitHub issue · open
User reports repeated crashes around Deku Tree, followed by booting getting stuck compiling shaders; deleting the shader cache allows booting again. Another user reports the problem only with RADV.
Solución sugerida: Deleting the shader cache allows booting again, according to the user report.
GitHub issue · open
On Windows build-83, shutdown can hang at “Closing software…” after gameplay. Some sessions completed shutdown successfully; the cause is undetermined.
GitHub issue · open
A user reports missing textures and buggy visuals after booting, occasional startup crashes, and crashes when playing the Grand Prix race on build-83 with Intel integrated graphics on Windows 11.
GitHub issue · open
GitHub issue · open
Persistent graphics pipeline cache entries are reportedly rebuilt on the GPU thread during gameplay on repeated boots, causing a visible hitch.
GitHub issue · open
With GPU Mode: Accurate (High), gameplay may run in slow motion at about 30 FPS; shader compilation can cause stutter on new content.
Solución sugerida: Set GPU Mode to Fast; the commenter reports this resolved the slow gameplay for their setup.
GitHub issue · open
The issue title says “literally The Legend of Green,” but the game field is “Other / not listed”; no specific compatibility symptom is stated.
GitHub issue · open
Black screen after boot; some reports say sound and the title/logo work.
GitHub issue · open
On build-83, one user reports a solid-green displayed image although a screen capture shows the game rendering correctly.
GitHub issue · open
On build 83, a user reports device loss at gameplay start with VK_ERROR_DEVICE_LOST.
GitHub issue · open
User reports GPU driver timeout or device loss when gameplay starts on AMD Windows systems, including RX 7900 XTX and RX 9060 XT. Reports associate the issue with #150 pointer-binding changes, but this is an unconfirmed hypothesis.
GitHub issue · open
PGO artifact crashes in dynarmic with Unhandled SIGSEGV after 2–10 minutes on the reported machine.
GitHub issue · open
After the startup screen, audio plays but the screen is black.
GitHub issue · open
GitHub issue · open
The emulator closes while loading shaders before a game is opened; the report says it used 20GB of RAM. Reports mention Windows 11 and Linux, and AMD GPUs.
GitHub issue · open
User reports the game crashes after about 15 to 20 minutes.
GitHub issue · open
User reports the game blacks out when booted in build 83; they state it worked in build 75.
GitHub issue · open
The emulator crashes after 5 to 10 minutes of gameplay on Linux with an AMD RX 9000 series GPU.
GitHub issue · open
Clean audio from a different point of the game plays while the intro image is displayed; audio and picture are substantially out of sync.
GitHub issue · open
On build-75, user reports over-bright bloom/glow, overly dense fog, incorrect lighting, and some textures decoded as garbage; logs include macro-parameter assertions and an unknown texture format 100.
GitHub issue · open
Textures and surfaces flicker with Low GPU accuracy and EDEN_NX2_SPLIT=2 on Radeon RX 9070 XT; some surfaces remain white temporarily.
GitHub issue · open
Outdoor haze is very strong, and the river surface can appear dark or black.
GitHub issue · open
A commenter reports being unable to load a save, with the PC hard-locking or freezing before recovering after a driver crash or timeout; same GPU, 32GB RAM, and i7 9700K.
GitHub issue · open
On Windows builds 70 and 75, terrain/world renders solid white while the HUD and characters still render. On build 75, EDEN_NX2_RESETFIX=0 changes the ground to black with no texture or lighting.
GitHub issue · open
GitHub issue · open
The emulator force quits after being stuck on the "Loading Shaders" screen for about 2 seconds.
GitHub issue · closed
The 3D gameplay scene can appear black while the HUD remains visible.
Solución sugerida: Switch to Docked mode; one commenter reported this resolved the black screen. Other reports say this workaround did not help.
GitHub issue · closed
A commenter reported stuttering, FPS drops, and overexposure after switching to Docked mode.
GitHub issue · closed
A commenter reported flickering shadows and trees with no leaves.
GitHub issue · closed
A commenter reported audio playing ahead of the video during the intro.
GitHub issue · open
Black screen after the first cutscene in handheld mode and VHS-like visual filter in docked mode.
GitHub issue · open
After the intro, the scene where the deku tree is talking is completely black with very slow, stuttery dialogue.
GitHub issue · open
GitHub issue · closed
Boots to a black screen with audio on macOS.
Solución sugerida: Clear the cache and launch again.
GitHub issue · open
On Radeon RX 580, hangs at a black screen at 0 FPS while building compute pipelines as the intro video starts.
GitHub issue · open
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.
Solución sugerida: 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.
GitHub issue · open
Very low FPS and graphics problems, including missing textures, lighting or ambient occlusion issues, and a blown-out white image.
GitHub issue · open
With use_disk_shader_cache = true, subsequent boots hang indefinitely at Loading Shaders 25 / 27.
Solución sugerida: Delete cache/shader/0400486024dec000 and set use_disk_shader_cache = false; the reporter says this resolves the startup freeze.
GitHub issue · open
Black screen after the intro on AMD RX 9070 XT; the game's 1080p upscaler shader is rejected.
Solución sugerida: 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.
GitHub issue · open
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.
Solución sugerida: 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.
GitHub issue · open
Texture flicker with Low GPU accuracy and GPU thread split on AMD RX 9070 XT.
GitHub issue · open
Handheld mode is reported as much brighter and blurrier than Docked mode.
GitHub issue · open
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.
GitHub issue · open
On Linux with AMD/RADV, AV1 intro cutscene video renders solid green while audio and subtitles work.
GitHub issue · open
On Windows 10 with AMD, the intro AV1 cutscene shows a black video layer with working audio and subtitles, then the emulator hangs indefinitely.
GitHub issue · open
Black screen or intermittent black-screen flashes during gameplay and GDT; additional reports describe distorted docked rendering, overly bright and low-resolution handheld rendering, and intro audio ahead of video.
GitHub issue · open
A local ClangCL build of b8c812b18 stalled at max present 8 and showed no frames; a local MSVC build of the same commit stalled at max present 8 and died within a minute, unlike the reported build-75 release.
GitHub issue · open
clang-cl configure/compile failures are reported from min/max macros exposed by windows.h and direct FARPROC-to-function-pointer casts.
Solución sugerida: The commenter says PR #164 contains the NOMINMAX/WIN32_LEAN_AND_MEAN definitions and two FARPROC cast changes that resolved the compile failures.
GitHub issue · closed
User reports a black background at the title screen and a black screen after starting a new game, with sound still audible.
GitHub issue · open
User reports audio/video desynchronization on the title screen and intro; a commenter reports slow-motion live-rendered title-screen video with audio leading by approximately three seconds, worsening by the initial dream cutscene.
GitHub issue · open
User reports a black screen after the game's AV1 video streams fail to decode; FFmpeg reports no decoder for "video/av1". The game idles indefinitely on a black frame.
GitHub issue · open
Music disappears during the cutscene after booting the game.
GitHub issue · open
In gameplay, the world renders almost entirely black, with only the HUD and some areas near light sources visible; some shapes appear blown out with heavy bloom.
GitHub issue · open
The game crashes while building shaders after the title card fades.
GitHub issue · open
On Adreno 740 with Turnip, large native compute-shader pipelines can keep Vulkan pipeline-builder workers busy, consume substantial memory, and result in a black screen; some tests also reported GPU hangs or device loss.
GitHub issue · open
The emulator closes about a minute after gameplay begins on Windows 11 with an NVIDIA RTX 50 series GPU.
GitHub issue · open
An error appears after the cinematic and remains on screen, blocking the view.
GitHub issue · open
GitHub issue · open
Black screen during cinematic after the main menu appears; reported on Windows 11 with an AMD RX 6000 series or older GPU.
GitHub issue · open
GitHub issue · open
On linux-aarch64, the PGO AppImage logs `assert r > 0` during ZBIC NSO decompression and does not present a frame for the reported game. The non-PGO AppImage of the same commit has no such assertions and decompresses the same game without errors. The issue report does not identify the game by name.
GitHub issue · open
Users report crashes before the training mission begins and during the campaign.
GitHub issue · open
Infinite startup launch loop when booting the .NUP version.
GitHub issue · open
Issue reporter says Zelda Ocarina Of Time Remake stays on "Launching..." indefinitely; the log records an emulated program break with error F001. Other reports mention an infinite launch screen.
GitHub issue · open
A user reports severe shader problems with white visuals; handheld mode shows a black screen.
GitHub issue · open
A user reports a black screen past the title screen.
GitHub issue · open
A user reports repeated Unmapped Write64 errors, possible audio popping, and an emulation crash when closing the game.
GitHub issue · closed
The 3D gameplay scene is black while HUD elements remain visible; menus and item preview can render correctly.
GitHub issue · closed
GitHub issue · open
Terrain is visible through solid objects after getting past the intro.
GitHub issue · open
FMVs and pre-rendered videos are skipped, including the opening cut-scene.
GitHub issue · open
On build 70 (286117c), the MSVC zip aborts after 133.8 seconds of gameplay with 0xC0000409 at lichii.exe+0x2ecd3bd. The MinGW PGO zip reportedly aborts on the intro screen at the same offset.
GitHub issue · open
A black rectangle appears in a mini-example guide; the reporter says it persists on build-70.
GitHub issue · open
GitHub issue · open
GitHub issue · open
Weird artifacts, especially on shadows.
GitHub issue · open
GitHub issue · open
User reports a black screen while loading in Build 65.
GitHub issue · open
Freezes while menu preview videos play on build 65. A comment reports a custom kirby-test build log showing the game aborting (2162-0001) during menu videos.
GitHub issue · open
GitHub issue · open
GitHub issue · open
GitHub issue · open
GitHub issue · open
GitHub issue · open
GitHub issue · open
GitHub issue · closed
GitHub issue · closed
Lichii release
An existing fence-worker shutdown race can leave the emulator waiting during shutdown; it was reproduced during testing and is unchanged by this release.
Lichii release
Outdoor areas have far too much fog and glow compared with console; performance is about 12–22 fps on a Ryzen 5900X with an RTX 3080, and three rare shaders remain unsupported.
Lichii release
On RTX 50-series GPUs, the GPU device can still be lost after a scene change.
Solución sugerida: Try NVIDIA driver 610.88.
Lichii release
“Failed to allocate 14336 MiB of backing memory” means Windows ran out of RAM plus page file.
Solución sugerida: Set the page file to system-managed.
Lichii release
Gameplay is capped at about 30 fps, even though the game asks for 60.
Lichii release
On RTX 50-series GPUs (5070 Ti, 5090), the GPU device can be lost shortly after a scene change.
Solución sugerida: Try NVIDIA driver 610.88.
Lichii release
Failed to allocate 14336 MiB of backing memory means Windows ran out of RAM plus page file.
Solución sugerida: Set the page file to system-managed and close memory-heavy apps.
Lichii release
Some textures are still black, and the game can crash later in play.
Lichii release
Some races still stall while shaders build.
Consulta de juegos
Selecciona manualmente el sistema operativo, la arquitectura, la categoría de GPU y la preferencia de DLSS.
Consulta los archivos publicados para el sistema operativo seleccionado arriba.
Consulta las notas de la versión utilizada en un informe de compatibilidad.
Dudas sobre la instalación
Conserva la versión que funciona hasta que hayas instalado y probado la nueva. Haz una copia de seguridad de tus partidas y tu configuración antes de cambiar de versión.
Conserva todos los archivos auxiliares de la misma versión en la misma carpeta que lichii.exe. Busca el mensaje exacto de la dependencia en las notas de la versión o en el gestor de incidencias.
Revisa el perfil de entrada y la asignación de botones. Después, busca el modelo de tu mando o el juego en la sección de solución de problemas.
«Cerrada» es el estado en el gestor de incidencias. Lee la conversación para saber si el problema se resolvió, se trasladó o la incidencia se cerró por otro motivo, y qué versión está afectada.
Indica la versión de Lichii, el sistema operativo, la GPU y su controlador, el texto completo del error y los pasos que lo provocan. Aclara si también ocurre en una versión que antes funcionaba.