Other / not listed
Fairy-light flickering and flashing white sky, reported in Sacred Grove and other locations; may occur randomly without clear reproduction steps.
Spielekompatibilität
Spielekompatibilität des Lichii Emulators
Du hast ein bestimmtes Spiel im Sinn? Erfahre, wie es mit Lichii läuft, welche Probleme bekannt sind und welchen Build du ausprobieren kannst.
Latest recorded build
build-117
Published November 7, 2026
Ein Spiel finden
Nach kompatiblen Lichii-Spielen suchen
108 Einträge zu Spielen und Testumgebungen sowie 308 Lichii-Berichte sind derzeit erfasst.
Dein Spiel fehlt? Ein leeres Suchergebnis bedeutet, dass noch kein Lichii-Bericht erfasst ist. Daraus lässt sich kein fehlgeschlagener Test ableiten.
An der Plattformangabe erkennst du, welche Version eines Spiels gemeint ist.
Was die Statuswerte bedeuten: Unknown bedeutet, dass kein Ergebnis feststeht. Not booting heißt, dass das Spiel nicht startete. Boots steht dafür, dass nur der Start gelang. Runs with issues bezeichnet Probleme beim Spielen. Playable heißt, dass der Tester weiterspielen konnte.
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.
Splatoon Raiders Reported platform: unknown
| Build | Status | GPU / CPU | FPS | Details |
|---|---|---|---|---|
| build93 | unknown | AMD RX 9000 series / Not provided | Not provided | Open report |
build93 report
Statusunknown
GPUAMD RX 9000 series
CPUNot provided
DriverNot provided
Recorded FPSNot provided
Problems or notes: The main area has a rhythmic wavy edge effect, described as depth of field toggling on and off. The reporter says it worked in the first release, but does not know about intervening builds.
Related game issues
- [VBug] Splatoon Raiders — [AMD]: Game's graphics all pixelated and blurr, with a bit slow FPS. | Liichi 95 (open)
- [VBug] Splatoon raiders wavy effect on edges like depth of field toggling on and off rythmicaly (open)
- MacOS: Splatoon Raiders unable to swim in ink (closed)
- [Feature Request] dynamic fps splatoon raiders (open)
- Release note: Characters look too dark, there is a green tint, and FPS is lower than in earlier builds.
- Release note: Characters look too dark, there is a green tint, and FPS is lower than in earlier builds. The issue is being investigated.
- Release note: User reports pixelated, blurry graphics and somewhat slow FPS on integrated AMD graphics in Windows 11.
- Release note: Rhythmic wavy effect on edges in the main area, described as depth of field toggling on and off.
- Release note: The reporter says they cannot swim in ink during the tutorial on MacOS.
Compared with Previous Build
Current: build-117 (1 record); previous: build-116 (1 record).
Splatoon Raiders Reported platform: Windows 11
| Build | Status | GPU / CPU | FPS | Details |
|---|---|---|---|---|
| build-95(or 94 whatever) | runs with issues | Integrated graphics AMD / Not provided | Not provided | Open report |
build-95(or 94 whatever) report
Statusruns with issues
GPUIntegrated graphics AMD
CPUNot provided
DriverNot provided
Recorded FPSNot provided
Problems or notes: User reports pixelated, blurry graphics and somewhat slow FPS. They say the game worked in Selevet 6, a fork used before Liichi. The user speculates anti-aliasing may be related, but says changing anti-aliasing settings did not help.
Related game issues
- [VBug] Splatoon Raiders — [AMD]: Game's graphics all pixelated and blurr, with a bit slow FPS. | Liichi 95 (open)
- [VBug] Splatoon raiders wavy effect on edges like depth of field toggling on and off rythmicaly (open)
- MacOS: Splatoon Raiders unable to swim in ink (closed)
- [Feature Request] dynamic fps splatoon raiders (open)
- Release note: Characters look too dark, there is a green tint, and FPS is lower than in earlier builds.
- Release note: Characters look too dark, there is a green tint, and FPS is lower than in earlier builds. The issue is being investigated.
- Release note: User reports pixelated, blurry graphics and somewhat slow FPS on integrated AMD graphics in Windows 11.
- Release note: Rhythmic wavy effect on edges in the main area, described as depth of field toggling on and off.
- Release note: The reporter says they cannot swim in ink during the tutorial on MacOS.
Compared with Previous Build
Star Fox Reported platform: Linux AppImage (PGO)
| Build | Status | GPU / CPU | FPS | Details |
|---|---|---|---|---|
| Lichii nx2 build 70 (`286117c`) | runs with issues | integrated RDNA2, RADV, reports as `GFX1013` / AMD BC-250 (Oberon APU), 7 cores / 14 threads, AVX2 + FMA | Not provided | Open report |
Lichii nx2 build 70 (`286117c`) report
Statusruns with issues
GPUintegrated RDNA2, RADV, reports as `GFX1013`
CPUAMD BC-250 (Oberon APU), 7 cores / 14 threads, AVX2 + FMA
DriverNot provided
Recorded FPSNot provided
Problems or notes: User reports heavily distorted speech, music, and effects (“robot voice”). Comments clarify that the approximately 0.7032 accepted/copied ratio reflects retries, not audio loss at that point; they discuss possible timebase or host-drain causes without confirming which applies. The user also says build 75 does not reach gameplay, instead hitting a guest Userspace PANIC (`debug_buffer_err_code=40299`) about 29 seconds in and presenting a static black frame at 59.9 FPS.
Related game issues
- [GBug] StarFox: nx2_sysmix accepts a constant 70.32% of mixer output, so audio plays as "robot voice" (open)
- [Crash] StarFox, Device loss occurred! (closed)
- [Crash] Starfox is crashing right before the training mission begins. I got it to pass one time havent been able to get it work again. (closed)
- Release note: On RTX 50-series GPUs, the GPU device can still be lost after a scene change.
- Release note: Gameplay is capped at about 30 fps, even though the game asks for 60.
- Release note: On RTX 50-series GPUs (5070 Ti, 5090), the GPU device can be lost shortly after a scene change.
- Release note: User reports heavily distorted speech, music, and effects (“robot voice”) on build 70. Comments clarify that the approximately 0.7032 accepted/copied ratio reflects retries rather than lost samples; possible causes discussed include emulated time running ahead of wall time or slow host audio draining, but the cause is not confirmed.
- Release note: A user reports the emulator closes about a minute after gameplay begins on Build 75 with an NVIDIA RTX 50 series GPU and Windows 11.
- Release note: User reports crashes before the training mission begins; another user reports crashes during the campaign after skipping training.
Compared with Previous Build
Star Fox Reported platform: unknown
Also listed as: StarFox
| Build | Status | GPU / CPU | FPS | Details |
|---|---|---|---|---|
| build-75 | runs with issues | Not provided / Not provided | 60 FPS | Open report |
| build-70 | runs with issues | Not provided / Not provided | ?–30 FPS | Open report |
| 19.44 (11-4-2026) | runs with issues | NVIDIA RTX 50 series / Not provided | Not provided | Open report |
| Lichii nx2 build 75 (c9ebb5c) | runs with issues | NVIDIA RTX 40 series / Not provided | Not provided | Open report |
| Build - 75 | runs with issues | NVIDIA RTX 50 series / Not provided | Not provided | Open report |
build-75 report
Statusruns with issues
GPUNot provided
CPUNot provided
DriverNot provided
Recorded FPS60 FPS
Problems or notes: On RTX 50-series GPUs, the GPU device can be lost after a scene change.
build-70 report
Statusruns with issues
GPUNot provided
CPUNot provided
DriverNot provided
Recorded FPS?–30 FPS
Problems or notes: Gameplay is capped at about 30 fps despite the game asking for 60. On RTX 50-series GPUs (5070 Ti, 5090), the GPU device can be lost shortly after a scene change.
19.44 (11-4-2026) report
Statusruns with issues
GPUNVIDIA RTX 50 series
CPUNot provided
DriverNot provided
Recorded FPSNot provided
Problems or notes: User reports crashes before the training mission begins; it passed once. A separate user reports crashes during the campaign after skipping training.
Lichii nx2 build 75 (c9ebb5c) report
Statusruns with issues
GPUNVIDIA RTX 40 series
CPUNot provided
DriverNot provided
Recorded FPSNot provided
Problems or notes: User reports repeated Unmapped Write64 errors and a crash when closing the game; audio popping is suspected but not confirmed.
Build - 75 report
Statusruns with issues
GPUNVIDIA RTX 50 series
CPUNot provided
DriverNot provided
Recorded FPSNot provided
Problems or notes: User reports that the emulator closes about a minute after gameplay begins.
Related game issues
- [GBug] StarFox: nx2_sysmix accepts a constant 70.32% of mixer output, so audio plays as "robot voice" (open)
- [Crash] StarFox, Device loss occurred! (closed)
- [GBug] Starfox - Unmapped write64 error spam in console (closed)
- [Crash] Starfox is crashing right before the training mission begins. I got it to pass one time havent been able to get it work again. (closed)
- Release note: On RTX 50-series GPUs, the GPU device can still be lost after a scene change.
- Release note: Gameplay is capped at about 30 fps, even though the game asks for 60.
- Release note: On RTX 50-series GPUs (5070 Ti, 5090), the GPU device can be lost shortly after a scene change.
- Release note: User reports heavily distorted speech, music, and effects (“robot voice”) on build 70. Comments clarify that the approximately 0.7032 accepted/copied ratio reflects retries rather than lost samples; possible causes discussed include emulated time running ahead of wall time or slow host audio draining, but the cause is not confirmed.
- Release note: A user reports the emulator closes about a minute after gameplay begins on Build 75 with an NVIDIA RTX 50 series GPU and Windows 11.
- Release note: Repeated Unmapped Write64 errors while the game is running, possible audio popping, and an emulation crash when closing the game, as reported by a user.
- Release note: User reports crashes before the training mission begins; another user reports crashes during the campaign after skipping training.
Compared with Previous Build
Current: build-75 (1 record); previous: build-70 (1 record).
The Legend of Zelda: Ocarina of Time Reported platform: unknown
Also listed as: Ocarina of Time, Zelda: Ocarina of Time, OoT, Zelda OoT, TLoZ: OoT
| Build | Status | GPU / CPU | FPS | Details |
|---|---|---|---|---|
| build-117 | runs with issues | AMD RX 7000 series; RX 7800 XT (RDNA3) / Not provided | Not provided | Open report |
| build-117 | runs with issues | NVIDIA 4070 Super / AMD 9850x3d | 0–50 FPS | Open report |
build-117 report
Statusruns with issues
GPUAMD RX 7000 series; RX 7800 XT (RDNA3)
CPUNot provided
DriverAMD driver 32.0.32015.7029
Recorded FPSNot provided
Problems or notes: In the Bombchu Bowling Alley, stones along the wall and ovens flash pink, yellow, red, or black by day; the sign shows garbage, noise, and fragments of another image. The graphics look correct at night after leaving and returning. The issue remains in official build-117. The Royal Family's Tomb red line is separately reported fixed by #722.
build-117 report
Statusruns with issues
GPUNVIDIA 4070 Super
CPUAMD 9850x3d
DriverNot provided
Recorded FPS0–50 FPS
Problems or notes: The issue author reports major stuttering and shader building around Hyrule Castle town, making play unworkable. They say visuals looked good and FPS seemed more stable in previous builds. In comments, users report shader loading/building stutter and repeated shader rebuilding when revisiting areas. One commenter says enabling “switch 2 draws with unbuilt pipelines to skip” fixed the stutter but caused graphical and lighting issues. Another says deleting the shader cache and letting it rebuild helped, but performance remained slower than build 93. A commenter reports build 93 had better FPS but worse visuals than build 117.
Related game issues
- Build 117 - Ocarina of Time major stuttering. Constant shader building making it unplayable. (open)
- [GBug] Ocarina of Time on i7-8700K (6c/12t) + RTX 3060: ~23-25 fps, GPU ~35-50%, all 12 logical CPUs ~50% (open)
- [VBug] Ocarina of Time: Missing Foliage/Grass + Missing Textures/Objects on GTX 1070/1080. Mesh/task geometry is not drawn on GPUs without VK_EXT_mesh_shader (missing objects/foliage) [93+] (open)
- [GBug] System language Portuguese (Brazil) doesn't change in-game language for the Remake of The Legend of Zelda: Ocarina of Time (closed)
- [Crash] Ocarina of Time (0400486024DEC000): Linux NVIDIA GPU hang, Xid 109 CTX SWITCH TIMEOUT after ~5 min, every time (Windows recovers from the same stall) (open)
- [Crash] Ocarina of Time Remake crash after intro cinematic (closed)
- [VBug] Ocarina of Time (AMD): red line in Royal Family's Tomb (fixed by #722) and day-only garbage on stones, ovens and sign in the Bombchu Bowling Alley (open)
- [VBug] [AMD] Ocarina of Time: yellow-white haze and green shimmering water from NaN through FMin/FMax/FClamp (closed)
- [GBug] Green hat kid bushes, shrubbery and grass turn dead when approaching too close. (open)
- [VBug] macOS/MoltenVK (Apple M1): Ocarina of Time (0400486024DEC000) shows only black output from boot, 1 FPS, only 2 draws per frame (open)
- [Crash] OoT (0400486024DEC000): 8 compute shaders rejected on RX 6750 GRE, unoptimized table only covers 2 (open)
- [GBug] Ocarina of Time: ~31 FPS in crowded scenes, front GPU thread stalls waiting for back thread (open)
- Higher Resolution than 1x for TLoZ: OoT with DLSS? (open)
- Ocarina of Time on integrated AMD graphics: texture collector stuck in aggressive mode, ~480 images/s created and deleted (open)
- Severe performance issue on Apple M5 / MoltenVK – Ocarina of Time runs at ~8 FPS on build-95 (open)
- [GBug] No Loading build 95 Shadercache (AMD RX 6600) (open)
- [GBug] wall textures are missing in the water temple (open)
- [Crash] Ocarina of Time (0400486024DEC000) freezes when Navi reaches the Kokiri guard on the Deku Tree path, Radeon 890M iGPU, build 95 (open)
- [GBug] Performance degradation/regressions between this release and last release on Zelda Ocarina of time Steam Deck (open)
- [Perf] Ocarina of Time on Ryzen 7 2700X + RTX 3070 Ti (build-95): resolution scale has no effect, CPU-bound measurements and settings A/B (open)
- [Crash] Ocarina of Time freeze, I/O spike to very high value, consume a lot of RAM then crash entire emulator (6700XT) (open)
- Ocarina of Time crashes (unhandled vk::Exception) with VK_ERROR_OUT_OF_DEVICE_MEMORY on an 8 GB RX 9060 XT, after the first cutscene (open)
- [Crash] 100% reproducible crash inside Guardhouse in Hyrule Castle Town (OoT) (open)
- [Crash] Ocarina of Time (0400486024DEC000): freezes in Hyrule Castle Town pot room near the guard (open)
- [GBug] Ocarina of Time 6fps (open)
- [VBug] Ocarina of Time: image washes out white with Switch 2 draws set to Bounded (build 117, RTX 4070 Ti Super) (open)
- [Bug] Steam Controller motion: "Shake!" mapping never detects it, and motion stops after reconnecting (SDL3) (open)
- [GBug] Ocarina of Time (0400486024DEC000): black screen on Adreno 740/Turnip, pipeline builders stuck in driver until memory runs out (open)
- [Perf] OoT on AMD RX 7900 GRE: shader/pipeline hitches; preload max-age + async discard native (open)
- [GBug] Ocarina of Time (0400486024DEC000): coil whine on laptop (open)
- [Crash] Ocarina of Time (0400486024DEC000): unimplemented nx2:vi2 function 201 (open)
- [GBug] Ocarina of Time 0 FPS in Lichii Build 95, but in Build 93 it is playable at 10–25 FPS (closed)
- [GBug] Ocarina of Time (0400486024DEC000): black screen at intro video on build 95, GPU semaphore deadlock; build 93 works (Linux, NVIDIA RTX 3050 Laptop) (closed)
- [GBug] Ocarina of Time: pipelines evicted after ~2.5 min are rebuilt on the GPU thread when re-entering an area (stutter) (open)
- [Crash] Linux RADV, Navi 33 (Steam Machine): GPU reset from mesh draws in OoT, "Illegal opcode in command stream", also MKW on stock build 88 (open)
- [Feature Request] Make pipeline eviction configurable — EDEN_NX2_PRELOAD_ALL_PIPELINES=1 is undone after 9000 frames (open)
- [VBug] Certain blades of grass and pebbles vanish when attacking with sword. (open)
- [VBug] Ocarina of Time – Missing geometry, invisible objects and walls (open)
- [Crash] AMD Crash/AudioDesync (open)
- [Crash] Ocarina of Time on RX 6900 XT (RDNA2): amdvlk64.dll+0x2f1c749 building the VK_KHR_cooperative_matrix HMMA pipelines since #582/#583 (open)
- black screen on linux (open)
- [GBug] Cutscenes running in slow motion(OoT) (open)
- [UIBug] (open)
- [GBug] Ocarina of Time (0400486024DEC000): about half of boots run 20-25% slower; the game's job workers stay awake ~45% longer (open)
- [Crash] Ocarina of Time: AMD RX 7900 XTX driver timeout / device lost at gameplay start, gone with #150 reverted (open)
- [GBug] OoT on RTX 4060 Laptop (45 W): build-95 holds draws for unbuilt pipelines; Frizti host pacer misreads refresh with mixed-refresh monitors (open)
- [Crash] Ocarina of Time hangs on "Loading...", emulator crashes about 10 seconds later. (open)
- [GBug] Game remains 20 fps with music glitches on macOS (open)
- [GBug] Ocarina of Time (0400486024DEC000) on Ryzen 5 5500 + RX 7600: test notes, and movie audio voices that get paused (open)
- Ocarina of Time (Switch 2) gets stuck at "Building 9 shaders" on AMD RX 6750 XT (open)
- [VBug] Ocarina of time Black square lines all over hyrule field (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] Zelda: Ocarina of Time (0400486024DEC000): the audio plays a different part of the stream than the picture (open)
- [VBug] [AMD RX 9070 XT] Build 95 – White sky during daytime and black distant terrain/water at night in Zelda OoT (open)
- [VBug] Zelda Ocarina Of Time white sky (open)
- [VBug] Ocarina of Time: distant Kokiri Forest canopy renders neon green in the main scene pass (RX 7900 XTX) (open)
- [AMD] Ocarina of Time: cyan/magenta line on mountain ridges - FS with no color output writes garbage (fix included) (closed)
- [VBug] Ocarina of Time (0400486024DEC000): a far-distance draw in pass #72 writes NaNs on AMD RX 9070 XT (rainbow blocks on the horizon) (closed)
- [Crash] Linux/RADV (RX 9070 XT): invalid SPIR-V fragment shader (depth image u32 sampled as f32) segfaults in VkPipelineBuild, Ocarina of Time (closed)
- [GBug] Ocarina of Time (0400486024DEC000): intro freezes for 6 to 18 minutes on AMD while the driver optimizes two compute shaders (closed)
- [VBug] OoT (0400486024DEC000): textures flicker with Low GPU accuracy + EDEN_NX2_SPLIT=2 on AMD RX 9070 XT; High fixes it but turns the split off (~9 fps) (closed)
- [UIBug] Extract NUP fails on paths over 260 chars: longPathAware in yuzu.manifest uses undeclared ws2 prefix (open)
- [VBug] Ocarina of Time is a black screen with the title theme music, and I can't press any buttons (open)
- [Crash] Ocarina of Time on RX 6900 XT (RDNA2, driver 2.0.353): amdvlk64.dll+0xaff2e7 in more shaders than #273's list; building pipelines unoptimized avoids it (open)
- Snapdragon 8 elite gen 4 (open)
- [VBug] black screen amd (closed)
- [VBug] [AMD RX 9070 XT] Ocarina of Time (0400486024DEC000): ~20 FPS, light/haze artifacts, audio desync (open)
- [GBug] Ocarina of Time on RADV (RX 9070 XT): 28-35 fps, 35 ms frame with no saturated thread (translation/sync bound) (open)
- [Visual] Mesh-shader draws are dropped silently on GPUs without VK_EXT_mesh_shader (GTX 1070, Ocarina of Time) (closed)
- [Crash] RX9070XT, SteamOS (closed)
- [Regression][Linux RADV] Zelda Ocarina of Time black screen in build 95 (works in 93); native MME macro RAM errors (closed)
- [AMD RX 9070 XT] Tela preta com interface visível e tempo limite do driver da GPU (Build 88) (open)
- [VBug] Flashing textures with GPU mode: FAST (closed)
- [GBug] Ocarina of Time: Multi-second single-pipeline GPU-thread re-translation stutters & 579k OnCPURead traps with Reactive Flushing (open)
- [VBug] Ocarina of Time (0400486024DEC000): Blinding white bloom/flare streak in Kakariko Village (NVIDIA) (open)
- [GBug] Textures not working properly, slow frame rate and shield glitch in The Legend of Zelda Ocarina of Time remake (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)
- [GBug] Lichii Build 93 – Significant AMD Progress, but Lighting Flickering and Performance Issues Remain (open)
- [AMD RX 9070 XT] Rainbow-colored graphical artifacts along mountain edges in Zelda OoT (Build 93) (open)
- [VBug] (open)
- [VBug] Ocarina of Time: holes in the distant mountains of Hyrule Field show the sky through them (open)
- [VBug] Doesn't work for AMD GPU - 9070 XT (The Legend of Boy in Green Hat) (closed)
- [Build] Tree does not compile with clang-cl on Windows (NOMINMAX and FARPROC casts) (closed)
- [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)
- [VBug] Ocarina of Time: AV1 cutscenes render solid green on AMD/RADV (audio and subtitles OK) (closed)
- [GBug] Zelda OOTR Won't Load (closed)
- [Crash] chuppatricky-amd-testbuild v13: amdvlk64.dll access violation (0xc0000005) during shader compile on RX 6700 XT (open)
- [VBug] Build 93 finaly has no major visual errors but has poor performance 9070xt (open)
- [Crash] RADEON RX 9070 crashes every single run. (open)
- [Crash] Crash replicated multiple times when trying to enter Hyrule Market - The Legend of Zelda: Ocarina of Time (open)
- [Crash] (open)
- [GBug] Ocarina of Time / Audio Desync (open)
- [Crash] chuppatricky-amd-testbuild v13: amdvlk64.dll access violation (0xc0000005) during shader compile on RX 6700 XT (closed)
- [Crash] Ocarina of Time Crashes on macOS on game loading (after intro video or selecting a saved file) (open)
- [Crash] AMD Ocarina of time Doesn't Start (open)
- [GBug] OoT (0400486024DEC000): the same ~60 cached graphics pipelines are rebuilt on the GPU thread every boot (closed)
- [GBug] OOT Remake Intel Arc 7 Cores - Only 1 Fps in the main menu and first cutscene (open)
- [Crash] Lichii crashes at OOT launch (open)
- [VBug] Ocarina of Time: dialogue box panel and hint strip flicker with EDEN_NX2_FRAMES_AHEAD=1, gone with =0 (closed)
- RX6600: video_core\renderer_vulkan\vk_pipeline_cache (open)
- [Crash] Ocarina of Time NUP remains on Launching in build 88 (open)
- [VBug] OoT Slows when booting. (closed)
- [Crash] infinite launch screen with legend of zelda ocarina of time (closed)
- [GBug] overall zelda ocarina of time experience on win11 rtx 2060 3700x 16gb ram system and visual glitches (open)
- [VBug] OOT eventually turns into hard black screen outside of captions in handheld mode, renders as though looking through vaseline in docked mode (open)
- [GBug] Ocarina of Time (0400486024DEC000): gameplay settles at ~29 fps, CPU-bound on two cores (build 75) (open)
- Legend of Zelda Ocarina of time (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)
- [GBug] Ocarina of Time: black 3D gameplay screen; HUD remains visible (Lichii build 75) (closed)
- Ocarina of Time: frame dump findings (overlay source, bloom/exposure, missing vegetation, rejected gathers) (open)
- [Bug] Windows build-83 can hang on Closing software after OoT gameplay (open)
- Ocarina of Time (0400486024DEC000) build-75: macro parameter desync + unknown texture format 100, broken lighting/bloom and corrupted textures (open)
- [GBug] (closed)
- Release note: White streaks or trails at night, including around Navi, fireflies, and smoke.
- Release note: With DLSS on, Navi, fireflies, and smoke can leave trails at night. A fix is being tested.
- Release note: AMD Radeon RX 6000 series and older on Windows crash while building shaders after boot. The release says this is fixed in build 117; RX 7000/9000 and NVIDIA are not affected.
- Release note: AMD black foliage and haze.
- Release note: HUD flicker.
- Release note: Cutscene audio drift.
- Release note: First-launch shader stall on Linux.
- Release note: An NVIDIA device-lost crash was reported on build 93; the release says it is awaiting retest on this build.
- 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 build 117, users report severe stuttering and low or variable FPS while shaders are building; comments also describe shader rebuilding when revisiting areas.
- Release note: The suggested setting “switch 2 draws with unbuilt pipelines to skip” reportedly reduced stuttering, but introduced graphical and lighting issues.
- Release note: A user reports that shader-cache rebuilding may contribute to stuttering and that deleting the cache and letting it rebuild helped, though performance was still slower than build 93.
- Release note: A user reports approximately 23–25 FPS in Kokiri Forest on Fritchii v4, with CPU and GPU not saturated.
- Release note: Foliage, leaves, walls, doors, and other geometry can be missing on GPUs without VK_EXT_mesh_shader because task/mesh shader draws are skipped.
- Release note: A draft compute-based task/mesh shader fallback rendered some foliage on GTX 1070 but produced flickering geometry and still missed canopies, grass, and house walls.
- Release note: On Linux with NVIDIA GPUs, gameplay can lead to a GPU hang after roughly five minutes. Reports include Xid 109 CTX SWITCH TIMEOUT or a GPU stuck at 100% utilization without an Xid.
- Release note: On the reported NVIDIA systems using driver 581.29, the game crashes with Vulkan device loss during shader and pipeline compilation after the intro cinematic; reports include repeated Unmapped Device ReadBlock errors and Windows nvlddmkm Event ID 153.
- Release note: Day-only garbage graphics in the Bombchu Bowling Alley: stones and ovens flash pink, yellow, red, or black, and the sign displays garbage, noise, and fragments of another image. It looks correct at night after leaving and returning, and was still present in build-117.
- Release note: After outdoor play, the sky becomes flat yellow-white and water shimmers green until reboot, due to NaNs spreading through bloom. The report says the NaNs probably originate from fog/foliage probe reads beyond the 64 MiB graphics table-pointer cap.
- Release note: Foliage and vegetation near the player may turn into dead-looking variants or lose leaves up close, including hedges and plants in Hyrule Castle; reports also mention trees, Kokiri Forest bushes, Castle Town hedges, and Hyrule Field grass. One user describes the behavior as an inverted LOD.
- Release note: On macOS/MoltenVK with an Apple M1, the Switch 2 NSO version boots and plays audio but presents a black image from startup, with approximately 1 FPS and occasional red/green block artifacts.
- Release note: On AMD GPUs, Ocarina of Time's compute shaders can fail compilation with VK_ERROR_OUT_OF_HOST_MEMORY or cause the AMD driver to crash. The issue report describes missing intro video and an eventual process crash; a later user reports an access violation inside amdvlk64.dll.
- Release note: OpenGL is reported not to work for this game because GLSL task and mesh programs are not implemented, resulting in repeated errors and an emulator hang.
- Release note: Rejecting shader hashes before translation skips their dispatches and can result in missing output or a black screen; a user reports the environment switch did not affect the tested Vulkan compute-pipeline path.
- Release note: Performance slows in crowded or busy areas, with front/back GPU-thread synchronization drains and waits; short freezes while attacking are also reported.
- Release note: Shader compilation can cause freezes of about 3 seconds with each step, according to a user report.
- Release note: On integrated AMD graphics, device-memory thresholds can keep the texture cache collector in aggressive mode even though deleting all images cannot reduce total usage below the threshold. This causes extensive image churn and GPU waits during gameplay.
- Release note: Severe performance, around 8 FPS (approximately 123 ms frame time), on macOS with Apple M5 using Vulkan / MoltenVK at 1x resolution; the report also says MoltenVK fallback warnings occur. A commenter reports the same issue on Mac M4.
- Release note: On build 117, the game shows a black screen while background music plays and does not load, reported with an AMD RX 6000 series or older GPU on Windows 11.
- Release note: A commenter reports white flashes or missing textures on Windows 11 with some RTX and AMD graphics cards, and another reports missing textures in the Deku Tree after loading a save.
- Release note: On the reported Radeon 890M system, the game freezes during early Kokiri Forest gameplay, accompanied by Unmapped Device ReadBlock errors; a later report on build 117 also describes pipeline-building stalls and a hard freeze.
- Release note: On Linux using a Steam Deck, the reporter describes a main-menu performance regression in build 117, from 60 FPS with some drops on the prior legacy build to 10 FPS, with audio out of sync. The non-PGO version reportedly had the same problem.
- Release note: Shader stutter and multi-second freezes while shaders are being built, including during first visits.
- Release note: Gameplay performance is CPU-bound on the reported Ryzen 7 2700X; resolution scale changes and switching to Handheld did not improve performance.
- Release note: User reports random freezes after 5–15 minutes of play on Linux with an AMD RX 6000 series or older GPU, followed by I/O spikes up to 6GB/s, rising RAM use, and an out-of-memory emulator crash.
- Release note: Crashes during play with VK_ERROR_OUT_OF_DEVICE_MEMORY on 8 GB AMD GPUs; reports describe unhandled Vulkan exceptions.
- Release note: A user reports a reproducible crash to desktop within a few seconds of entering the Guardhouse in Hyrule Castle Town.
- Release note: The game freezes or crashes in the Hyrule Castle Town guard house when moving deeper into the room, talking to the guard, or looking toward the windowed wall while panning the camera.
- Release note: On Frizti v3, performance in the guard house remains low after the freeze is addressed, with about 20 fps reported as the floor after additional texture-cache changes.
- Release note: A user reports performance of up to 6 FPS and a crash at Kokiri Tree after removing the pipeline cache.
- Release note: With Switch 2 draws with unbuilt pipelines set to Bounded and an 8 ms wait, the image washed out to white and orange and parts of the scene rendered as large flat polygons while pipelines were building.
- Release note: With a Steam Controller (2026) connected through its wireless dongle, motion mapping via Configure → Controls does not detect shaking, and gyro/accelerometer input stops after the controller reconnects or after a few seconds with Steam running.
- Release note: On an AYN Thor with Adreno 740 and Turnip, large native compute shaders cause pipeline compilation to consume substantial memory and pin Vulkan pipeline-builder threads; reports include black output, GPU device loss, or out-of-memory termination.
- Release note: On ARM hosts using NCE, the built-in Dynamic FPS by Dark and Max Resolution patches together were reported to trigger an early SIGILL on builds 88 and 94.
- Release note: Long shader and pipeline hitches while exploring; the user also reports texture flashes or freezes when new pipelines compile.
- Release note: A user reports constant CPU-side coil whine while playing on a laptop.
- Release note: Crashes during boot at an unimplemented nx2:vi2 function 201; the report also mentions a later unimplemented IGeneralService function 101 assert.
- Release note: On Build 95, the user reports sound from the intro but no video and 0 FPS on Linux.
- Release note: A commenter says performance is worse on Build 116 than on Build 93.
- Release note: Build 95 hangs on a black screen at the intro video on reported Linux/NVIDIA systems, with GPU macro failures and semaphore waits; build 93 works in the reports.
- Release note: A user reports heavy stutter when re-entering areas after graphics pipelines are evicted and rebuilt. The report attributes eviction to pipelines being unused for 9000 frames.
- Release note: A user reports frequent shader-building notifications and stutter, including when revisiting areas, on nx2-build-117. Their single capture showed substantial runtime pipeline creation but no eviction entries; persistence after a second launch is undetermined.
- Release note: On Linux RADV systems, user reports describe GPU resets or device loss during mesh draws, sometimes with an illegal opcode in the command stream. EDEN_NX2_NO_MESH=1 avoided resets in several tests but caused missing terrain, plants, or other geometry.
- Release note: With EDEN_NX2_PRELOAD_ALL_PIPELINES=1, pipelines are evicted after 9000 frames, causing runtime builds, long held draws, and a reported freeze.
- Release note: Grass and pebbles disappear or flicker during sword attacks; disabling persistent pipeline cache was reported to make grass disappear permanently, while enabling it left flickering.
- Release note: Walls, environmental geometry, and some interactive objects are invisible; occasional stuttering is also reported.
- Release note: A commenter reports invisible push blocks.
- Release note: A commenter reports that objects and doors do not appear.
- Release note: Issue reports describe audio desynchronization and crashes or full-system freezes during early cutscenes on AMD graphics cards.
- Release note: On AMD RDNA2 GPUs, the 16x16x16 VK_KHR_cooperative_matrix HMMA pipeline path can cause an access violation in amdvlk64.dll during shader or pipeline compilation, typically 30–90 seconds after game startup.
- Release note: On Linux, a black screen can occur with the Native MME error "instruction outside uploaded RAM". One report says shaders load and menu music is audible; another says the game opens, reaches 0 FPS, and freezes.
- Release note: Cutscenes play in slow motion, lagging behind audio; the report describes them as locked to 49fps with 99% GPU usage.
- Release note: The same slow-motion cutscene problem is reported.
- Release note: The same slow-motion cutscene problem is reported.
- Release note: After the Kaepora Gaebora cutscene near Hyrule Castle, the scene appears empty and foggy and Link repeatedly falls through the world and voids out, preventing progression.
- Release note: When fastmem could not be created, guest code ran about 1.4x slower; Kokiri Forest ran at 22.2–26.6 FPS rather than 28.5–33.8 FPS. The report attributes the slow boots to failure to allocate 14336 MiB of backing memory.
- Release note: On AMD Windows proprietary drivers, older builds can lose the GPU device when gameplay or a save starts; build-83 and build-88 reports include this problem.
- Release note: On AMD RADV Mesa 26.2.4, task/mesh shader use can hang the GPU and cause device loss during 3D gameplay.
- Release note: On build-95, the user reports draws held while unbuilt pipelines are being built, causing multi-second stalls, even with async shaders enabled.
- Release note: The user reports that a fresh build-95 config starts with slow defaults, including High GPU accuracy, asynchronous shaders off, async presentation off, Handheld mode, 4 GB memory layout, and CPU NVDEC; the game ran at 10–15 fps with stalls up to 8.9 s and blurry/pixelated Handheld resolution.
- Release note: Users report failure to start, black screens with 0 FPS, or emulator crashes in builds 88–95, including a build-95 Linux report with an unhandled SIGSEGV and null-pointer dereference. The comments caution that the reports may have different causes.
- Release note: A user reports a black screen and around 2 FPS on macOS with build 95 on an Apple M1 Pro; shader compilation eventually finishes, but no title screen or gameplay is visible.
- Release note: During movies, including the title-screen background, the six movie audio voices can pause while the picture continues, resulting in late or silent audio. The issue varied between sessions and was also reported on builds without the movie-sync patch.
- Release note: On an RX 6650 XT setup, asynchronous shader compilation on was associated with a black screen or a freeze while building shaders; asynchronous shader compilation off allowed the game to load and play on that setup.
- Release note: A commenter reports a freeze with background music on an AMD Ryzen 5 5500U with Radeon Graphics, regardless of the asynchronous shader compilation toggle.
- Release note: Black square lines appear across Hyrule Field and disappear when approached.
- Release note: Skipping or batching Preflushable buffer downloads can cause the scene to be overexposed because guest reads may occur before downloaded GPU-written data is available. The issue also reports potentially stale exposure data with the no-preflush experiment.
- Release note: A commenter reports that Kokiri Forest and the Deku Tree can run much more slowly after watching the New Game intro than when loading a save directly; the commenter reports a storage-write extent branch improved the intro-first result.
- Release note: A commenter reports that the per-fence download cost remains and describes an unmerged pull request that limits GPU-written marking to shader store extents.
- Release note: Audio plays from a different point in the game than the picture, including audio leading video in intro and other scenes. A bot comment says pull request #251 targets slow AV1 intro movies by skipping late frames, but it is not merged.
- Release note: On AMD Radeon RX 9070 XT with Vulkan, the daytime sky and distant scenery can appear white or washed out, and distant terrain and water can appear black at night.
- Release note: A user reports crashing while loading on an RX 9070 XT, even after copying another user's settings; the game and setup details are not established in that comment.
- Release note: On AMD, the sky appears white and fog or distant scenery is overbright. A bot comment attributes this to far-field light probe reads being cut off at 64 MiB and shader NaN handling.
- Release note: On an AMD RX 7900 XTX, the distant Kokiri Forest canopy renders neon green and cyan.
- Release note: On AMD Radeon RX 9070 XT with driver 2.0.416, a dotted cyan/magenta line appeared along mountain and sky silhouettes in Hyrule Field.
- Release note: Coloured blocks or a magenta line along the Hyrule Field mountain ridge on AMD GPUs; the original report described NaNs in the scene target that bloom spread into a coloured band.
- Release note: Distant mountains remain overexposed with a white glow after the coloured blocks are removed; the source identifies this as a separate bloom/exposure issue.
- Release note: On Linux with AMD RX 9000-series graphics using RADV, an invalid SPIR-V fragment shader can cause a segfault during Vulkan graphics-pipeline construction during gameplay.
- Release note: On AMD's proprietary Windows Vulkan driver, the intro could freeze while two compute shaders were optimized, taking 6–18 minutes; long graphics-pipeline builds can also cause substantial in-game stalls.
- Release note: On earlier builds, small details such as leaves, pebbles, and grass flickered or appeared black with Low GPU accuracy and the split GPU thread enabled.
- Release note: On Windows 11, extracting a NUP to a path longer than 260 characters fails even when LongPathsEnabled is set. The issue reports a malformed longPathAware manifest entry as the probable cause.
- Release note: A user reports a black screen with title music and unresponsive controls until shaders loaded; after entering gameplay, they reported severe glitches and lag, freezes lasting about 20 seconds during shader building, and a steady 18 FPS.
- Release note: On an RX 6900 XT with AMD proprietary driver 2.0.353, the driver crashes while compiling shaders during gameplay; rejecting one shader hash does not prevent a subsequent crash at the same driver fault offset. The reject check may not help when the shader is already in the disk cache.
- Release note: A user reports the frame rate drops to 2.5 FPS when shader loading begins, after the initial cutscene runs at 50–60 FPS.
- Release note: On build 95, Linux and SteamOS users report black-screen hangs with audio still playing; comments associate the issue with repeated `Native MME (split front) failed` errors.
- Release note: A commenter reports reaching the main menu by starting with GPU accuracy set to Accurate, but reports audio issues and possible recurrence after changing settings.
- Release note: On Windows 11 with an AMD RX 9000 series GPU and proprietary driver 2.0.416, gameplay is around 20 FPS with large variance, light/haze artifacts, and desynchronized, stuttering audio.
- Release note: On Linux with an AMD Radeon RX 6700 XT, gameplay is around 20 FPS with audio crackling below full speed. On Windows with the same PC, only subtitles rendered.
- Release note: With Mesa 25.0.7 and kernel 6.12.115, gameplay was followed after about nine minutes by a Vulkan device loss and an unrecovered display; this was not seen again after updating Mesa and the kernel.
- Release note: The official PGO artifact of build-80 / nx2-latest crashed in dynarmic with Unhandled SIGSEGV after 2-10 minutes on the reporting machine; another report found a PGO AppImage produced audio but no video output.
- Release note: White flashes were reported before PR #345 in the Deku Tree interior; the sky/lighting colour result from a separate misaligned 64/128-bit SSBO split fix was not verified.
- Release note: In a Windows AMD-driver follow-up on Frizti v3, performance was about 20 fps in a busy view and about 60 fps looking at the floor; the reporter said keeping float16 on improved the busy-view result from about 20 to 24-25 fps.
- Release note: On a GPU without VK_EXT_mesh_shader, mesh-shader draws may be skipped, resulting in missing scene geometry. The reported log labels skipped draws as "no pipeline" and caps the warning entries at 64.
- Release note: On Linux, loading into gameplay initially caused a system crash. With EDEN_NX2_NO_MESH=1, gameplay was reached with missing geometry and shading issues.
- Release note: On Linux with AMD RADV, the game stalls at a black screen at 0 FPS on build 95; the report describes repeated native MME macro execution failures.
- Release note: Black or missing 3D rendering; some reports also describe driver timeouts or crashes. Reports include AMD GPUs and one Nvidia RTX 4070 SUPER.
- Release note: One user reports FPS between 15 and 30 with constant drops in v93.
- Release note: A commenter reports white flickering throughout the 3D world in the Frizti fork.
- Release note: User reports describe multi-second GPU-thread shader translation stalls, gameplay stuttering, and growing synchronous OnCPURead waits during long sessions.
- Release note: Blinding white bloom/flare streak in Kakariko Village; a commenter reports it also occurs in the well, later areas, and frozen Zora's domain.
- Release note: User reports textures not working properly, slow frame rate, and a shield glitch.
- Release note: On Linux Mint with Intel(R) HD Graphics 620, Vulkan and OpenGL GLSL show audio without video; the introductory sequence eventually freezes when using OpenGL GLSL.
- Release note: Severe lighting flickering, excessively bright or visually corrupted lighting effects, performance slowdowns, audio desynchronization during cinematics, and lengthy initial shader compilation.
- Release note: Eglantine crashes at the end of the intro with VK_ERROR_DEVICE_LOST on an Apple Silicon Mac, according to a user comment.
- Release note: Severe rainbow-colored graphical artifacts along mountain edges in Kakariko Village on an AMD Radeon RX 9070 XT.
- Release note: User reports intermittent audio loss, brief frame-rate drops, an excessively bright missing sky, and a missing map.
- Release note: User reported sky-coloured holes in distant mountains of Hyrule Field on nx2 a7a28175 (same content as build-93) + local patches; a later user comment says they could no longer reproduce them on a newer local build.
- Release note: A commenter reports subsequent boots hang at Loading Shaders 25 / 27 with use_disk_shader_cache = true.
- Release note: A commenter reports a black screen after the intro on AMD, attributed in the comment to rejection of the game's 1080p upscaler shader.
- Release note: A commenter reports that 3D rendering remains black on AMD, while the start menu and 2D UI render.
- Release note: A user reported that local ClangCL and MSVC builds stalled with no frames, while the compared build-75 release presented frames. The cause was not determined; a maintainer noted the report came from an old commit and may no longer happen.
- Release note: On the reported Windows 11 system with a Radeon RX 9070, the world rendered almost entirely black after entering gameplay, with only lit areas and some white shapes visible; multi-second stalls were also reported during pipeline building and ASTC decodes.
- Release note: On nx2-build-75, AV1 video streams fail to decode and the game remains on a black screen despite booting and presenting frames.
- Release note: On AMD/RADV under Linux, AV1 intro-cutscene video renders as a solid green area while audio and subtitles work.
- Release note: On Windows with AMD hardware, the emulator hangs indefinitely when the AV1 intro cutscene starts; the video layer is black while audio and subtitles work.
- Release note: User reports include indefinite launching, white graphics, and a black screen in handheld mode or past the title screen. A separate report says it boots past the intro FMV in docked mode.
- Release note: On Windows 11 with an AMD Radeon RX 6700 XT and AMD Software (Adrenalin) 26.10.2, Lichii closes during shader rebuilding with an access violation in amdvlk64.dll.
- 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: AMD graphics-driver TDR or crash and a black screen when the game transitions from the introductory scene to gameplay; some users also report crashes while loading a save and visual bugs during gameplay.
- Release note: Users report mixed results on Build 93: an AMD GPU crash without the environment variable, successful play through Kokiri Forest, and persistent visual bugs.
- Release note: The emulator closes when loading Hyrule Market after the user exits Kokiri Forest and enters Hyrule Castle.
- 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: Audio and video become desynchronized on the title screen, intro, and initial dream cutscene; a commenter reports slow-motion live-rendered video and an audio lead of approximately 3 seconds.
- Release note: On an AMD Radeon RX 6700 XT with AMD Software (Adrenalin) 26.10.2, Lichii closes during the first shader rebuild after about 9-10 minutes; Event Viewer reports an access violation in amdvlk64.dll.
- Release note: User reports freezing while loading a game and a subsequent emulator crash on macOS; in Build 93, pressing A on a controller reportedly does nothing when attempting to return to the title screen.
- Release note: AMD GPUs may show a black screen or crash the graphics driver after loading, the intro, or a cutscene.
- Release note: On a local nx2 build, white or yellow haze outdoors and black water or foliage after an area change were reported as remaining graphics issues.
- Release note: On build-83, repeated graphics-pipeline builds on the GPU thread across boots cause a visible gameplay hitch.
- Release note: A user reported repeated GPU-thread pipeline builds and tessellation-related warnings in one Linux session; recurrence across launches was not confirmed.
- Release note: Users report very low frame rates in the main menu and opening cutscene on Intel Arc GPUs; a Linux user also reports a prolonged shader stall on first boot and a frozen Kokiri intro cutscene.
- Release note: A user reports a crash when launching the game; the log reports failed backing-memory and fallback-buffer allocation.
- Release note: Dialogue box background panel and hint strip flicker in about half of presented frames with EDEN_NX2_FRAMES_AHEAD=1; other HUD elements may also flicker.
- Release note: User reports a permanent Vulkan startup freeze during shader compilation on AMD RX 6600-series hardware, at “Building: 13 shader(s)” with 0 FPS; a second user reports it on an RX 6600M.
- Release note: A user reports that the game remains on the Launching screen and does not start in nx2 build 88 on Windows 11.
- Release note: The game runs slowly when booting.
- Release note: A user reported an infinite startup launch loop when booting the .NUP version.
- Release note: User reports fluctuating performance of approximately 10–30 FPS, bushes disappearing when approached or changing shape, and intermittent lighting and shading glitches.
- Release note: Black screens during the introductory cinematic, GDT sequence, or gameplay; reports include intermittent black flashes and audio playing ahead of video.
- Release note: Docked mode may show a black screen except for captions or HUD, while handheld mode may appear excessively bright, low resolution, or vaseline-like.
- Release note: A commenter says many crashes with AMD graphics cards are related to mesh shaders.
- Release note: In build 75 on Windows x86_64, gameplay settles at 28–29 FPS while menus and loading screens run at 53–59 FPS; the reporter characterizes the gameplay performance as CPU-bound.
- Release note: Handheld mode gives a black 3D screen; Docked mode renders. A user also reports flicker/line artifacts at 2X resolution.
- Release note: A user reports frequent hangs or stalls in build 83; the trigger and duration were not isolated.
- Release note: A user reports new-area shader hitches in build88.
- Release note: The user reports audio delays after scenes followed by a black screen and emulator crash on Windows 11 with AMD graphics. A commenter reports a similar crash on Linux with AMD graphics.
- Release note: A user reports a crash when opening the game on Linux with an AMD Radeon AI PRO R9700 (9070XT).
- Release note: On an AMD Radeon RX 9070 XT, the logo, text, and UI are visible while the 3D environment remains black; audio continues and AMD driver timeouts or crashes sometimes occur.
- Release note: A commenter reports AMD graphics-card crashes related to mesh shaders.
- Release note: A commenter reports that the game looks too bright when using the Aubepine build, making it barely playable.
- Release note: Black 3D gameplay scene with HUD or menus still visible; some reports also mention stuttering, audio problems, flickering shadows, or missing tree leaves.
- Release note: The Deku Tree exterior cutscene can render black except for a small circle around Navi, even when the title screen, intro, and earlier cinematics render correctly. A later report also observed a deterministic AMD driver crash while building graphics pipelines in the same scene.
- Release note: A half-resolution layer can produce dark blotches and translucent patches over Link, terrain, and other objects. User reports traced the issue to a depth image being cleared after a depth copy; one report says PR #185 addresses the ordering, but reports do not establish a confirmed released fix.
- Release note: River water may be dark or lack visible lit contribution, and one user reported flickering that depends on the sun's position relative to the camera.
- Release note: Outdoor scenes may remain severely white/yellow and washed out on clean upstream nx2, despite substantial improvements to vegetation and atmosphere.
- Release note: Texture-format and texture-index assertions were reported during gameplay; a separate report associated a period of such assertions with terrain and subtitle flickering, without establishing causation.
- 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: On build-75, user reports over-bright bloom/glow, overly dense fog, incorrect lighting, and some textures decoded as garbage; logs include macro-parameter assertions and an unknown texture format 100.
- Release note: The 3D gameplay scene is black while HUD elements remain visible; menus and item preview can render correctly.
Compared with Previous Build
Current: build-117 (2 records); previous: build-116 (0 records).
Showing 131–140 of 308 reports
Known issues from Lichii sources
Known Game Issues
The Legend of Zelda: Ocarina of Time
On AMD RDNA2 GPUs, the 16x16x16 VK_KHR_cooperative_matrix HMMA pipeline path can cause an access violation in amdvlk64.dll during shader or pipeline compilation, typically 30–90 seconds after game startup.
Recorded fix: The source reports that EDEN_NX2_NO_COOP_MATRIX=1 avoids the crash. A later comment states that merged PR #657 fixes it.
Other / not listed
The underground fairy fountain has no environment.
Recorded fix: A commenter says the issue is caused by a dump missing textures and advises using a NUP dumped without missing textures.
Zelda: Ocarina of Time
On Linux, a black screen can occur with the Native MME error "instruction outside uploaded RAM". One report says shaders load and menu music is audible; another says the game opens, reaches 0 FPS, and freezes.
Recorded fix: A comment reports that setting DMA accuracy to Safe works as a workaround. Another comment attributes the error to a GCC 13 miscompile and says a fix was merged but was not yet in a published release.
OoT
Cutscenes play in slow motion, lagging behind audio; the report describes them as locked to 49fps with 99% GPU usage.
OoT
The same slow-motion cutscene problem is reported.
OoT
The same slow-motion cutscene problem is reported.
The Legend of Zelda: Ocarina of Time
After the Kaepora Gaebora cutscene near Hyrule Castle, the scene appears empty and foggy and Link repeatedly falls through the world and voids out, preventing progression.
Mario Kart World
User reports 17–23.8 FPS in 3D races on build-95, compared with 40.0–54.1 FPS on build-93 under the same reported test conditions.
Other / not listed
Black screen when starting in build 95 on Linux; a commenter reports black screen with music. The commenter says build 93 loads normally on their system.
Showing 111–120 of 361 issues
Aktuelle Release-Hinweise
Kompatibilitätsänderungen in den neuesten Builds
Build build-117 · Ocarina of Time
Fixed a crash during shader building on Windows drivers for RX 6000 (RDNA2), RX 5000 (RDNA1), Vega, and Polaris cards. The faster matrix path now runs only on RDNA3 and newer.
Build build-116 · Zelda: Ocarina of Time
Ocarina of Time is described as very stable; foliage and Hyrule Field grass rendering are fixed, and many users get 60+ fps.
Build build-116 · Zelda: Ocarina of Time
NVIDIA DLSS Super Resolution can replace the game's own upscaler on RTX cards; the setting is experimental.
Build build-116 · Zelda: Ocarina of Time
A new option turns off the game's sharpening anti-aliasing; the default Game setting behaves as before, and DLSS takes priority if both are enabled.
Build build-116 · Mario Tennis Fever
The game runs fully at 60 fps, and texture glitches are fixed.
Den passenden Build finden
Welchen Build soll ich verwenden?
Wähle oben ein Spiel aus, um zu sehen, welche getesteten Builds zum Download verfügbar sind. Bis dahin kannst du den neuesten veröffentlichten Build verwenden und seine Release-Hinweise lesen.
Probiere den neuesten verfügbaren Release aus: build-117. Behalte beim Testen einen funktionierenden Build, zu dem du zurückkehren kannst.
Fragen zur Kompatibilität
Häufige Fragen zur Spielekompatibilität
Wie teile ich ein Spiel mit diesen Filtern?
Setze die Filter für Spiel, Status, GPU und Build und kopiere anschließend die Seitenadresse. Ein direkter Link zum Spiel öffnet dessen Berichtskarte.
Was kann ich bei einem schwarzen Bildschirm versuchen?
Prüfe in anderen Berichten, ob das Spiel bis zum Menü oder ins Spielgeschehen gelangt. Notiere Treiber und Renderer und suche nach dem Spiel oder dem Fehler in der Anleitung zur Fehlerbehebung.
Warum kann dieselbe GPU unterschiedliche Ergebnisse liefern?
Treiberversion, Grafikeinstellungen, CPU-Auslastung und die getestete Spielszene können das Ergebnis beeinflussen. Vergleiche diese Details, bevor du deine Konfiguration änderst.
Wo kann ich ein fehlendes Testergebnis melden?
Nutze den offiziellen Issue-Tracker von Lichii. Nenne das Spiel, den Build-Tag, Hardware, Treiber, Einstellungen und die Schritte, mit denen sich deine Beobachtung reproduzieren lässt.