Zelda: Ocarina of Time
Slows when booting.
Compatibilidade de jogos
Compatibilidade de jogos no Lichii Emulator
Tem um jogo em mente? Veja como ele roda no Lichii, confira os problemas conhecidos e escolha uma versão para testar.
Latest recorded build
build-94
Pre-release
Published November 7, 2026
Encontre um jogo
Buscar jogos compatíveis com o Lichii
Os dados atuais incluem 76 registros de jogo e ambiente e 175 relatos sobre o Lichii.
Não encontrou um jogo? Um resultado vazio significa que ainda não há um relato sobre ele no Lichii. Isso não indica falha em um teste.
Confira a plataforma indicada para distinguir diferentes versões de um jogo.
O que cada status significa: “Unknown”: sem conclusão. “Not booting”: o jogo não iniciou. “Boots”: só a inicialização foi confirmada. “Runs with issues”: houve problemas durante o jogo. “Playable”: foi possível continuar jogando durante o teste.
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.
Zelda: Ocarina of Time Reported platform: unknown
Also listed as: OoT
| Build | Status | GPU / CPU | FPS | Details |
|---|---|---|---|---|
| Not provided | unknown | intel arc b580 / Not provided | 10 FPS | Open report |
| 95 | not booting | AMD RX 9000 series / Not provided | Not provided | Open report |
Not provided report
Statusunknown
GPUintel arc b580
CPUNot provided
DriverNot provided
Recorded FPS10 FPS
Problems or notes: User reports the game runs at 10 FPS.
95 report
Statusnot booting
GPUAMD RX 9000 series
CPUNot provided
DriverNot provided
Recorded FPSNot provided
Problems or notes: The reporter says the game hangs on a black screen while outputting normal audio. They report it used to boot on 88 with launch parameters, but no longer does. A commenter reports no video output on build 95 after video output on build 93, and another says Docked Mode with Accurate GPU loads the main menu but audio gets issues again.
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-93 (1 record); previous: build-88 (1 record).
Zelda: Ocarina of Time Reported platform: Windows 11, Vulkan
Also listed as: OoT
| Build | Status | GPU / CPU | FPS | Details |
|---|---|---|---|---|
| nx2 @ 27226d2 plus two measurement-only commits | runs with issues | RTX 5060 Laptop (8 GB) / Ryzen AI 9 365 | Not provided | Open report |
nx2 @ 27226d2 plus two measurement-only commits report
Statusruns with issues
GPURTX 5060 Laptop (8 GB)
CPURyzen AI 9 365
Driver621.01
Recorded FPSNot provided
Problems or notes: In Kokiri Forest, disabling per-fence Preflushable downloads or batching them by 64 fences caused overexposure. Default per-fence downloads preserved correct exposure. The report measures GPU back-thread draws/s, not game FPS.
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
Zelda: Ocarina of Time Reported platform: Linux, Fedora 44
Also listed as: OoT
| Build | Status | GPU / CPU | FPS | Details |
|---|---|---|---|---|
| Not provided | unknown | RTX 3080 Ti / i9-12900K | 46–47.8 FPS | Open report |
Not provided report
Statusunknown
GPURTX 3080 Ti
CPUi9-12900K
Driver615.78
Recorded FPS46–47.8 FPS
Problems or notes: A user comment reports same-binary, 300-second headless-harness measurements in Kokiri Forest: median FPS was 46.0 in Full mode and 47.8 in Auto mode. The comment reports correct auto-exposure in both modes and identifies readback bandwidth and stale-constants flicker as visible concerns; no sustained gameplay validation is stated.
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
Zelda Ocarina Of Time Remake Reported platform: unknown
| Build | Status | GPU / CPU | FPS | Details |
|---|---|---|---|---|
| build-93 | runs with issues | RX 5700 XT 8GB / Ryzen 5 5600 | Not provided | Open report |
| build-93 | runs with issues | AMD Radeon 9070XT / Intel Core I5 | Not provided | Open report |
| Not provided | unknown | GTX 1070 8GB / Ryzen 5 5500 | Not provided | Open report |
| Not provided | runs with issues | rx7600xt 16gb / ryzen 5 5600 | Not provided | Open report |
build-93 report
Statusruns with issues
GPURX 5700 XT 8GB
CPURyzen 5 5600
DriverNot provided
Recorded FPSNot provided
Problems or notes: User reports excessive bloom outside the Great Deku Tree, returning to normal after defeating Gohma, and invisible boxes and walls inside it. Windows 10.
build-93 report
Statusruns with issues
GPUAMD Radeon 9070XT
CPUIntel Core I5
DriverNot provided
Recorded FPSNot provided
Problems or notes: 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.
Not provided report
Statusunknown
GPUGTX 1070 8GB
CPURyzen 5 5500
DriverNot provided
Recorded FPSNot provided
Problems or notes: Commenter reports the same issue; Windows and build are not stated.
Not provided report
Statusruns with issues
GPUrx7600xt 16gb
CPUryzen 5 5600
DriverNot provided
Recorded FPSNot provided
Problems or notes: Commenter says the game runs pretty well and posts an image, but is unsure whether it relates to bloom. No specific issue is identified.
Related game issues
- [GBug] Textures not working properly, slow frame rate and shield glitch in The Legend of Zelda Ocarina of Time remake (open)
- [GBug] (open)
- [VBug] Invisible things and bloom in Zelda Ocarina Of Time Remake (AMD GPU) (open)
- Release note: 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.
- Release note: User reports excessive bloom outside the Great Deku Tree and invisible boxes and walls inside it.
Compared with Previous Build
Current: build-93 (2 records); previous: build-88 (0 records).
Showing 91–98 of 98 reports
Known issues from Lichii sources
Known Game Issues
Legend of Green hat boy
User reports the game crashes after about 15 to 20 minutes.
Kirby Air Riders
The emulator force quits after being stuck on the "Loading Shaders" screen for about 2 seconds.
Other / not listed
After the intro, the scene where the deku tree is talking is completely black with very slow, stuttery dialogue.
Other / not listed
After the startup screen, audio plays but the screen is black.
Other / not listed
Music disappears during the cutscene after booting the game.
Other / not listed
The game crashes while building shaders after the title card fades.
Hyrule Warriors
An error appears after the cinematic and remains on screen, blocking the view.
Other / not listed
Black screen during cinematic after the main menu appears; reported on Windows 11 with an AMD RX 6000 series or older GPU.
Other / not listed
Infinite startup launch loop when booting the .NUP version.
Showing 141–150 of 188 issues
Notas de versão recentes
Mudanças na compatibilidade nas versões mais recentes
Versão build-94 · Ocarina of Time
Fixes near foliage disappearing, white flashes during camera movement, terrain drawn over the scene, a stale Z-target reticle, and several shader issues. The changes had only limited gameplay testing.
Versão build-94 · Não informado
Fixes a race-related random crash involving an unallocated SparseLargeVector region, which the release says can affect any game.
Versão build-94 · Não informado
Adds LayeredFS mod support for NUP titles.
Versão build-94 · Não informado
The migration prompt's Keep Old Data option now keeps data instead of moving it.
Versão build-94 · Não informado
Adds an experimental option to pin GPU threads to their own cores. It is off by default and requires 6 or more physical performance cores.
Escolha da versão
Qual versão devo usar?
build-93 · Publicada em November 6, 2026
Zelda: Ocarina of Time
- runs with issues · GPU RX 9060XT 16GB · CPU Ryzen 5 7600 · Driver Não informado
7 arquivos para download nesta versão.
build-88 · Publicada em November 6, 2026
Zelda: Ocarina of Time
- not booting · GPU AMD Radeon AI PRO R9700 (9070XT) · CPU Não informado · Driver Não informado
7 arquivos para download nesta versão.
build-83 · Publicada em November 6, 2026
Zelda: Ocarina of Time
- runs with issues · GPU RTX 4070 SUPER 12 GB · CPU i5-14600KF · Driver 621.14
- unknown · GPU AMD RX 6000 series or older; AMD Radion RX 6650 XT · CPU AMD Ryzen 5 5600 · Driver Não informado
- unknown · GPU Não informado · CPU Não informado · Driver Não informado
12 arquivos para download nesta versão.
Experimente a versão mais recente disponível: build-94. Guarde uma versão que funcione para poder voltar a ela durante os testes.
Dúvidas sobre compatibilidade
Perguntas frequentes sobre compatibilidade de jogos
Como compartilho um jogo com esses filtros?
Aplique os filtros de jogo, status, GPU e versão e copie a URL da página. Um link para um jogo específico abre o cartão de relatos dele.
O que devo tentar se a tela ficar preta?
Confira nos outros relatos se o jogo chega aos menus ou se dá para jogar. Anote o driver e o renderizador e procure o jogo ou o erro no guia de solução de problemas.
Por que a mesma GPU pode apresentar resultados diferentes?
A versão do driver, as configurações gráficas, a carga da CPU e o trecho do jogo testado podem influenciar o resultado. Compare esses detalhes antes de alterar sua configuração.
Onde posso enviar um resultado que ainda não aparece aqui?
Use a lista oficial de issues do Lichii. Informe o jogo, a tag da versão, o hardware, o driver, as configurações e os passos para reproduzir o que você observou.