After: Dynamic FPS mod bundled and enabled by default; automatic patching is restricted to the supported game build and checks for patch conflicts.
build-83 → build-88
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.
Zelda: Ocarina of Time Reported platform: CachyOS; Proton
Also listed as: OoT
| Build | Status | GPU / CPU | FPS | Details |
|---|---|---|---|---|
| build-88 | runs with issues | 7800xt / Ryzen 7 5700X | Not provided | Open report |
build-88 report
Statusruns with issues
GPU7800xt
CPURyzen 7 5700X
DriverNot provided
Recorded FPSNot provided
Problems or notes: A commenter reports a large audio/video delay during the initial cutscene, followed by black screens on both monitors, a GPU crash and reset, and a Hyprland crash when they start controlling the character.
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
From build-83 to build-88: follow the gameplay changes described for these two builds.
Zelda: Ocarina of Time Reported platform: Windows
Also listed as: OoT
| Build | Status | GPU / CPU | FPS | Details |
|---|---|---|---|---|
| build-83 | runs with issues | RTX 5090 / Ryzen 7 9800X3D | Not provided | Open report |
| Not provided | runs with issues | RX 5700 / Not provided | Not provided | Open report |
build-83 report
Statusruns with issues
GPURTX 5090
CPURyzen 7 9800X3D
DriverNVIDIA 617.42
Recorded FPSNot provided
Problems or notes: Opening rendered and controllable Kokiri Forest gameplay was reached. Some sessions hung at “Closing software…” during shutdown, while others exited successfully. The source does not establish a cause or fix.
Not provided report
Statusruns with issues
GPURX 5700
CPUNot provided
DriverAMD proprietary driver
Recorded FPSNot provided
Problems or notes: A commenter reports a black 3D world with working UI. The commenter proposes possible shader reordering and fragment shader shuffle causes, and describes code changes and measurements from other projects; these are user-provided claims, not confirmed Lichii fixes.
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
Current: build-83 (1 record); previous: build-75 (0 records).
Zelda: Ocarina of Time Reported platform: unknown
Also listed as: OoT
| Build | Status | GPU / CPU | FPS | Details |
|---|---|---|---|---|
| build-88 | not booting | AMD Radeon AI PRO R9700 (9070XT) / Not provided | Not provided | Open report |
| Not provided | unknown | Not provided / Not provided | Not provided | Open report |
| build-83 | runs with issues | RTX 4070 SUPER 12 GB / i5-14600KF | 30 FPS | Open report |
| build-83 | unknown | AMD RX 6000 series or older; AMD Radion RX 6650 XT / AMD Ryzen 5 5600 | Not provided | Open report |
| build-83 | unknown | Not provided / Not provided | Not provided | Open report |
| build-75 | runs with issues | RTX 3080 / Ryzen 5900X | 12–22 FPS | Open report |
| Not provided | runs with issues | AMD Radeon RX 6600 XT 8 GB / Ryzen 5 5600X | 25–33 FPS | Open report |
build-88 report
Statusnot booting
GPUAMD Radeon AI PRO R9700 (9070XT)
CPUNot provided
DriverNot provided
Recorded FPSNot provided
Problems or notes: User reports the app crashes when opening the game, with a segmentation fault. They say some earlier builds worked.
Not provided report
Statusunknown
GPUNot provided
CPUNot provided
DriverNot provided
Recorded FPSNot provided
Problems or notes: Dynamic FPS is enabled by default, but full gameplay timing has not been verified; CPU Clock Boost/Overclock can affect game speed.
build-83 report
Statusruns with issues
GPURTX 4070 SUPER 12 GB
CPUi5-14600KF
Driver621.14
Recorded FPS30 FPS
Problems or notes: Issue reporter describes shader problems and gameplay at about 30% speed. A commenter reports that GPU Mode: Fast restored normal speed and reached 60 FPS in most areas; build-83 held 60 FPS after the shader cache warmed up. The commenter also reports stutter while new shader pipelines are built.
build-83 report
Statusunknown
GPUAMD RX 6000 series or older; AMD Radion RX 6650 XT
CPUAMD Ryzen 5 5600
DriverNot provided
Recorded FPSNot provided
Problems or notes: Reported that the game slows when booting; the reporter restarted the emulator and game and changed settings, but did not state a resolution.
build-83 report
Statusunknown
GPUNot provided
CPUNot provided
DriverNot provided
Recorded FPSNot provided
Problems or notes: The release says the perf9 build was tested successfully in Ocarina of Time, but provides no gameplay duration or specific tested hardware.
build-75 report
Statusruns with issues
GPURTX 3080
CPURyzen 5900X
DriverNot provided
Recorded FPS12–22 FPS
Problems or notes: Outdoor areas have excessive fog and glow, performance is about 12–22 fps, and three rare shaders remain unsupported.
Not provided report
Statusruns with issues
GPUAMD Radeon RX 6600 XT 8 GB
CPURyzen 5 5600X
DriverAMD proprietary driver 2.0.353 (`amdvlk64.dll` 32.0.21045.16010)
Recorded FPS25–33 FPS
Problems or notes: On the reported Windows 11 setup, the intro freezes at 0 FPS while two compute pipelines compile, taking 6 and 18 minutes. After compilation and caching, the intro proceeds; reported scenes run at about 33 FPS. Disabling optimization builds the pipelines faster but reported scenes run at about 25 FPS. Rejecting the two shader hashes makes the intro play at 60 FPS but leaves parts of the picture black.
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
From build-83 to build-88: follow the gameplay changes described for these two builds.
After: Dynamic FPS mod bundled and enabled by default; automatic patching is restricted to the supported game build and checks for patch conflicts.
build-83 → build-88
Showing 41–50 of 61 reports
Known issues from Lichii sources
Known Game Issues
The Legend of Zelda: Ocarina of Time
The 3D gameplay scene is black while HUD elements remain visible; menus and item preview can render correctly.
Other / not listed
Terrain is visible through solid objects after getting past the intro.
Fire Emblem
FMVs and pre-rendered videos are skipped, including the opening cut-scene.
Donkey Kong Bananza
On build 70 (286117c), the MSVC zip aborts after 133.8 seconds of gameplay with 0xC0000409 at lichii.exe+0x2ecd3bd. The MinGW PGO zip reportedly aborts on the intro screen at the same offset.
Donkey Kong Bananza
A black rectangle appears in a mini-example guide; the reporter says it persists on build-70.
Donkey Kong Bananza
Weird artifacts, especially on shadows.
Pokémon Pokopia
User reports a black screen while loading in Build 65.
Kirby Riders
Freezes while menu preview videos play on build 65. A comment reports a custom kirby-test build log showing the game aborting (2162-0001) during menu videos.
Showing 91–98 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?
build-83 · Publicada el November 6, 2026
The Legend of Zelda: Ocarina of Time
- runs with issues · GPU AMD Radeon RX 9060 XT 16 GB · CPU Intel i7-9700K · Controlador AMD proprietary driver 32.0.32015.7029
12 archivos para descargar en esta versión.
build-75 · Publicada el November 5, 2026
The Legend of Zelda: Ocarina of Time
- runs with issues · GPU RX 5700 · CPU No indicado · Controlador amdvlk 32.0.21045.16010
- runs with issues · GPU AMD Radeon RX 7900 XTX · CPU No indicado · Controlador AMD proprietary driver 2.0.416
12 archivos para descargar en esta versión.
build-70 · Publicada el November 4, 2026
The Legend of Zelda: Ocarina of Time
- not booting · GPU NVIDIA GeForce RTX 3070 · CPU AMD Ryzen 7 5800X 8-Core Processor · Controlador NVIDIA 621.1.0.0
12 archivos para descargar en esta versión.
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.