Installation et dépannage
Du téléchargement au premier lancement, configurez vos commandes, ajoutez vos jeux et résolvez les problèmes qui vous bloquent.
Trois plateformes
Choisissez votre plateforme pour suivre l’installation pas à pas.
Besoin d’un autre fichier ? Voir les téléchargements pour windows.
Besoin d’un autre fichier ? Voir les téléchargements pour linux.
Besoin d’un autre fichier ? Voir les téléchargements pour macos.
Premier lancement
Configurez Lichii dès le premier lancement : choisissez la disposition de manette qui vous convient, réglez les graphismes et ajoutez votre bibliothèque de jeux.
Commencez par les réglages graphiques décrits dans les notes de votre version. Changez un seul réglage à la fois et notez le tag de la version avec vos résultats.
Pour trouver des réglages de départ adaptés à un jeu, ouvrez son rapport de compatibilité.
Connectez votre manette, attribuez les boutons, puis enregistrez le profil. Si un bouton ne fonctionne pas, recherchez le modèle de votre manette et votre version de Lichii dans la section de dépannage.
Ajoutez vos jeux obtenus légalement depuis la bibliothèque ou l’option d’ouverture de fichiers de jeu de Lichii. Les jeux, les clés et le micrologiciel sont à fournir séparément.
Reprendre la partie
276 problèmes dans la liste
Aucun problème ne correspond à cette recherche. Consultez les notes de version ou essayez le texte exact de l’erreur.
GitHub issue · open
The sky in Hyrule glows white when the save file is loaded.
GitHub issue · open
Black screen or no video output while audio works or appears to work.
Solution proposée : A commenter reports that launching in Docked Mode with Accurate GPU loads the main menu; this is a user-reported workaround, not a confirmed fix.
GitHub issue · open
Audio issues and occasional crash when launching another game without restarting after the game loads using Docked Mode and Accurate GPU.
GitHub issue · open
The Skateboarding sport's Sightseeing Tour requires a Joy-Con 2 controller, but the Controller Applet has no Joy-Con 2 option, making it impossible to play.
GitHub issue · open
GitHub issue · open
On build 95 on Linux with AMD RADV, the game stalls on a black screen at 0 FPS, with repeated native MME macro execution failures.
GitHub issue · open
GitHub issue · open
The game reportedly runs at 10 FPS on the menu and shows a black screen after the cutscene on Intel Arc.
GitHub issue · open
GitHub issue · closed
Flashing textures when running with GPU Mode: Fast on Linux; the report says the issue does not occur with GPU Mode: Accurate.
GitHub issue · closed
A commenter reports white flickering throughout the 3D world in the Frizti fork.
GitHub issue · open
On build 94 with GPU thread split enabled, split-front macros repeatedly fail with “instruction outside uploaded RAM,” leading to a black screen or stopped rendering.
Solution proposée : Set EDEN_NX2_SPLIT=1 to keep macros on the back thread; both issue reporters say this avoids the macro errors, and the second reports that the game renders.
GitHub issue · open
Translucent shaders flicker on water and garden windows.
GitHub issue · open
**Build:** 222877d (build 95), also present on current main **GPU:** Nvidia, Vulkan ### Symptom 3D scene renders completely black. UI, subtitles and audio are fine; the pause menu background shows the scene. Every frame the log reports: ``` Native QMD failed: native shader dispatch required (native_qmd.h:96) ``` `DispatchNativeCompute` returns false for a full-screen post-process compute (QMD grid 120x68x1), so …
GitHub issue · open
GPU channels can wait indefinitely on a semaphore, leaving the emulator hung or Not Responding. The issue body attributes one hang to a data race that drops a `SET_REPORT_SEMAPHORE` release. A user separately reported an intermittent freeze after about 100 minutes on build 93; a second 98-minute run did not reproduce it.
Solution proposée : The issue body gives a tested code change: replace the DMA pusher bitfields with separate boolean members, make `synced` an atomic boolean, and load it in the condition-variable predicate.
GitHub issue · open
Town vegetation and small clutter render at a distance but disappear when approached; a later report says flowers no longer disappear in builds 94/95, while tree leaves still do.
GitHub issue · open
GitHub issue · open
GitHub issue · open
Users report low FPS and frequent stuttering on their hardware; one user reports about 15 FPS.
GitHub issue · closed
GitHub issue · open
User reports describe multi-second GPU-thread shader translation stalls, gameplay stuttering, and growing synchronous OnCPURead waits during long sessions.
GitHub issue · open
A user reports an instant GPU crash after the starting cutscene ends, with audio out of sync, on CachyOS with AMD graphics. The log records a Vulkan device loss.
GitHub issue · open
Blinding white bloom/flare streak in Kakariko Village; a commenter reports it also occurs in the well, later areas, and frozen Zora's domain.
GitHub issue · open
Performance varies by boot on the same build, save, and scene. Heavy boots run 20–25% slower in gameplay, and job workers stay awake about 45% longer.
GitHub issue · open
Plants around the Castle render as dead; a commenter reports bushes render correctly at a distance.
GitHub issue · closed
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
User reports a crash after the intro cinematic when shader and pipeline compilation starts, with Vulkan device loss and NVIDIA driver errors.
GitHub issue · open
Commenters report similar crashes and audio desynchronization during the intro cutscene.
GitHub issue · open
User reports that Fire Emblem: Fortune's Weave crashes on Linux with VK_ERROR_DEVICE_LOST and a GPU reset on AMD Radeon GPUs.
GitHub issue · open
The game freezes when pressing any button in the ocarina menu.
Solution proposée : In Options, set "Ocarina Mic Input" to "None". A commenter reports this fixed the issue.
GitHub issue · open
User reports disappearing room textures inside the Water Temple, making walls and stairs difficult to see.
GitHub issue · open
User reports textures not working properly, slow frame rate, and a shield glitch.
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
GitHub issue · open
A user reports bright light/haze-like artifacts, roughly 20 FPS with large variance, and desynced, stuttering audio during gameplay on an AMD RX 9070 XT.
GitHub issue · closed
On nx2 / build 93, normal launches without EDEN_NX2_TC_LOG can keep texture debug bookkeeping enabled for the entire session, causing unnecessary per-image map operations and retaining distinct shape keys.
GitHub issue · open
Crash reported after joining the game with OpenGL.
GitHub issue · closed
Crashes immediately after the first cutscene.
GitHub issue · open
The Fairy Fountain before meeting Saria in the Lost Woods does not render.
GitHub issue · open
Severe lighting flickering, excessively bright or visually corrupted lighting effects, performance slowdowns, audio desynchronization during cinematics, and lengthy initial shader compilation.
GitHub issue · open
Build 93 crashes the GPU on an AMD 7800xt, according to a user comment.
GitHub issue · open
Eglantine crashes at the end of the intro with VK_ERROR_DEVICE_LOST on an Apple Silicon Mac, according to a user comment.
GitHub issue · open
A user reports that loading "oot remake" in build 93 stops and closes the emulator; they say build 88 worked.
GitHub issue · open
Rainbow-colored artifacts on mountain edges above the castle, excessive bloom in Hyrule Field, and intermittent severe FPS drops during gameplay.
GitHub issue · open
The emulator crashes shortly after entering the Guardhouse (Pot Room) in Hyrule Castle Town.
GitHub issue · open
Cannot go further than the DekuTree cutscene; a commenter reports a black screen after getting past the title screen with OpenGL.
GitHub issue · open
In crowded scenes, the front GPU thread spends substantial time draining the back thread while the back thread waits, resulting in serialized work, about 31 FPS on average (down to about 19 FPS), and short freezes while attacking.
GitHub issue · open
Severe rainbow-colored graphical artifacts along mountain edges in Kakariko Village on an AMD Radeon RX 9070 XT.
GitHub issue · open
User reports intermittent audio loss, brief frame-rate drops, an excessively bright missing sky, and a missing map.
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
On the Vulkan backend with an AMD RX 6750 GRE, eight compute shaders are reported rejected with VK_ERROR_OUT_OF_HOST_MEMORY; the AV1 intro video is not presented and the process later aborts with 0xc0000409.
GitHub issue · open
The screen has visual noise ("nieve") and lag when entering the game.
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
On build-93, reported low FPS causes gameplay to run in slow motion; users also report heavy bloom and overexposure in bright areas and a dark-silhouette rendering of the Great Deku Tree in its intro scene.
GitHub issue · open
On the Lichii-AMD 2026.11.07 (nauxph fork, f4e938f516), GPU Mode Fast reportedly causes recurring blackouts of the game world while the HUD remains visible; the game continues running.
Solution proposée : Switching GPU Mode from Fast to Accurate at runtime restores the picture without restarting; the user reports Accurate avoids blackouts but causes heavy stutter.
GitHub issue · open
A user reports that gpu_accuracy, scaling_filter, and anti_aliasing values edited in qt-config.ini are rewritten at startup and says these settings must be changed through the GUI.
GitHub issue · open
Shaders load slowly and significantly slow gameplay, rebuilding when entering the same area. In the Kokiri Sword area, Link and most surroundings turn solid black; white flickers also occur.
GitHub issue · open
GitHub issue · open
GitHub issue · open
GitHub issue · open
User reports a crash at the first cutscene and emulator shutdown after compiling existing shaders on reboot.
GitHub issue · open
On AMD Radeon RX 6800 XT, opening the game leaves the screen black with no video output and unresponsive controls; music eventually stops.
GitHub issue · open
Many water temple rooms are not visible; walls are completely transparent.
GitHub issue · open
Much of Gerudo does not render correctly, appearing like the skybox; resetting shaders reportedly changes it to physical forms and shapes with skybox textures.
GitHub issue · open
User reports missing geometry, walls, buildings, and caves in the Great Deku Tree on a GTX 1070 Ti; the issue worsens deeper into the area.
GitHub issue · open
User reported sky-coloured holes in distant mountains of Hyrule Field on nx2 a7a28175 (same content as build-93) + local patches; a later user comment says they could no longer reproduce them on a newer local build.
GitHub issue · open
Stones intermittently flash bright pink, red, yellow, cyan, or black in the Bombchu Bowling Alley in Castle Town Market and near Hyrule Castle. The user’s investigation found zero weight inputs to the final scene-compose dispatch, producing invalid output.
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
The sky is extremely bright, obscuring visibility in open areas such as Hyrule Field.
GitHub issue · open
User reports excessive bloom outside the Great Deku Tree and invisible boxes and walls inside it.
GitHub issue · open
GitHub issue · open
Walls are invisible in underground areas with red health fairies.
GitHub issue · open
GitHub issue · closed
On Radeon RX 580, hangs at a black screen at 0 FPS while building compute pipelines as the intro video starts.
GitHub issue · closed
With use_disk_shader_cache = true, subsequent boots hang indefinitely at Loading Shaders 25 / 27.
Solution proposée : Delete cache/shader/0400486024dec000 and set use_disk_shader_cache = false; the reporter says this resolves the startup freeze.
GitHub issue · closed
Black screen after the intro on AMD RX 9070 XT; the game's 1080p upscaler shader is rejected.
Solution proposée : 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 · closed
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.
Solution proposée : 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 · closed
Texture flicker with Low GPU accuracy and GPU thread split on AMD RX 9070 XT.
GitHub issue · closed
Handheld mode is reported as much brighter and blurrier than Docked mode.
GitHub issue · closed
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 · closed
clang-cl configure/compile failures are reported from min/max macros exposed by windows.h and direct FARPROC-to-function-pointer casts.
Solution proposée : 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
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 · closed
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.
Solution proposée : 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 · closed
Very low FPS and graphics problems, including missing textures, lighting or ambient occlusion issues, and a blown-out white image.
GitHub issue · closed
The emulator closes about a minute after gameplay begins on Windows 11 with an NVIDIA RTX 50 series GPU.
GitHub issue · closed
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 · closed
On Linux with AMD/RADV, AV1 intro cutscene video renders solid green while audio and subtitles work.
GitHub issue · closed
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 · closed
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 · closed
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 · closed
A user reports severe shader problems with white visuals; handheld mode shows a black screen.
GitHub issue · closed
A user reports a black screen past the title screen.
GitHub issue · closed
FMVs and pre-rendered videos are skipped, including the opening cut-scene.
GitHub issue · closed
GitHub issue · closed
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 · closed
GitHub issue · closed
GitHub issue · closed
GitHub issue · open
Grass, vegetation, and pebbles may disappear during sword attacks; one user reports grass vanished permanently after clearing the shader cache.
Solution proposée : A user reports that disabling "use persistent pipeline cache" fixed the issue for them.
GitHub issue · open
User reports the game crashes when the loading screen appears on Windows 10 with an AMD RX 6000 series or older graphics card.
GitHub issue · open
PGO artifact crashes in dynarmic with Unhandled SIGSEGV after 2–10 minutes on the reported machine.
GitHub issue · open
Deku has black textures on some parts during the cinematic, with stuttering, bloom and artifacts when jumping. Dynamic FPS makes the game run too fast (about 2x speed); without it, gameplay is almost in slow motion.
GitHub issue · open
User reports the emulator hangs and crashes at 11/14 shaders loaded on Linux with AMD graphics when booting the game in Build-88 or Build-93.
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
In the shield tutorial, holding ZL is not detected and the tutorial loops. The user reports the same issue after rebinding ZL to L or switching to keyboard.
GitHub issue · open
Black screen and GPU deadlock after an unsupported native QMD compute dispatch; GPU channels wait on the semaphore the QMD was supposed to release.
GitHub issue · open
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
White haze over Hyrule Field and the sky on AMD cards, attributed by a commenter to froxel fog reading light probes beyond a 64 MiB read-only storage binding.
Solution proposée : A commenter says the issue was fixed in #351.
GitHub issue · open
GitHub issue · closed
A user reports black visuals except for the UI after starting a new game, while audio is audible.
GitHub issue · closed
A commenter reports that the PGO build produces a black screen in both docked and handheld modes.
GitHub issue · open
On Windows 11 with an AMD Radeon RX 6700 XT and AMD Software (Adrenalin) 26.10.2, Lichii closes during shader rebuilding with an access violation in amdvlk64.dll.
GitHub issue · open
In build 93, the user reports controller input is hijacked about every 30 seconds, causing the character to run into a wall. The user says this did not happen in build 92.
GitHub issue · open
Poor frame rates; the issue says performance is worse than on most other forks.
GitHub issue · open
Conflicting reports of low and high frame rates on an RX 9070 XT, with one comment suggesting Windows performance may be worse than Linux.
GitHub issue · open
The issue says FPS is worse than on most other forks.
GitHub issue · open
GitHub issue · open
A black screen with title music and unresponsive controls; after waiting for shaders to load, the game worked but was extremely glitchy and laggy.
Solution proposée : Waiting for shaders to load resolved the reported black screen, according to the user; gameplay remained unplayable.
GitHub issue · open
The emulator closes when loading Hyrule Market after the user exits Kokiri Forest and enters Hyrule Castle.
GitHub issue · open
The console restarts after the scene on Linux with a lenovo legion go 2 z2 and egpu 7600xt; the report names versions 83 et 93.
GitHub issue · open
GitHub issue · closed
GitHub issue · open
On AMD RX 9070XT under SteamOS/Linux, the game reportedly froze before the title screen, then showed pixel artefacts and caused a system crash.
GitHub issue · open
The source refers to the game as OOT but does not clearly identify which listed Ocarina of Time game it is. On AMD RX 9070XT under SteamOS/Linux, loading a save reportedly led to a black screen and system crash. After trying EDEN_NX2_NO_MESH=1, rendering and shading issues remained.
GitHub issue · open
GitHub issue · open
Walls and objects are missing/not rendered inside the Deku tree.
GitHub issue · open
Overexposure in specific areas, including the lower part of Saria's house and the right side of the entrance to hyrule castle.
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
On build 93, FPS fluctuates approximately between 20 and 60, with frequent periods around 30 and drops to 25–28 FPS in the Dragon Layer; GameSir G7 Pro rumble can be excessive, occur without an obvious trigger, or continue longer than expected.
GitHub issue · closed
On an AMD Radeon RX 6700 XT with AMD Software (Adrenalin) 26.10.2, Lichii closes during the first shader rebuild after about 9-10 minutes; Event Viewer reports an access violation in amdvlk64.dll.
GitHub issue · open
Constant 4 FPS in-game on AMD Radeon RX 570 4GB.
GitHub issue · open
A user reports a freeze about 40 seconds after boot, with texture rendering failure and overbright world brightness beforehand. A dump showed GPUBack waiting on the guest page table lock while in the texture garbage collector; the user suspects a lock cycle.
GitHub issue · open
The mountain on the way up to Zora's Domain following the river is invisible.
GitHub issue · open
On a GPU without VK_EXT_mesh_shader, the user reports missing scene geometry during gameplay; mesh/task draws may be skipped and logged only as "Draw skipped (no pipeline)". The cause of the reported missing geometry was not confirmed on screen.
GitHub issue · open
User reports a crash when loading a save on AMD RX 6000 series or older under Windows 11.
GitHub issue · open
GitHub issue · open
Rhythmic wavy effect on edges in the main area, described as depth of field toggling on and off.
GitHub issue · open
A user reports sound glitches and improper rendering after booting Mario tennis.
GitHub issue · open
GitHub issue · open
Game remains at 20 fps with music glitches on macOS; the issue has continued since build 75, with a small regression in build 83/88.
GitHub issue · open
User reports a GPU and emulator crash within seconds of starting Green Hat Kid on Linux with an AMD RX 9000 series graphics card, producing VK_ERROR_DEVICE_LOST.
Solution proposée : User reports that running with EDEN_NX2_NO_MESH=1 avoids the crash.
GitHub issue · open
GitHub issue · open
Crashes at the same moment as it flies under the user's feet; the log reports an application error in amdvlk64.dll.
GitHub issue · open
User reports freezing while loading a game and a subsequent emulator crash on macOS; in Build 93, pressing A on a controller reportedly does nothing when attempting to return to the title screen.
GitHub issue · open
GitHub issue · open
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 · closed
GitHub issue · open
User reports the game is locked at 20 FPS, including menus and title screen, on Windows 11.
GitHub issue · open
The game reaches responsive gameplay with a correctly rendered HUD, but the 3D scene is black. Graphics programs are rejected and draws are skipped.
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.
Solution proposée : 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
User reports an unhandled Vulkan::vk::Exception and emulator crash shortly after the first cutscene when texture allocation fails with VK_ERROR_OUT_OF_DEVICE_MEMORY on an AMD Radeon RX 9060 XT 8 GB.
GitHub issue · open
Game freezes when the user tries the Ocarina at the Temple of Time.
GitHub issue · open
GitHub issue · open
User reports a crash when booting the game in build 88 after it worked in build 75.
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
On AMD RX 7000 series, NaNs from FMin, FMax, and FClamp can spread through bloom, producing a yellow-white sky and green shimmering water.
GitHub issue · open
GitHub issue · open
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
GitHub issue · closed
Persistent graphics pipeline cache entries are reportedly rebuilt on the GPU thread during gameplay on repeated boots, causing a visible hitch.
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
GitHub issue · open
GitHub issue · open
GitHub issue · open
GitHub issue · open
GitHub issue · closed
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.
Solution proposée : Set GPU Mode to Fast; the commenter reports this resolved the slow gameplay for their setup.
GitHub issue · open
GitHub issue · open
GitHub issue · closed
GitHub issue · closed
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
GitHub issue · closed
GitHub issue · closed
GitHub issue · closed
Slows when booting.
GitHub issue · closed
GitHub issue · closed
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 · closed
User reports the game crashes after about 15 to 20 minutes.
GitHub issue · closed
GitHub issue · closed
The emulator force quits after being stuck on the "Loading Shaders" screen for about 2 seconds.
GitHub issue · closed
GitHub issue · closed
After the intro, the scene where the deku tree is talking is completely black with very slow, stuttery dialogue.
GitHub issue · closed
After the startup screen, audio plays but the screen is black.
GitHub issue · closed
Music disappears during the cutscene after booting the game.
GitHub issue · closed
The game crashes while building shaders after the title card fades.
GitHub issue · closed
An error appears after the cinematic and remains on screen, blocking the view.
GitHub issue · closed
Black screen during cinematic after the main menu appears; reported on Windows 11 with an AMD RX 6000 series or older GPU.
GitHub issue · closed
Infinite startup launch loop when booting the .NUP version.
GitHub issue · closed
A user reports repeated Unmapped Write64 errors, possible audio popping, and an emulation crash when closing the game.
GitHub issue · closed
Terrain is visible through solid objects after getting past the intro.
GitHub issue · closed
Users report crashes before the training mission begins and during the campaign.
GitHub issue · closed
Weird artifacts, especially on shadows.
GitHub issue · closed
User reports a black screen while loading in Build 65.
GitHub issue · closed
A black rectangle appears in a mini-example guide; the reporter says it persists on build-70.
GitHub issue · closed
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 · closed
GitHub issue · closed
GitHub issue · closed
GitHub issue · closed
GitHub issue · closed
GitHub issue · open
GitHub issue · open
GitHub issue · open
GitHub issue · open
GitHub issue · open
GitHub issue · open
User-reported reproducible freeze when walking deeper into the pot room in Hyrule Castle Town, near the guard.
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
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
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
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.
Solution proposée : Deleting the shader cache allows booting again, according to the user report.
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
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 · open
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 · closed
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
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
OCARINA OF TIME ### Before submitting - [x] I searched existing issues and found no duplicate - [x] I'm using the latest build - [x] My game is legally dumped from my own console ### Emulator build BUILD-88 ### Regression - [ ] This is a regression (it worked in an older build) ### Last known working build _No response_ ### Game Other / not listed ### Graphics card NVIDIA RTX 30 series or older ### Opera…
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 · closed
The 3D gameplay scene can appear black while the HUD remains visible.
Solution proposée : 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
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.
Solution proposée : 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
Only character outlines and UI are visible after launching the game.
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 Windows build-83, shutdown can hang at “Closing software…” after gameplay. Some sessions completed shutdown successfully; the cause is undetermined.
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
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
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
Black screen after the first cutscene in handheld mode and VHS-like visual filter in docked mode.
GitHub issue · closed
Boots to a black screen with audio on macOS.
Solution proposée : Clear the cache and launch again.
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 · 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 · closed
The 3D gameplay scene is black while HUD elements remain visible; menus and item preview can render correctly.
GitHub issue · closed
GitHub issue · closed
GitHub issue · closed
Lichii release
AMD black foliage and haze.
Lichii release
HUD flicker.
Lichii release
Cutscene audio drift.
Lichii release
First-launch shader stall on Linux.
Lichii release
An NVIDIA device-lost crash was reported on build 93; the release says it is awaiting retest on this build.
Lichii release
AMD black textures, haze, HUD flicker, and cutscene audio remain open investigations; the release does not claim these symptoms are fixed.
Lichii release
Initial Linux shader-loading stall remains an open investigation; the worker-cancellation fix does not address it.
Lichii release
The combined AMD shader and Vulkan synchronization fixes have not been verified in affected AMD gameplay.
Lichii release
Native draw discard can skip writes to persistent resources and leave missing effects when enabled.
Lichii release
An existing fence-worker shutdown race can leave the emulator waiting during shutdown.
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.
Solution proposée : Try NVIDIA driver 610.88.
Lichii release
“Failed to allocate 14336 MiB of backing memory” means Windows ran out of RAM plus page file.
Solution proposée : 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.
Solution proposée : Try NVIDIA driver 610.88.
Lichii release
Failed to allocate 14336 MiB of backing memory means Windows ran out of RAM plus page file.
Solution proposée : 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.
Vérification des jeux
Sélectionnez manuellement le système d’exploitation, l’architecture, la catégorie de GPU et l’option DLSS.
Consultez les fichiers publiés pour le système d’exploitation sélectionné ci-dessus.
Consultez les notes de la version utilisée dans un rapport de compatibilité.
Questions sur l’installation
Gardez la version qui fonctionne jusqu’à ce que la nouvelle soit installée et testée. Sauvegardez vos parties et votre configuration avant de changer de version.
Conservez tous les fichiers associés de la même version dans le même dossier que lichii.exe. Recherchez le message exact de dépendance dans les notes de version ou le suivi des tickets.
Vérifiez le profil de la manette et l’affectation des boutons, puis recherchez le modèle ou le jeu dans la section de dépannage.
« Fermé » est le statut dans le suivi des tickets. Lisez la discussion pour savoir si le problème a été résolu, déplacé ou si le ticket a été fermé pour une autre raison, et quelle version est concernée.
Indiquez la version de Lichii, le système d’exploitation, le GPU et son pilote, le texte complet de l’erreur et les étapes qui la déclenchent. Précisez si elle survient aussi dans une version qui fonctionnait auparavant.