The Legend of Zelda: Ocarina of Time
On Linux with AMD/RADV, AV1 intro cutscene video renders solid green while audio and subtitles work.
Compatibilidad de juegos
Compatibilidad de juegos con Lichii Emulator
¿Tienes un juego en mente? Comprueba cómo funciona en Lichii, revisa los problemas detectados y elige una versión para probar.
Latest recorded build
build-88
Pre-release
Published November 6, 2026
Encuentra un juego
Buscar juegos compatibles con Lichii
Los datos actuales incluyen 58 registros de juego y entorno y 114 informes sobre Lichii.
¿No encuentras un juego? Si no hay resultados, aún no se muestra ningún informe de Lichii sobre ese juego. No significa que haya fallado una prueba.
Fíjate en la plataforma indicada para distinguir entre distintas versiones de un juego.
Qué significa cada estado: «Unknown»: sin conclusión. «Not booting»: el juego no arrancó. «Boots»: solo se confirmó el arranque. «Runs with issues»: hubo problemas durante la partida. «Playable»: la persona que hizo la prueba pudo seguir jugando.
Compatibility results
Game Compatibility Results
Recorded performance
Performance by Build and Hardware
Open a game for its test details. Start with a GPU and build close to your own, then explore the driver, FPS, and gameplay notes.
No games match these filters. Try a different name, GPU, or build, or clear a filter to broaden the search.
Yoshi and the Mysterious Book (demo) Reported platform: unknown
| Build | Status | GPU / CPU | FPS | Details |
|---|---|---|---|---|
| build-70 | runs with issues | Not provided / Not provided | Not provided | Open report |
build-70 report
Statusruns with issues
GPUNot provided
CPUNot provided
DriverNot provided
Recorded FPSNot provided
Problems or notes: Some textures are still black, and it can crash later in play.
Related game issues
Compared with Previous Build
Current: build-70 (1 record); previous: build-65 (0 records).
Zelda Ocarina of Time Reported platform: Windows 11
| Build | Status | GPU / CPU | FPS | Details |
|---|---|---|---|---|
| build-75 | not booting | AMD RX 6000 series or older / Not provided | Not provided | Open report |
| build-75 | runs with issues | RTX 3070 / 7800x3D | Not provided | Open report |
| Lichii build-75 (nx2-build-75) | not booting | RTX 5080 / Not provided | 60 FPS | Open report |
build-75 report
Statusnot booting
GPUAMD RX 6000 series or older
CPUNot provided
DriverNot provided
Recorded FPSNot provided
Problems or notes: User reports that sound and the Zelda logo work, but the game displays a black screen. Comments also report black screens on AMD and NVIDIA GPUs and on Linux.
build-75 report
Statusruns with issues
GPURTX 3070
CPU7800x3D
DriverNot provided
Recorded FPSNot provided
Problems or notes: Commenters report that shared settings resolved the black screen on the MSVC build, but serious FPS, ambient occlusion, and lighting issues remain.
Lichii build-75 (nx2-build-75) report
Statusnot booting
GPURTX 5080
CPUNot provided
Driver621.14
Recorded FPS60 FPS
Problems or notes: A commenter reports that the title screen displays at 60 FPS but the screen goes black after selecting New Game and remains black through the intro cutscene. The log reports that FFmpeg has no decoder for video/av1.
Related game issues
- [GBug] Black Screen In AMD - Zelda Ocarina Of Time (open)
- [Crash] infinite launch screen with legend of zelda ocarina of time (open)
- Release note: Black screen after boot; some reports say sound and the title/logo work.
- Release note: On build-83, one user reports a solid-green displayed image although a screen capture shows the game rendering correctly.
- Release note: On build 83, a user reports device loss at gameplay start with VK_ERROR_DEVICE_LOST.
Compared with Previous Build
Current: build-75 (2 records); previous: build-70 (0 records).
Zelda Ocarina of Time Reported platform: Windows
| Build | Status | GPU / CPU | FPS | Details |
|---|---|---|---|---|
| build-83 | runs with issues | RX 9060 XT 16 GB / Not provided | Not provided | Open report |
build-83 report
Statusruns with issues
GPURX 9060 XT 16 GB
CPUNot provided
Driver32.0.32015.7029
Recorded FPSNot provided
Problems or notes: User reports that the black-screen behavior is gone and the game reaches gameplay, but it device-loses at gameplay start with VK_ERROR_DEVICE_LOST.
Related game issues
- [GBug] Black Screen In AMD - Zelda Ocarina Of Time (open)
- [Crash] infinite launch screen with legend of zelda ocarina of time (open)
- Release note: Black screen after boot; some reports say sound and the title/logo work.
- Release note: On build-83, one user reports a solid-green displayed image although a screen capture shows the game rendering correctly.
- Release note: On build 83, a user reports device loss at gameplay start with VK_ERROR_DEVICE_LOST.
Compared with Previous Build
Current: build-83 (1 record); previous: build-75 (0 records).
Zelda Ocarina of Time Reported platform: Windows 11 24H2
| Build | Status | GPU / CPU | FPS | Details |
|---|---|---|---|---|
| Lichii nx2-build-83 | not booting | AMD Radeon RX 6650 XT (RDNA2) / Intel Core i5-10400F | Not provided | Open report |
| nx2-build-83 | runs with issues | Radeon RX 6800 / Not provided | 43–47 FPS | Open report |
Lichii nx2-build-83 report
Statusnot booting
GPUAMD Radeon RX 6650 XT (RDNA2)
CPUIntel Core i5-10400F
Driver32.0.21045.16010 (15/10/2026); also reproduced on 32.0.21030.2001 (24/09/2025)
Recorded FPSNot provided
Problems or notes: User reports the render area remains black after booting, in both handheld and docked modes. Updating the AMD driver, clearing the shader cache, changing listed settings, and trying other builds did not change the result.
nx2-build-83 report
Statusruns with issues
GPURadeon RX 6800
CPUNot provided
DriverAMD 2.0.353 (AMDVLK 9.2.10.353)
Recorded FPS43–47 FPS
Problems or notes: User reports the game renders correctly in a screen capture at about 47 fps, but the displayed image is solid green. The report states about 43 fps during presentation.
Related game issues
- [GBug] Black Screen In AMD - Zelda Ocarina Of Time (open)
- [Crash] infinite launch screen with legend of zelda ocarina of time (open)
- Release note: Black screen after boot; some reports say sound and the title/logo work.
- Release note: On build-83, one user reports a solid-green displayed image although a screen capture shows the game rendering correctly.
- Release note: On build 83, a user reports device loss at gameplay start with VK_ERROR_DEVICE_LOST.
Compared with Previous Build
Zelda: Ocarina of Time Reported platform: Windows x86_64
Also listed as: OoT
| Build | Status | GPU / CPU | FPS | Details |
|---|---|---|---|---|
| build-83 (PGO, Windows x86_64) | runs with issues | RTX 3090 24 GB / Ryzen 9 5900X | Not provided | Open report |
build-83 (PGO, Windows x86_64) report
Statusruns with issues
GPURTX 3090 24 GB
CPURyzen 9 5900X
Driverv621.14
Recorded FPSNot provided
Problems or notes: User reports that about 99–104 graphics pipelines are rebuilt on the GPU thread during the first 10 seconds of gameplay on each boot, taking about 943.3–998.1 ms and causing a visible hitch.
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
Zelda: Ocarina of Time Reported platform: Linux
Also listed as: OoT
| Build | Status | GPU / CPU | FPS | Details |
|---|---|---|---|---|
| build 83 (clang 23.1.6) | runs with issues | AMD RX 9000 series / Not provided | Not provided | Open report |
build 83 (clang 23.1.6) report
Statusruns with issues
GPUAMD RX 9000 series
CPUNot provided
DriverMesa RADV
Recorded FPSNot provided
Problems or notes: User reports repeated segfaults during gameplay in the Great Deku Tree while RADV builds a graphics pipeline. The reported fragment shader fails spirv-val because its depth image sampled type is u32 while the sampling result type is f32.
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
Zelda: Ocarina of Time Reported platform: macOS arm64
Also listed as: OoT
| Build | Status | GPU / CPU | FPS | Details |
|---|---|---|---|---|
| Not provided | runs with issues | Not provided / Apple M6 (arm64) | 12–14 FPS | Open report |
Not provided report
Statusruns with issues
GPUNot provided
CPUApple M6 (arm64)
DriverMoltenVK 1.4.1 (bundled `v1.4.1-ryujinx`)
Recorded FPS12–14 FPS
Problems or notes: The title screen and intro video render, but the emulator may lose the Metal device or hang at the intro-video/gameplay boundary. The report also describes GPU-thread deadlocks or hangs and, in one run, a process abort. Intro playback is reported at 12–14 FPS. A commenter reports a separate black 3D scene with sound and subtitles after applying a local workaround on an Eglantine fork; current nx2 behavior was not yet confirmed.
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
Showing 81–90 of 114 reports
Known issues from Lichii sources
Known Game Issues
The Legend of Zelda: Ocarina of Time
On Windows 10 with AMD, the intro AV1 cutscene shows a black video layer with working audio and subtitles, then the emulator hangs indefinitely.
Ocarina of Time
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.
The Legend of Zelda: Ocarina of Time
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.
Other / not listed
User reports a black background at the title screen and a black screen after starting a new game, with sound still audible.
The Legend of Zelda: Ocarina of Time
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.
The Legend of Zelda: Ocarina of Time
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.
Other / not listed
Music disappears during the cutscene after booting the game.
OoT
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.
Other / not listed
The game crashes while building shaders after the title card fades.
Showing 71–80 of 98 issues
Notas de versiones recientes
Cambios de compatibilidad en las últimas versiones
Versión build-88 · No indicado
Integrated performance ports and reduced unnecessary writer tracking; added explicit GPU-to-host visibility before buffer readback and submitted native desktop GPU work earlier while preserving conservative synchronization for macro reads and semaphore waits.
Versión build-88 · No indicado
Added bounded background preparation of cached graphics pipelines and persistent task/mesh shader state. Updated the Vulkan cache to v53 while preserving compatible v52 caches, and made interrupted cache migrations retryable.
Versión build-88 · No indicado
Fixed temporal history, motion interpolation, image transitions, and descriptor retirement for FSR3 frame generation; frame generation remains off by default.
Versión build-88 · Zelda: Ocarina of Time
Bundled Dark's Dynamic FPS mod, enabled by default for Ocarina of Time. Disable it independently in the game's Add-Ons settings. Max Resolution remains a separate Add-On. CPU Clock Normal is recommended when evaluating the mod; Boost/Overclock can affect game speed. Full gameplay timing has not been verified.
Versión build-83 · Ocarina of Time
Fixed missing vegetation, incorrect materials and lighting, a glowing doorway, one-frame white flashes, and an AMD black 3D scene. Added Max Resolution (built-in), enabled by default for the supported game build, and Ocarina-specific frame-ahead presentation tuning.
Elegir una versión
¿Qué versión debo usar?
Elige un juego arriba para ver qué versiones probadas puedes descargar. Mientras tanto, usa la descarga más reciente y lee sus notas.
Prueba la última versión disponible: build-88. Conserva una versión que funcione por si necesitas volver a ella durante las pruebas.
Dudas sobre compatibilidad
Preguntas frecuentes sobre compatibilidad de juegos
¿Cómo comparto un juego con estos filtros?
Aplica los filtros de juego, estado, GPU y versión y copia la URL de la página. Un enlace a un juego concreto abre su ficha de informes.
¿Qué puedo probar si aparece una pantalla negra?
Revisa en otros informes si el juego llega a los menús o permite jugar. Anota el controlador y el motor de renderizado y busca el juego o el error en la guía de solución de problemas.
¿Por qué puede dar resultados distintos la misma GPU?
La versión del controlador, los ajustes gráficos, la carga de la CPU y el tramo del juego que se prueba pueden cambiar el resultado. Compara estos detalles antes de cambiar tu configuración.
¿Dónde puedo aportar un resultado que no aparece?
Usa el gestor oficial de incidencias de Lichii. Indica el juego, la etiqueta de la versión, el hardware, el controlador, los ajustes y los pasos para reproducir lo que viste.