Spielekompatibilität des Lichii Emulators

Related game issues

• [Regression][Linux RADV] Zelda Ocarina of Time black screen in build 95 (works in 93); native MME macro RAM errors (open)
• [GBug] Ocarina of Time: Multi-second single-pipeline GPU-thread re-translation stutters & 579k OnCPURead traps with Reactive Flushing (open)
• [VBug] Ocarina of Time (0400486024DEC000): Blinding white bloom/flare streak in Kakariko Village (NVIDIA) (open)
• [Crash] Ocarina of Time Remake crash after intro cinematic (open)
• [GBug] Textures not working properly, slow frame rate and shield glitch in The Legend of Zelda Ocarina of Time remake (open)
• [VBug] OoT (0400486024DEC000): textures flicker with Low GPU accuracy + EDEN_NX2_SPLIT=2 on AMD RX 9070 XT; High fixes it but turns the split off (~9 fps) (open)
• [VBug] [AMD RX 9070 XT] Ocarina of Time (0400486024DEC000): ~20 FPS, light/haze artifacts, audio desync (open)
• [GBug] Lichii Build 93 – Significant AMD Progress, but Lighting Flickering and Performance Issues Remain (open)
• [Crash] 100% reproducible crash inside Guardhouse in Hyrule Castle Town (OoT) (open)
• [GBug] Ocarina of Time: ~31 FPS in crowded scenes, front GPU thread stalls waiting for back thread (open)
• [AMD RX 9070 XT] Rainbow-colored graphical artifacts along mountain edges in Zelda OoT (Build 93) (open)
• [Crash] OoT (0400486024DEC000): 8 compute shaders rejected on RX 6750 GRE, unoptimized table only covers 2 (open)
• [Crash] Ocarina of Time: AMD RX 7900 XTX driver timeout / device lost at gameplay start, gone with #150 reverted (open)
• [GBug] Ocarina of Time (Switch 2): playable on RX 9070 XT with build 93, ~29 FPS in Kokiri Forest, one thread at 99% (open)
• [VBug] Ocarina of Time: stones flash pink, red, yellow or black (Bombchu Bowling Alley, Hyrule Castle), scene compose divides by zero blend weights (open)
• [VBug] Doesn't work for AMD GPU - 9070 XT (The Legend of Boy in Green Hat) (closed)
• [Build] Tree does not compile with clang-cl on Windows (NOMINMAX and FARPROC casts) (closed)
• [VBug] [nx2-build-75] Zelda: Ocarina of Time (0400486024DEC000) black screen — no AV1 decoder (closed)
• [VBug] Ocarina of Time: AV1 cutscenes render solid green on AMD/RADV (audio and subtitles OK) (closed)
• [GBug] Zelda OOTR Won't Load (closed)
• [Crash] chuppatricky-amd-testbuild v13: amdvlk64.dll access violation (0xc0000005) during shader compile on RX 6700 XT (open)
• [Crash] Crash replicated multiple times when trying to enter Hyrule Market - The Legend of Zelda: Ocarina of Time (open)
• [GBug] Ocarina of Time / Audio Desync (open)
• [Crash] chuppatricky-amd-testbuild v13: amdvlk64.dll access violation (0xc0000005) during shader compile on RX 6700 XT (closed)
• [Visual] Mesh-shader draws are dropped silently on GPUs without VK_EXT_mesh_shader (GTX 1070, Ocarina of Time) (open)
• [GBug] System language Portuguese (Brazil) doesn't change in-game language for the Remake of The Legend of Zelda: Ocarina of Time (closed)
• [GBug] Ocarina of Time (0400486024DEC000): black screen on Adreno 740/Turnip, pipeline builders stuck in driver until memory runs out (open)
• [GBug] Ocarina of Time (0400486024DEC000): gameplay settles at ~29 fps, CPU-bound on two cores (build 75) (open)
• [GBug] Ocarina of Time: black 3D gameplay screen; HUD remains visible (Lichii build 75) (closed)
• Ocarina of Time (Switch 2) gets stuck at "Building 9 shaders" on AMD RX 6750 XT (open)
• Ocarina of Time (0400486024DEC000) build-75: macro parameter desync + unknown texture format 100, broken lighting/bloom and corrupted textures (open)
• [GBug] (closed)
• Release note: 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.
• Release note: User reports describe multi-second GPU-thread shader translation stalls, gameplay stuttering, and growing synchronous OnCPURead waits during long sessions.
• Release note: Blinding white bloom/flare streak in Kakariko Village; a commenter reports it also occurs in the well, later areas, and frozen Zora's domain.
• Release note: User reports a crash after the intro cinematic when shader and pipeline compilation starts, with Vulkan device loss and NVIDIA driver errors.
• Release note: Commenters report similar crashes and audio desynchronization during the intro cutscene.
• Release note: User reports textures not working properly, slow frame rate, and a shield glitch.
• Release note: Textures and surfaces flicker with Low GPU accuracy and EDEN_NX2_SPLIT=2 on Radeon RX 9070 XT; some surfaces remain white temporarily.
• Release note: Outdoor haze is very strong, and the river surface can appear dark or black.
• Release note: 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.
• Release note: 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.
• Release note: Severe lighting flickering, excessively bright or visually corrupted lighting effects, performance slowdowns, audio desynchronization during cinematics, and lengthy initial shader compilation.
• Release note: Eglantine crashes at the end of the intro with VK_ERROR_DEVICE_LOST on an Apple Silicon Mac, according to a user comment.
• Release note: The emulator crashes shortly after entering the Guardhouse (Pot Room) in Hyrule Castle Town.
• Release note: 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.
• Release note: Severe rainbow-colored graphical artifacts along mountain edges in Kakariko Village on an AMD Radeon RX 9070 XT.
• Release note: 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.
• Release note: 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.
• Release note: 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.
• Release note: 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.
• Release note: 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.
• Release note: 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.
• Release note: With use_disk_shader_cache = true, subsequent boots hang indefinitely at Loading Shaders 25 / 27.
• Release note: Black screen after the intro on AMD RX 9070 XT; the game's 1080p upscaler shader is rejected.
• Release note: 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.
• Release note: Texture flicker with Low GPU accuracy and GPU thread split on AMD RX 9070 XT.
• Release note: Handheld mode is reported as much brighter and blurrier than Docked mode.
• Release note: 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.
• Release note: 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.
• Release note: On Linux with AMD/RADV, AV1 intro cutscene video renders solid green while audio and subtitles work.
• Release note: On Windows 10 with AMD, the intro AV1 cutscene shows a black video layer with working audio and subtitles, then the emulator hangs indefinitely.
• Release note: 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.
• Release note: A user reports severe shader problems with white visuals; handheld mode shows a black screen.
• Release note: A user reports a black screen past the title screen.
• Release note: 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.
• Release note: The emulator closes when loading Hyrule Market after the user exits Kokiri Forest and enters Hyrule Castle.
• Release note: 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.
• Release note: 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.
• Release note: 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.
• Release note: 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.
• Release note: 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.
• Release note: 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.
• Release note: The 3D gameplay scene can appear black while the HUD remains visible.
• Release note: A commenter reported stuttering, FPS drops, and overexposure after switching to Docked mode.
• Release note: A commenter reported flickering shadows and trees with no leaves.
• Release note: A commenter reported audio playing ahead of the video during the intro.
• Release note: 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.
• Release note: 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.
• Release note: The 3D gameplay scene is black while HUD elements remain visible; menus and item preview can render correctly.

Compared with Previous Build

Related game issues

• [VBug] black screen amd (open)
• [GBug] Zelda: Ocarina of Time (0400486024DEC000): the audio plays a different part of the stream than the picture (open)
• [Crash] black screen when starting Zelda: Ocarina of Time on the latest build - Intel(R) HD Graphics 620 with vulkan and OpenGL GLS (open)
• [VBug] OoT (0400486024DEC000): world renders black except areas lit by Navi and around Link, AMD RX 9070 (closed)
• [VBug] [nx2-build-75] Zelda: Ocarina of Time (0400486024DEC000) black screen — no AV1 decoder (closed)
• [GBug] Ocarina of Time on RADV (RX 9070 XT): 28-35 fps, 35 ms frame with no saturated thread (translation/sync bound) (open)
• [VBug] Build 93 finaly has no major visual errors but has poor performance 9070xt (open)
• [Crash] Crash replicated multiple times when trying to enter Hyrule Market - The Legend of Zelda: Ocarina of Time (open)
• [Crash] (open)
• [Perf] OoT (0400486024DEC000): per-fence Preflushable buffer downloads (~430 MB/s) are the biggest GPU back-thread cost; batching them gives +55% draws/s but breaks exposure (open)
• [GBug] Ocarina of Time (0400486024DEC000): intro freezes for 6 to 18 minutes on AMD while the driver optimizes two compute shaders (open)
• [Crash] AMD Ocarina of time Doesn't Start (open)
• Ocarina of Time harvest fork: findings and open tasks (open)
• [GBug] OoT (0400486024DEC000): the same ~60 cached graphics pipelines are rebuilt on the GPU thread every boot (closed)
• macOS/MoltenVK: Ocarina of Time (0400486024DEC000) kills or hangs the Metal device at the intro-video boundary (open)
• [GBug] System language Portuguese (Brazil) doesn't change in-game language for the Remake of The Legend of Zelda: Ocarina of Time (closed)
• [VBug] Oot is in a "nightmare mode"? also gameplay speed is at like 30% (open)
• [VBug] OoT Slows when booting. (closed)
• [Crash] Ocarina of Time (0400486024DEC000): freezes in Hyrule Castle Town pot room near the guard (open)
• [Crash] Linux/RADV (RX 9070 XT): invalid SPIR-V fragment shader (depth image u32 sampled as f32) segfaults in VkPipelineBuild, Ocarina of Time (open)
• [Crash] AMD Crash/AudioDesync (open)
• [Crash] Ocarina of time crash on Linux AMD (open)
• [AMD RX 9070 XT] Black screen with UI visible and GPU driver timeout (Build 88) (open)
• [Bug] Windows build-83 can hang on Closing software after OoT gameplay (open)
• Release note: 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.
• Release note: Black screen or no video output while audio works or appears to work.
• Release note: Audio issues and occasional crash when launching another game without restarting after the game loads using Docked Mode and Accurate GPU.
• Release note: Clean audio from a different point of the game plays while the intro image is displayed; audio and picture are substantially out of sync.
• Release note: 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.
• Release note: PGO artifact crashes in dynarmic with Unhandled SIGSEGV after 2–10 minutes on the reported machine.
• Release note: Conflicting reports of low and high frame rates on an RX 9070 XT, with one comment suggesting Windows performance may be worse than Linux.
• Release note: 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.
• Release note: In the measurement-only experiment, disabling per-fence Preflushable downloads or batching downloads by 64 fences caused overexposure in Kokiri Forest.
• Release note: 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.
• Release note: 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.
• Release note: 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.
• Release note: 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.
• Release note: Commenters report rendering failures, black screens, and AMD driver crashes; one reports that audio continues while rendering is crashed.
• Release note: 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.
• Release note: Persistent graphics pipeline cache entries are reportedly rebuilt on the GPU thread during gameplay on repeated boots, causing a visible hitch.
• Release note: 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.
• Release note: 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.
• Release note: With GPU Mode: Accurate (High), gameplay may run in slow motion at about 30 FPS; shader compilation can cause stutter on new content.
• Release note: Slows when booting.
• Release note: User-reported reproducible freeze when walking deeper into the pot room in Hyrule Castle Town, near the guard.
• Release note: 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.
• Release note: 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.
• Release note: 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.
• Release note: On some AMD GPUs, the UI may remain visible while the 3D world is black; reports also describe AMD driver timeouts or crashes.
• Release note: On Windows build-83, shutdown can hang at “Closing software…” after gameplay. Some sessions completed shutdown successfully; the cause is undetermined.

Compared with Previous Build

Current: build-83 (1 record); previous: build-75 (0 records).