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
Compatibilité des jeux
Compatibilité des jeux avec Lichii Emulator
Vous avez un jeu en tête ? Voyez comment il tourne dans Lichii, repérez les problèmes et choisissez une version à essayer.
Latest recorded build
build-88
Pre-release
Published November 6, 2026
Trouver un jeu
Rechercher des jeux compatibles avec Lichii
Les données actuelles comptent 58 entrées par jeu et environnement, et 114 rapports sur Lichii.
Un jeu manque ? Un résultat vide indique qu’aucun rapport sur ce jeu n’est encore répertorié pour Lichii. Cela ne signifie pas que le jeu a échoué à un test.
Consultez la plateforme indiquée pour distinguer les différentes versions d’un jeu.
Signification des statuts : « Unknown » : aucune conclusion. « Not booting » : le jeu ne démarre pas. « Boots » : seul le démarrage a été constaté. « Runs with issues » : des problèmes surviennent en jeu. « Playable » : la personne ayant testé le jeu a pu continuer à jouer.
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 |
|---|---|---|---|---|
| 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 |
| Not provided | runs with issues | RX 6650 XT (RDNA2) / i5-10400F | 25–27 FPS | Open report |
| nx2 `5a50f50e0b` (official PGO artifact of build-80 and local non-PGO build of nx2-latest) | runs with issues | AMD RX 9070 XT (RDNA4, 16 GB) / Ryzen 7 5800X3D (8C/16T), 32 GB RAM | 28–35 FPS | Open report |
| Not provided | runs with issues | AMD RX 9070 XT / Not provided | Not provided | Open report |
| Not provided | playable | RTX 5090 / Not provided | 40–60 FPS | Open report |
| Not provided | unknown | AMD 7600 / Not provided | Not provided | Open report |
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.
Not provided report
Statusruns with issues
GPURX 6650 XT (RDNA2)
CPUi5-10400F
DriverAMD proprietary driver 2.0.353 (`amdvlk64.dll` 32.0.21045.16010)
Recorded FPS25–27 FPS
Problems or notes: A user comment reports that with three shaders built unoptimized, the intro plays and the game reaches Kokiri Forest, with cutscenes at about 25 to 27 FPS. With `EDEN_NX2_NOOPT_SHADERS=all`, it ran at about 16 to 17 FPS. With asynchronous shader compilation on, this build showed a black screen with audio or stayed at “Loading Shaders” at 0 FPS; the user had not waited long enough to determine whether it would finish.
nx2 `5a50f50e0b` (official PGO artifact of build-80 and local non-PGO build of nx2-latest) report
Statusruns with issues
GPUAMD RX 9070 XT (RDNA4, 16 GB)
CPURyzen 7 5800X3D (8C/16T), 32 GB RAM
DriverMesa 26.x RADV
Recorded FPS28–35 FPS
Problems or notes: User reports gameplay at 28–35 fps with 31–36 ms frame time and no saturated thread. The PGO artifact crashes in dynarmic with Unhandled SIGSEGV after 2–10 minutes on this machine; a local non-PGO build was stable over several sessions.
Not provided report
Statusruns with issues
GPUAMD RX 9070 XT
CPUNot provided
Driver26.10.2
Recorded FPSNot provided
Problems or notes: A commenter reports approximately 3 minutes of gameplay before a black screen, driver crash, and crash to desktop.
Not provided report
Statusplayable
GPURTX 5090
CPUNot provided
DriverNot provided
Recorded FPS40–60 FPS
Problems or notes: Gameplay testing in Kokiri Forest reported no crashes; normal game speed was below 60 FPS with #216. GPU accuracy was Low.
Not provided report
Statusunknown
GPUAMD 7600
CPUNot provided
DriverNot provided
Recorded FPSNot provided
Problems or notes: A commenter reports having the same issue without further details.
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: 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
- 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: 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
- 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: Windows 11
Also listed as: OoT
| Build | Status | GPU / CPU | FPS | Details |
|---|---|---|---|---|
| build-88 | runs with issues | AMD Radeon RX 9070 XT / AMD Ryzen 7 7800X3D | Not provided | Open report |
build-88 report
Statusruns with issues
GPUAMD Radeon RX 9070 XT
CPUAMD Ryzen 7 7800X3D
DriverAdrenalin 26.10.1 (also tested an older driver)
Recorded FPSNot provided
Problems or notes: The logo, text, and UI are visible, but the 3D environment and background remain black; audio continues. AMD driver timeouts or crashes sometimes occur. The issue persists after updating and rolling back the driver and restarting. The issue author says graphics displayed previously, but the issue appeared afterward.
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 101–110 of 114 reports
Known issues from Lichii sources
Known Game Issues
Zelda: Ocarina of Time
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.
Star Fox
On RTX 50-series GPUs, the GPU device can still be lost after a scene change.
Recorded fix: Try NVIDIA driver 610.88.
Star Fox
Gameplay is capped at about 30 fps, even though the game asks for 60.
Star Fox
On RTX 50-series GPUs (5070 Ti, 5090), the GPU device can be lost shortly after a scene change.
Recorded fix: Try NVIDIA driver 610.88.
Yoshi and the Mysterious Book (demo)
Some textures are still black, and the game can crash later in play.
Kirby Air Riders
Some races still stall while shaders build.
Zelda: Ocarina of Time
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.
Zelda: Ocarina of Time
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.
Hyrule Warriors
In stages past the first one, the gameplay screen is black while the UI remains visible; pausing shows the world rendered in the background.
Zelda: Ocarina of Time
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.
Showing 1–10 of 98 issues
Notes de version récentes
Changements de compatibilité dans les dernières versions
Version build-88 · Non renseigné
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.
Version build-88 · Non renseigné
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.
Version build-88 · Non renseigné
Fixed temporal history, motion interpolation, image transitions, and descriptor retirement for FSR3 frame generation; frame generation remains off by default.
Version 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.
Version 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.
Choix d’une version
Quelle version utiliser ?
Choisissez un jeu ci-dessus pour voir quelles versions testées sont disponibles au téléchargement. En attendant, utilisez la dernière version disponible et lisez ses notes.
Essayez la dernière version disponible : build-88. Gardez une version fonctionnelle sous la main pendant vos essais.
Questions sur la compatibilité
FAQ sur la compatibilité des jeux
Comment partager un jeu avec ces filtres ?
Appliquez les filtres de jeu, de statut, de GPU et de version, puis copiez l’URL de la page. Un lien vers un jeu précis ouvre sa fiche.
Que faire si j’obtiens un écran noir ?
Vérifiez dans d’autres rapports si le jeu atteint les menus ou une partie jouable. Notez votre pilote et le moteur de rendu, puis recherchez le jeu ou l’erreur dans le guide de dépannage.
Pourquoi un même GPU peut-il donner des résultats différents ?
La version du pilote, les réglages graphiques, la charge du processeur et la partie du jeu testée peuvent influer sur le résultat. Comparez ces détails avant de modifier votre configuration.
Où puis-je soumettre un résultat manquant ?
Utilisez le suivi officiel des tickets de Lichii. Indiquez le jeu, le tag de la version, le matériel, le pilote, les réglages et les étapes pour reproduire ce que vous avez observé.