Lichii Emulator のゲーム互換性

Related game issues

• [GBug] Ocarina of Time (0400486024DEC000): gameplay settles at ~29 fps, CPU-bound on two cores (build 75) (open)
• Ocarina of Time (Switch 2) gets stuck at "Building 9 shaders" on AMD RX 6750 XT (open)
• [Crash] Ocarina of Time: AMD RX 7900 XTX driver timeout / device lost at gameplay start, gone with #150 reverted (open)
• Ocarina of Time (0400486024DEC000) build-75: macro parameter desync + unknown texture format 100, broken lighting/bloom and corrupted textures (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)
• [GBug] Ocarina of Time: black 3D gameplay screen; HUD remains visible (Lichii build 75) (closed)
• [VBug] Doesn't work for AMD GPU - 9070 XT (The Legend of Boy in Green Hat) (open)
• [VBug] Ocarina of Time: AV1 cutscenes render solid green on AMD/RADV (audio and subtitles OK) (open)
• [Build] Tree does not compile with clang-cl on Windows (NOMINMAX and FARPROC casts) (open)
• [GBug] Ocarina of Time / Audio Desync (open)
• [VBug] [nx2-build-75] Zelda: Ocarina of Time (0400486024DEC000) black screen — no AV1 decoder (open)
• [GBug] Ocarina of Time (0400486024DEC000): black screen on Adreno 740/Turnip, pipeline builders stuck in driver until memory runs out (open)
• [GBug] Zelda OOTR Won't Load (open)
• [GBug] (closed)
• 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: 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: 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-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: 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: 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: 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: 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: 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 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: 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 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: 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: 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

• [GBug] Ocarina of Time (0400486024DEC000): gameplay settles at ~29 fps, CPU-bound on two cores (build 75) (open)
• Ocarina of Time (Switch 2) gets stuck at "Building 9 shaders" on AMD RX 6750 XT (open)
• [Crash] Ocarina of Time: AMD RX 7900 XTX driver timeout / device lost at gameplay start, gone with #150 reverted (open)
• Ocarina of Time (0400486024DEC000) build-75: macro parameter desync + unknown texture format 100, broken lighting/bloom and corrupted textures (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)
• [GBug] Ocarina of Time: black 3D gameplay screen; HUD remains visible (Lichii build 75) (closed)
• [VBug] Doesn't work for AMD GPU - 9070 XT (The Legend of Boy in Green Hat) (open)
• [VBug] Ocarina of Time: AV1 cutscenes render solid green on AMD/RADV (audio and subtitles OK) (open)
• [Build] Tree does not compile with clang-cl on Windows (NOMINMAX and FARPROC casts) (open)
• [GBug] Ocarina of Time / Audio Desync (open)
• [VBug] [nx2-build-75] Zelda: Ocarina of Time (0400486024DEC000) black screen — no AV1 decoder (open)
• [GBug] Ocarina of Time (0400486024DEC000): black screen on Adreno 740/Turnip, pipeline builders stuck in driver until memory runs out (open)
• [GBug] Zelda OOTR Won't Load (open)
• [GBug] (closed)
• 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: 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: 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-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: 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: 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: 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: 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: 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 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: 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 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: 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: The 3D gameplay scene is black while HUD elements remain visible; menus and item preview can render correctly.

Compared with Previous Build

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

Related game issues

• macOS/MoltenVK: Ocarina of Time (0400486024DEC000) kills or hangs the Metal device at the intro-video boundary (open)
• [Crash] (open)
• [Crash] AMD Crash/AudioDesync (open)
• [AMD RX 9070 XT] Black screen with UI visible and GPU driver timeout (Build 88) (open)
• [Crash] Ocarina of Time (0400486024DEC000): freezes in Hyrule Castle Town pot room near the guard (open)
• [Crash] AMD Ocarina of time Doesn't Start (open)
• [GBug] Ocarina of Time (0400486024DEC000): intro freezes for 6 to 18 minutes on AMD while the driver optimizes two compute shaders (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)
• [VBug] OoT Slows when booting. (open)
• Ocarina of Time harvest fork: findings and open tasks (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)
• [Bug] Windows build-83 can hang on Closing software after OoT gameplay (open)
• [GBug] OoT (0400486024DEC000): the same ~60 cached graphics pipelines are rebuilt on the GPU thread every boot (open)
• [VBug] Oot is in a "nightmare mode"? also gameplay speed is at like 30% (open)
• [GBug] Ocarina of Time on RADV (RX 9070 XT): 28-35 fps, 35 ms frame with no saturated thread (translation/sync bound) (open)
• [GBug] Zelda: Ocarina of Time (0400486024DEC000): the audio plays a different part of the stream than the picture (open)
• [VBug] [nx2-build-75] Zelda: Ocarina of Time (0400486024DEC000) black screen — no AV1 decoder (open)
• [VBug] OoT (0400486024DEC000): world renders black except areas lit by Navi and around Link, AMD RX 9070 (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: 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: 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: 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: 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: User-reported reproducible freeze when walking deeper into the pot room in Hyrule Castle Town, near the guard.
• 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: 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: 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: Slows when booting.
• 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: 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: On Windows build-83, shutdown can hang at “Closing software…” after gameplay. Some sessions completed shutdown successfully; the cause is undetermined.
• 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: 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: PGO artifact crashes in dynarmic with Unhandled SIGSEGV after 2–10 minutes on the reported machine.
• 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.

Compared with Previous Build

Related game issues

• macOS/MoltenVK: Ocarina of Time (0400486024DEC000) kills or hangs the Metal device at the intro-video boundary (open)
• [Crash] (open)
• [Crash] AMD Crash/AudioDesync (open)
• [AMD RX 9070 XT] Black screen with UI visible and GPU driver timeout (Build 88) (open)
• [Crash] Ocarina of Time (0400486024DEC000): freezes in Hyrule Castle Town pot room near the guard (open)
• [Crash] AMD Ocarina of time Doesn't Start (open)
• [GBug] Ocarina of Time (0400486024DEC000): intro freezes for 6 to 18 minutes on AMD while the driver optimizes two compute shaders (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)
• [VBug] OoT Slows when booting. (open)
• Ocarina of Time harvest fork: findings and open tasks (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)
• [Bug] Windows build-83 can hang on Closing software after OoT gameplay (open)
• [GBug] OoT (0400486024DEC000): the same ~60 cached graphics pipelines are rebuilt on the GPU thread every boot (open)
• [VBug] Oot is in a "nightmare mode"? also gameplay speed is at like 30% (open)
• [GBug] Ocarina of Time on RADV (RX 9070 XT): 28-35 fps, 35 ms frame with no saturated thread (translation/sync bound) (open)
• [GBug] Zelda: Ocarina of Time (0400486024DEC000): the audio plays a different part of the stream than the picture (open)
• [VBug] [nx2-build-75] Zelda: Ocarina of Time (0400486024DEC000) black screen — no AV1 decoder (open)
• [VBug] OoT (0400486024DEC000): world renders black except areas lit by Navi and around Link, AMD RX 9070 (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: 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: 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: 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: 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: User-reported reproducible freeze when walking deeper into the pot room in Hyrule Castle Town, near the guard.
• 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: 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: 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: Slows when booting.
• 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: 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: On Windows build-83, shutdown can hang at “Closing software…” after gameplay. Some sessions completed shutdown successfully; the cause is undetermined.
• 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: 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: PGO artifact crashes in dynarmic with Unhandled SIGSEGV after 2–10 minutes on the reported machine.
• 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.

Compared with Previous Build