Game compatibility
Got a game in mind? Find out how it is running in Lichii, spot the rough edges, and pick a build worth trying.
Find a game
58 game/environment entries and 114 Lichii reports are in the current data.
Missing a game? A blank result means no Lichii report is listed yet, rather than a failed test.
Use the platform label to distinguish different versions of a game.
Status meanings: Unknown means no conclusion; Not booting means the game did not start; Boots means startup only; Runs with issues means gameplay had problems; Playable means the tester was able to keep playing.
Compatibility results
Recorded performance
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.
| Build | Status | GPU / CPU | FPS | Details |
|---|---|---|---|---|
| nx2-20261031 | boots | Not provided / Not provided | Not provided | Open report |
Problems or notes: Completed a 180-second GUI check; long-term memory stability and broader game compatibility remain unverified.
| Build | Status | GPU / CPU | FPS | Details |
|---|---|---|---|---|
| build-70 | runs with issues | NVIDIA RTX 40 series / Not provided | Not provided | Open report |
| build 70 (286117c) | runs with issues | AMD RX 6000 series or older / Not provided | 57 FPS | Open report |
Problems or notes: Picture is covered with weird artifacts especially on shadows.
Problems or notes: With Vulkan, 1x, handheld, GPU Fast, VRAM Aggressive, Nearest, AA off, and no frame generation, gameplay runs at ~57 fps before the process aborts after 133.8 seconds with 0xC0000409 at lichii.exe+0x2ecd3bd. On the MinGW PGO zip of the same build, it reportedly aborts on the intro screen seconds in, at the same offset.
Current: build-70 (1 record); previous: build-65 (0 records).
| Build | Status | GPU / CPU | FPS | Details |
|---|---|---|---|---|
| build-70 | playable | Not provided / Not provided | Not provided | Open report |
| nx2 build 65 (3bdd53d) | runs with issues | Sapphire nitro+ 7900XTX / 9800x3D | Not provided | Open report |
Problems or notes: Runs well, though not at a locked 60 fps.
Problems or notes: A black rectangle appears in a mini-example guide; the reporter says it also occurs on build-70.
Current: build-70 (1 record); previous: build-65 (0 records).
| Build | Status | GPU / CPU | FPS | Details |
|---|---|---|---|---|
| build-75 | runs with issues | NVIDIA GeForce RTX 4060 Laptop, 8 GB / Intel Core i7-13650HX | 20 FPS | Open report |
| build-70 | runs with issues | NVIDIA GeForce RTX 4060 Laptop, 8 GB / Intel Core i7-13650HX | 20 FPS | Open report |
| build-65 | playable | NVIDIA GeForce RTX 4060 Laptop, 8 GB / Intel Core i7-13650HX | 10–30 FPS | Open report |
Problems or notes: Terrain/world renders solid white while the HUD and characters still draw. With EDEN_NX2_RESETFIX=0, the ground renders black without texture or lighting.
Problems or notes: Terrain/world renders solid white while the HUD and characters still draw.
Problems or notes: Not provided
Current: build-75 (1 record); previous: build-70 (1 record).
| Build | Status | GPU / CPU | FPS | Details |
|---|---|---|---|---|
| release-binaries #80 | unknown | NVIDIA RTX 50 series / Not provided | 23–24 FPS | Open report |
Problems or notes: User report: the game runs at a maximum of 23–24 FPS.
| Build | Status | GPU / CPU | FPS | Details |
|---|---|---|---|---|
| build-70 | runs with issues | NVIDIA RTX 40 series / Not provided | Not provided | Open report |
Problems or notes: User reports that FMVs and pre-rendered videos are skipped; the opening cut-scene skips to the in-engine scene.
Current: build-70 (1 record); previous: build-65 (0 records).
| Build | Status | GPU / CPU | FPS | Details |
|---|---|---|---|---|
| 5a50f50 | runs with issues | AMD RX 7000 series / Not provided | Not provided | Open report |
Problems or notes: User reports repeated crashes around Deku Tree; after the first crash, booting gets stuck compiling shaders until the shader cache is deleted. Another user says the problem occurs only with RADV and that the game runs too slowly to be playable on their NVIDIA GPU.
| Build | Status | GPU / CPU | FPS | Details |
|---|---|---|---|---|
| build 75 (c9ebb5c) | runs with issues | AMD RX 9000 series; RX 9060 XT 16GB / Not provided | Not provided | Open report |
Problems or notes: An error appears after the cinematic and remains on screen, blocking the view.
| Build | Status | GPU / CPU | FPS | Details |
|---|---|---|---|---|
| 80 | runs with issues | NVIDIA RTX 40 series / Not provided | Not provided | Open report |
Problems or notes: In stages past the first one, gameplay displays a black screen while the UI remains visible; pausing shows the world rendered in the background. The reporter says it worked on older builds of eglantine.
| Build | Status | GPU / CPU | FPS | Details |
|---|---|---|---|---|
| build-70 | runs with issues | Not provided / Not provided | Not provided | Open report |
| release-binaries #80 | not booting | NVIDIA RTX 50 series / Not provided | Not provided | Open report |
Problems or notes: Some races still stall while shaders build.
Problems or notes: Force quits after being stuck on the "Loading Shaders" screen for about 2 seconds.
Current: build-70 (1 record); previous: build-65 (0 records).
| Build | Status | GPU / CPU | FPS | Details |
|---|---|---|---|---|
| build-65 | runs with issues | NVIDIA RTX 30 series or older / Not provided | Not provided | Open report |
Problems or notes: Freezes when preview videos play for the selected mode at the main menu, before starting a cutscene.
Current: build-65 (1 record); previous: nx2-build-34 (0 records).
| Build | Status | GPU / CPU | FPS | Details |
|---|---|---|---|---|
| build-83 | runs with issues | NVIDIA RTX 50 series / Not provided | Not provided | Open report |
Problems or notes: User reports a crash after about 15 to 20 minutes. The user also reports having 16GB of RAM.
Current: build-83 (1 record); previous: build-75 (0 records).
| Build | Status | GPU / CPU | FPS | Details |
|---|---|---|---|---|
| build-83 | runs with issues | AMD RX 9000 series / Not provided | Not provided | Open report |
Problems or notes: The emulator crashes after 5 to 10 minutes of gameplay.
Current: build-83 (1 record); previous: build-75 (0 records).
| Build | Status | GPU / CPU | FPS | Details |
|---|---|---|---|---|
| build-83 | not booting | Other / Not provided | Not provided | Open report |
Problems or notes: User reports that the game blacks out when booted. They identify this as a regression from build 75.
Current: build-83 (1 record); previous: build-75 (0 records).
| Build | Status | GPU / CPU | FPS | Details |
|---|---|---|---|---|
| Lichii build 83 (MSVC) | runs with issues | NVIDIA GeForce GTX 1070 / Intel Core i7-7700 | 18 FPS | Open report |
Problems or notes: User reports audio out of sync with video and frequent hangs or stalls during play. Configuration: Vulkan, 1X resolution, Handheld console mode; GPU Mode was Accurate at the time of the screenshot.
No related issues or release notes are listed for this game yet.
| Build | Status | GPU / CPU | FPS | Details |
|---|---|---|---|---|
| Lichii nx2 build 83 (5a50f50) | runs with issues | NVIDIA RTX 30 series or older; RTX 2060 Super / Ryzen 3600 / 32GB RAM | Not provided | Open report |
Problems or notes: Video is consistently out of sync with game audio from the first cutscene; the game freezes for a long time during the skippable dialogue sequence at the tree, tree light appears blown out afterward, and soundtrack stutters or lags relative to voice acting.
No related issues or release notes are listed for this game yet.
| Build | Status | GPU / CPU | FPS | Details |
|---|---|---|---|---|
| build-70 | playable | Not provided / M4 Pro | 30–38 FPS | Open report |
Problems or notes: The report says races measured 30–38 fps after macOS performance work.
Current: build-70 (1 record); previous: build-65 (0 records).
| Build | Status | GPU / CPU | FPS | Details |
|---|---|---|---|---|
| build-83 | runs with issues | intel uhd graphics / intel core i5 gen 13th | Not provided | Open report |
Problems or notes: User reports missing textures and buggy visuals after booting, occasional crashes during startup, and crashes when playing the Grand Prix race.
Current: build-83 (1 record); previous: build-75 (0 records).
| Build | Status | GPU / CPU | FPS | Details |
|---|---|---|---|---|
| build-75 | runs with issues | AMD RX 6000 series or older / Not provided | 10–15 FPS | Open report |
Problems or notes: User reports constant stuttering, GPU usage reaching 100%, and RAM usage increasing nonstop. FPS was around 10 on the title screen and barely reached 15 during play.
Current: build-75 (1 record); previous: build-70 (0 records).
| Build | Status | GPU / CPU | FPS | Details |
|---|---|---|---|---|
| build-75 | runs with issues | RTX 5070 Ti / Not provided | Not provided | Open report |
| 99ac3d595 plus listed cherry-picked commits | playable | RTX 5070 Ti / Not provided | 38 FPS | Open report |
Problems or notes: Docked, 1x. User reported missing vegetation, heavy white glow, and visual blotches in tested scenes. Rejecting shaders with EDEN_NX2_REJECT_HASH visibly improved Link and the foreground, but removed bloom accumulation and the river surface.
Problems or notes: Docked, 1x, in front of the Deku Tree in Kokiri Forest. Grass and ferns drew and the heavy haze was gone in a short, still-camera test. Other areas, interiors, cutscenes, long sessions, river rendering, and blotches were not verified. User reported about 38 FPS.
Current: build-75 (1 record); previous: build-70 (0 records).
| Build | Status | GPU / CPU | FPS | Details |
|---|---|---|---|---|
| Frizti v2 (oot-gather-fix @ 765659a) plus port of #204 | runs with issues | NVIDIA RTX 3090 / Ryzen 9 9950X3D | Not provided | Open report |
Problems or notes: Linux 7.0, Vulkan, GPU accuracy Low, docked, 1x, async shaders on. User reported river-water flicker that depended on the sun's position relative to the camera.
| Build | Status | GPU / CPU | FPS | Details |
|---|---|---|---|---|
| nx2 with extra PRs | runs with issues | RX 6650 XT / Not provided | Not provided | Open report |
Problems or notes: Handheld, 1x. During gameplay, user observed zero-format texture assertions and Unmapped Device ReadBlock errors; terrain and subtitles flickered. The user did not establish whether the assertions caused the flicker.
| Build | Status | GPU / CPU | FPS | Details |
|---|---|---|---|---|
| build-83 | playable | RTX 4070 Ti / Ryzen 7 7700X | Not provided | Open report |
| 3724db9a5c | playable | RTX 4070 / i9-12400F | 16 FPS | Open report |
Problems or notes: Vulkan, docked, 2x, GPU accuracy Low, game version 1.1. User reported haze gone and Link and Kokiri Forest clearly visible in gameplay, but FPS was described as low. Handheld mode was not tested.
Problems or notes: Vulkan, docked, 1x. User reported grass visible and the tree clearly visible through grey fog in front of the Deku Tree; 16 FPS was a single in-game counter reading.
From build-75 to build-83: follow the gameplay changes described for these two builds.
Before: Missing vegetation and incorrect material data; affected lighting and colours; a glowing doorway; one-frame white flashes; and on AMD, shaders could produce a black 3D scene.
After: Additional shader pointers and storage-buffer bindings, corrected buffer tracking and mesh-shader register handling, fixed occlusion-query and nested-return handling, and added the Max Resolution add-on and frame-ahead presentation tuning.
build-75 → build-83
| Build | Status | GPU / CPU | FPS | Details |
|---|---|---|---|---|
| 8813b44 | runs with issues | RX 6800 XT / Not provided | Not provided | Open report |
Problems or notes: At 1x in Link's house and Kokiri Forest, user reported blotches from a half-resolution layer. A diagnostic depth-clear change removed the blotches in Link's house, but the river water remained dark with ripples and no visible lit contribution.
| Build | Status | GPU / CPU | FPS | Details |
|---|---|---|---|---|
| build-80 | runs with issues | AMD RX 6700 XT / Not provided | Not provided | Open report |
Problems or notes: Docked, 1x. The opening cinematic and title screen rendered correctly, but the Deku Tree exterior cutscene remained black except for Navi's light radius. User also reported a deterministic AMD driver crash while building graphics pipelines in that scene.
| Build | Status | GPU / CPU | FPS | Details |
|---|---|---|---|---|
| 62ba83427e | runs with issues | Radeon 8060S / Ryzen AI MAX+ 395 | 31–37 FPS | Open report |
Problems or notes: Docked, 1x, Kokiri Forest. User reported haze, blotches, and a translucent band. Rejecting fog and layer shaders removed some artifacts but also removed in-game fog and darkened the river. Two starts remained black from launch, one with music playing; closing and reopening cleared the black screen.
| Build | Status | GPU / CPU | FPS | Details |
|---|---|---|---|---|
| b4716fc | runs with issues | RX 6700 XT / Not provided | Not provided | Open report |
Problems or notes: Docked, 1x. The Deku Tree exterior cutscene showed a black screen except for a small circle around Navi; the title screen and earlier cinematics rendered correctly.
| Build | Status | GPU / CPU | FPS | Details |
|---|---|---|---|---|
| build-75 | runs with issues | NVIDIA RTX 40 series / Not provided | Not provided | Open report |
Problems or notes: The user reports the game starts and audio is audible after starting a new game, but visuals are fully black other than the UI. A log reports that FFmpeg has no decoder for "video/av1". Comments mention differing results with docked mode and PGO versus MSVC builds; the game is not identified.
Current: build-75 (1 record); previous: build-70 (0 records).
| Build | Status | GPU / CPU | FPS | Details |
|---|---|---|---|---|
| build-75 | runs with issues | NVIDIA RTX 30 series or older / Not provided | Not provided | Open report |
| build-75 | runs with issues | NVIDIA RTX 30 series or older / Not provided | Not provided | Open report |
Problems or notes: The startup screen plays, but afterward there is audio and a black screen. A commenter suggests switching from handheld mode to Docked mode for minimally better performance, while noting very low FPS and bloom issues; this is a suggestion, not a confirmed fix.
Problems or notes: User reports the title screen and menus are visible with sound, but the background is black; after starting a new game, sound continues while the screen remains black.
Current: build-75 (2 records); previous: build-70 (0 records).
| Build | Status | GPU / CPU | FPS | Details |
|---|---|---|---|---|
| build-75 | runs with issues | Other / Not provided | 20 FPS | Open report |
Problems or notes: Boots to a black screen with audio. A comment reports that clearing the cache and launching again fixes the black-screen issue, but the game runs at 20 fps.
Current: build-75 (1 record); previous: build-70 (0 records).
| Build | Status | GPU / CPU | FPS | Details |
|---|---|---|---|---|
| build-88 | runs with issues | Intel(R) Iris(R) Xe Graphics / 12th Gen Intel(R) Core(TM) i7-1255U | Not provided | Open report |
| build-65 | not booting | NVIDIA GeForce RTX 3080 / AMD Ryzen 7 5800X 8-Core Processor | Not provided | Open report |
Problems or notes: Only character outlines and UI are visible; the user reports a black-screen-like graphics issue.
Problems or notes: User reports a black screen while loading; GPU is reported idle at 16% in the title. A commenter suggests trying build-70, but there is no reported result.
Current: build-88 (1 record); previous: build-83 (0 records).
| Build | Status | GPU / CPU | FPS | Details |
|---|---|---|---|---|
| Lichii nx2 build 75 (c9ebb5c) | runs with issues | NVIDIA RTX 40 series / Not provided | Not provided | Open report |
Problems or notes: Console spam of Unmapped Write64 errors; the reporter believes these may cause audio popping. Closing the game appears to cause an emulation crash.
| Build | Status | GPU / CPU | FPS | Details |
|---|---|---|---|---|
| build-75 | runs with issues | NVIDIA RTX 50 series / Not provided | Not provided | Open report |
| 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 |
Problems or notes: The emulator closes about a minute after gameplay begins.
Problems or notes: On RTX 50-series GPUs, the GPU device can be lost after a scene change.
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.
Current: build-75 (2 records); previous: build-70 (1 record).
| 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 |
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.
| Build | Status | GPU / CPU | FPS | Details |
|---|---|---|---|---|
| build-83 | runs with issues | AMD Radeon RX 9060 XT 16 GB / Intel i7-9700K | Not provided | Open report |
| build-75 | runs with issues | RX 5700 / Not provided | 32 FPS | Open report |
| build-75 | runs with issues | AMD Radeon RX 7900 XTX / Not provided | 12 FPS | Open report |
| build-70 | not booting | NVIDIA GeForce RTX 3070 / AMD Ryzen 7 5800X 8-Core Processor | Not provided | Open report |
| R75 MSVC | boots | Not provided / Not provided | Not provided | Open report |
| build 83 (MSVC) | runs with issues | NVIDIA GeForce GTX 1070 / Intel Core i7-7700 | 18 FPS | Open report |
| Not provided | runs with issues | RX 5700 / Not provided | Not provided | Open report |
| Not provided | runs with issues | AMD Radeon RX 7900 XTX / Not provided | Not provided | Open report |
| Not provided | runs with issues | AMD Radeon RX 7900 XTX / Not provided | Not provided | Open report |
Problems or notes: User reports say the game reaches gameplay and then loses the GPU device. The report also mentions black output after rejecting selected shaders and a later device loss. All tried settings and environment-variable changes still resulted in device loss.
Problems or notes: The comment reports 4800 to 16800 presents and 32 FPS, and says the game presents frames. This is compared with local builds of commit b8c812b18 that stalled at max present 8 and showed no frames; the difference's cause is unresolved.
Problems or notes: User reports no hang, but the 3D scene is black with HUD only.
Problems or notes: Issue reporter says the game remains on "Launching..." indefinitely; the log shows the emulated program breaking execution with error F001. Additional user reports mention infinite launch screens. Other users report that R75 MSVC boots past the intro FMV in docked mode, but describes severe white/black-screen graphics problems in other builds or modes.
Problems or notes: A user reports booting and working past the intro FMV in docked mode; no sustained gameplay is stated.
Problems or notes: User report: Approximately 18 FPS in gameplay, with frequent hangs or stalls whose trigger and duration were not isolated. Settings included Vulkan, 1X resolution, Accurate GPU mode, and Handheld console mode.
Problems or notes: The local ClangCL build of b8c812b18 stalled at max present 8 and showed no frames. A local MSVC build of the same commit also stalled at max present 8 and died within a minute.
Problems or notes: User reports GPU hang or device loss when gameplay starts on local build 27226d2. A separate local build with #150 reverted, #127 kept, and docked mode reportedly avoids the hang and renders the full scene at about 24 FPS; another configuration without #127 renders only areas lit by Navi.
Problems or notes: A user reports a local 27226d2 build with #150 pointer-binding commits reverted ran for 5+ minutes past the point where the original build timed out; grass and trees were reportedly still missing.
Current: build-83 (1 record); previous: build-75 (2 records).
| Build | Status | GPU / CPU | FPS | Details |
|---|---|---|---|---|
| build-75 | not booting | AMD Radeon RX 6750 XT (RDNA2) / Intel Core i7-11700F | Not provided | Open report |
| build-75 | runs with issues | AMD Radeon RX 6800 XT (16 GB, RDNA 2) / AMD Ryzen 5 9600X | Not provided | Open report |
| build-75 | runs with issues | RX 9070 XT / Not provided | Not provided | Open report |
| build-75 | runs with issues | AMD Radeon RX 9060 XT 16 GB (Navi 44) / AMD Ryzen 7 5700 | Not provided | Open report |
| R75 PGO | not booting | Not provided / Not provided | Not provided | Open report |
| release-binaries #75 | runs with issues | 4070 / 7800x3d | Not provided | Open report |
| Lichii nx2 build 75 (c9ebb5c) | runs with issues | NVIDIA GeForce RTX 4060 Laptop GPU / Intel Core i7-14650HX | Not provided | Open report |
| Not provided | boots | Not provided / Not provided | Not provided | Open report |
| Not provided | runs with issues | AMD Radeon RX 7800 XT (16 GB) / Not provided | Not provided | Open report |
| Not provided | runs with issues | AMD RADEON RX 9070 XT 16GB / AMD RYZEN 7700 | Not provided | Open report |
| Lichii nx2 build 75 | runs with issues | NVIDIA GeForce RTX 4060 Laptop GPU / Intel Core i7-14650HX | Not provided | Open report |
| Not provided | runs with issues | RTX 3050 Laptop / Not provided | Not provided | Open report |
| build 75 (`c9ebb5c`) | runs with issues | RX 5700 (RDNA1) / Not provided | Not provided | Open report |
| Not provided | runs with issues | RTX 5090 / Ryzen 9800X3D | 53.66 FPS | Open report |
| Not provided | playable | RX 6650 XT / i5-10400F | 22–27 FPS | Open report |
| Not provided | runs with issues | AMD 7900 XTX / Not provided | Not provided | Open report |
| current nx2 | playable | RTX 4070 SUPER / Not provided | Not provided | Open report |
Problems or notes: On Windows 11 25H2, the game passes the initial launching stage but becomes unresponsive at “Building 9 shaders”; audio continues and it does not reach gameplay. The report identifies the game as Switch 2 version 1.1.1.
Problems or notes: On Windows 11 Version 26H2, the Start Menu and 2D UI render, but gameplay has a completely black screen for all 3D geometry. With use_disk_shader_cache = true, subsequent boots hang at Loading Shaders 25 / 27; the reporter says deleting cache/shader/0400486024dec000 and setting use_disk_shader_cache = false resolves the startup freeze. The report says the black-screen workaround still does not render 3D scenes on this RDNA 2 card.
Problems or notes: Reporter describes a black screen after the intro caused by a rejected 1080p upscaler shader. They report a second AMD-only rendering issue that leaves the world black except around Navi and Link; with both cited fixes, gameplay renders. Handheld mode is reported as brighter and blurrier than Docked mode. Texture flicker is reported with Low GPU accuracy and GPU thread split; High removes it but disables the split and runs at about 9 fps.
Problems or notes: User reports over-bright bloom/glow, dense fog, incorrect lighting on characters and terrain, and some textures decoded as garbage after entering an outdoor area. The game does not crash. Performance was reported as 33–34 ms/frame until about 80 seconds, then 89.5 ms/frame (about 11 fps) outdoors.
Problems or notes: A user reports a black screen past the title screen.
Problems or notes: A user reports that it boots, but shaders are very bad and everything is white; in handheld mode everything appears black.
Problems or notes: Gameplay starts, but the 3D scene and character are black; menus and item preview can render, and HUD elements remain visible. Reported GPU shader errors include rejected native texture gather shaders and draws skipped for no pipeline.
Problems or notes: A commenter reported that only the starting menu and options appeared before Play, with audio working and no HUD visible.
Problems or notes: A commenter reported that the game launched and audio and controls worked, but the 3D gameplay scene remained black while the HUD was visible.
Problems or notes: A commenter reported a black screen after the introductory cinematic and audio playing ahead of the video during the intro.
Problems or notes: On Windows 11 with Vulkan, the game reaches gameplay, but the 3D scene is black while the HUD remains visible. The report notes shader rejections and skipped draws. A commenter reported that switching to Docked mode resolved the black screen, but also reported slow performance; others reported stuttering, FPS drops, overexposure, black scenes on AMD GPUs, or audio playing ahead of the video during the intro.
Problems or notes: A commenter reported that the 3D scene was not black, but shadows flickered and trees had no leaves.
Problems or notes: A commenter reported that the title screen rendered, but gameplay remained black at 31 FPS. Docked mode and the listed graphics-setting changes did not help; the commenter could not confirm the mode switch because the status bar continued to show HANDHELD.
Problems or notes: User report: A local candidate build and bundled settings produced 53.66 presents/s in a stationary village view. Limited gameplay traversed to the maze entrance and returned without death or reload; the test did not cover sword pickup, further boulder traversal, or the Deku Tree. Native 60 FPS was not locked, and the report does not establish full-game compatibility.
Problems or notes: A commenter reports that with asynchronous shader compilation off, the game loaded and played on an MSVC fork build on Windows 11 24H2, handheld, at 1x. With asynchronous shader compilation on, it either stayed black with background audio or remained at “Building N shader(s)” at 0 FPS. The commenter says this build already contained #149; disabling async compilation is a user-reported workaround, not a confirmed fix.
Problems or notes: A commenter reports that the game logo and menu options show, but there are no 3D graphics. The commenter attributes the issue to the PGO Windows build and says MSVC works.
Problems or notes: Commenter reports the over-bright, washed-out rendering is gone and says the title was played for about 20 minutes without stretched/exploded environment geometry recurring. The specific build changes responsible are unknown.
Current: build-75 (4 records); previous: build-70 (0 records).
Also listed as: OoT
| Build | Status | GPU / CPU | FPS | Details |
|---|---|---|---|---|
| build-83 | runs with issues | RTX 5090 / Ryzen 7 9800X3D | 34.04–46.28 FPS | Open report |
| build-75 | runs with issues | AMD RX 7000 series / AMD Ryzen 5 5600G with Radeon Graphics | Not provided | Open report |
| Not provided | runs with issues | Radeon RX 9070 XT 16 GB / Ryzen 7 7700X | Not provided | Open report |
Problems or notes: User report: Native gameplay remained below 60 FPS after shader warmup. Measurements varied by scene and settings; walking, camera movement, ladder climbing, NPC dialogue, autosave, and loading an outdoor save worked in a limited test. Audio was not assessed.
Problems or notes: User reports audio and video desynchronization on the title screen and intro. A commenter reports title-screen video in heavy slow motion, audio leading by approximately 3 seconds and the gap increasing by the initial dream cutscene; changing Frame Pacing (30/60/Auto) or reducing Anisotropic Filtering to 2x did not resolve it.
Problems or notes: With Low GPU accuracy and EDEN_NX2_SPLIT=2, textures and surfaces flicker and some surfaces remain white; reported frame time was 29–44 ms per frame, up to about 20 ms in lighter areas. High accuracy removes the flicker but disables the split and results in 9–14 fps. Accurate GPU fence behavior hangs after about 45 seconds; enabling buffer downloads does not resolve the flicker. Outdoor haze and a dark river surface are also reported.
Current: build-83 (1 record); previous: build-75 (1 record).
Also listed as: OoT
| Build | Status | GPU / CPU | FPS | Details |
|---|---|---|---|---|
| Not provided | playable | RTX 4070 SUPER / Not provided | 59.3–60 FPS | Open report |
Problems or notes: A commenter reports no texture flicker during roughly six minutes of gameplay with Low GPU accuracy and EDEN_NX2_SPLIT=2; light scenes reached the game's 60 FPS cap.
| Build | Status | GPU / CPU | FPS | Details |
|---|---|---|---|---|
| build-75 | runs with issues | NVIDIA GeForce RTX 5080 (16 GB) / Intel Core Ultra 7 270K Plus (24 threads) | 28–29 FPS | Open report |
Problems or notes: User report: Docked mode was required to render; Handheld showed a black 3D screen. Gameplay settled at 28–29 FPS, while menus and loading screens ran at 53–59 FPS. The report attributes the limit to CPU load. No attempted settings changes improved the gameplay ceiling.
Current: build-75 (1 record); previous: build-70 (0 records).
| Build | Status | GPU / CPU | FPS | Details |
|---|---|---|---|---|
| build-75 | runs with issues | NVIDIA RTX 3050 Laptop / AMD Ryzen 7 5800H | 30 FPS | Open report |
Problems or notes: User report: The game boots and presents frames at a steady 30 FPS, but remains on a black screen after its AV1 video streams fail because FFmpeg has no decoder for "video/av1". NVDEC Off and Gpu reportedly make no difference; the same result was reported on an AMD Radeon iGPU. Vulkan was used.
Current: build-75 (1 record); previous: build-70 (0 records).
| Build | Status | GPU / CPU | FPS | Details |
|---|---|---|---|---|
| 75 (`nx2-build-75`, Linux x86_64 PGO AppImage) | runs with issues | AMD RX 7000 series (Radeon RX 7600, RADV 26.2.5, Vulkan 1.4.354) / Not provided | Not provided | Open report |
Problems or notes: During the intro AV1 cutscene, the video area is solid green; audio and subtitles work. The report says decoded frames are produced at 60 fps, but the image does not reach the screen.
| Build | Status | GPU / CPU | FPS | Details |
|---|---|---|---|---|
| `nx2-build-75`, MSVC x86_64 (`lichii-windows-x86_64.zip`) | runs with issues | AMD Radeon RX 6700 XT 8 GB, AMD driver 2.0.353, Vulkan 1.4.315 / AMD Ryzen 7 5800X, 32 GB RAM | Not provided | Open report |
Problems or notes: The game renders normally before the intro AV1 cutscene, but the video layer is black while audio and subtitles work, then the emulator hangs indefinitely. The report says the freeze starts when the AV1 decoder opens.
| Build | Status | GPU / CPU | FPS | Details |
|---|---|---|---|---|
| build-75 | runs with issues | Adreno 740 / Snapdragon 8 Gen 2 | Not provided | Open report |
Problems or notes: Black screen despite booting to the AV1 video stage; pipeline-builder threads remain busy compiling large compute shaders, with memory exhaustion or GPU hangs reported in tests. Audio was intermittent. In a separate Eglantine PR #614 test, it reached the title screen and New Game, then went black at the first in-game frame at about 60 FPS.
Current: build-75 (1 record); previous: build-70 (0 records).
| Build | Status | GPU / CPU | FPS | Details |
|---|---|---|---|---|
| build-70 | runs with issues | Not provided / Not provided | Not provided | Open report |
Problems or notes: Some textures are still black, and it can crash later in play.
Current: build-70 (1 record); previous: build-65 (0 records).
| Build | Status | GPU / CPU | FPS | Details |
|---|---|---|---|---|
| build-75 | not booting | AMD RX 6000 series or older / Not provided | Not provided | Open report |
| build-75 | runs with issues | RTX 3070 / 7800x3D | Not provided | Open report |
| Lichii build-75 (nx2-build-75) | not booting | RTX 5080 / Not provided | 60 FPS | Open report |
Problems or notes: User reports that sound and the Zelda logo work, but the game displays a black screen. Comments also report black screens on AMD and NVIDIA GPUs and on Linux.
Problems or notes: Commenters report that shared settings resolved the black screen on the MSVC build, but serious FPS, ambient occlusion, and lighting issues remain.
Problems or notes: A commenter reports that the title screen displays at 60 FPS but the screen goes black after selecting New Game and remains black through the intro cutscene. The log reports that FFmpeg has no decoder for video/av1.
Current: build-75 (2 records); previous: build-70 (0 records).
| Build | Status | GPU / CPU | FPS | Details |
|---|---|---|---|---|
| build-83 | runs with issues | RX 9060 XT 16 GB / Not provided | Not provided | Open report |
Problems or notes: User reports that the black-screen behavior is gone and the game reaches gameplay, but it device-loses at gameplay start with VK_ERROR_DEVICE_LOST.
Current: build-83 (1 record); previous: build-75 (0 records).
| Build | Status | GPU / CPU | FPS | Details |
|---|---|---|---|---|
| Lichii nx2-build-83 | not booting | AMD Radeon RX 6650 XT (RDNA2) / Intel Core i5-10400F | Not provided | Open report |
| nx2-build-83 | runs with issues | Radeon RX 6800 / Not provided | 43–47 FPS | Open report |
Problems or notes: User reports the render area remains black after booting, in both handheld and docked modes. Updating the AMD driver, clearing the shader cache, changing listed settings, and trying other builds did not change the result.
Problems or notes: User reports the game renders correctly in a screen capture at about 47 fps, but the displayed image is solid green. The report states about 43 fps during presentation.
Also listed as: OoT
| Build | Status | GPU / CPU | FPS | Details |
|---|---|---|---|---|
| build-83 (PGO, Windows x86_64) | runs with issues | RTX 3090 24 GB / Ryzen 9 5900X | Not provided | Open report |
Problems or notes: User reports that about 99–104 graphics pipelines are rebuilt on the GPU thread during the first 10 seconds of gameplay on each boot, taking about 943.3–998.1 ms and causing a visible hitch.
Also listed as: OoT
| Build | Status | GPU / CPU | FPS | Details |
|---|---|---|---|---|
| build 83 (clang 23.1.6) | runs with issues | AMD RX 9000 series / Not provided | Not provided | Open report |
Problems or notes: User reports repeated segfaults during gameplay in the Great Deku Tree while RADV builds a graphics pipeline. The reported fragment shader fails spirv-val because its depth image sampled type is u32 while the sampling result type is f32.
Also listed as: OoT
| Build | Status | GPU / CPU | FPS | Details |
|---|---|---|---|---|
| Not provided | runs with issues | Not provided / Apple M6 (arm64) | 12–14 FPS | Open report |
Problems or notes: The title screen and intro video render, but the emulator may lose the Metal device or hang at the intro-video/gameplay boundary. The report also describes GPU-thread deadlocks or hangs and, in one run, a process abort. Intro playback is reported at 12–14 FPS. A commenter reports a separate black 3D scene with sound and subtitles after applying a local workaround on an Eglantine fork; current nx2 behavior was not yet confirmed.
Also listed as: OoT
| Build | Status | GPU / CPU | FPS | Details |
|---|---|---|---|---|
| build-83 | not booting | AMD RX 6000 series or older; AMD RX 6600 8GB / Not provided | Not provided | Open report |
| perf/frizti-integration build-85 | runs with issues | NVIDIA RTX 30 series or older (RTX 3060 12 GB) / i5-13600KF | Not provided | Open report |
Problems or notes: The issue reporter says the emulator begins loading and then stays on a black screen. This is an open issue.
Problems or notes: User reports the game freezes every time when walking deeper into the breakable-pot room in Hyrule Castle Town, near the guard. They report the same freeze on an earlier Lichii build and build-85; changing GPU Mode Fast vs Accurate and EDEN_NX2_BUFFER_DOWNLOADS on vs off did not resolve it.
Current: build-83 (1 record); previous: build-75 (0 records).
Also listed as: OoT
| Build | Status | GPU / CPU | FPS | Details |
|---|---|---|---|---|
| build-88 | runs with issues | 7800xt / Ryzen 7 5700X | Not provided | Open report |
Problems or notes: A commenter reports a large audio/video delay during the initial cutscene, followed by black screens on both monitors, a GPU crash and reset, and a Hyprland crash when they start controlling the character.
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
Also listed as: OoT
| Build | Status | GPU / CPU | FPS | Details |
|---|---|---|---|---|
| build-83 | runs with issues | RTX 5090 / Ryzen 7 9800X3D | Not provided | Open report |
| Not provided | runs with issues | RX 5700 / Not provided | Not provided | Open report |
Problems or notes: Opening rendered and controllable Kokiri Forest gameplay was reached. Some sessions hung at “Closing software…” during shutdown, while others exited successfully. The source does not establish a cause or fix.
Problems or notes: A commenter reports a black 3D world with working UI. The commenter proposes possible shader reordering and fragment shader shuffle causes, and describes code changes and measurements from other projects; these are user-provided claims, not confirmed Lichii fixes.
Current: build-83 (1 record); previous: build-75 (0 records).
Also listed as: OoT
| Build | Status | GPU / CPU | FPS | Details |
|---|---|---|---|---|
| build-88 | not booting | AMD Radeon AI PRO R9700 (9070XT) / Not provided | Not provided | Open report |
| Not provided | unknown | Not provided / Not provided | Not provided | Open report |
| build-83 | runs with issues | RTX 4070 SUPER 12 GB / i5-14600KF | 30 FPS | Open report |
| build-83 | unknown | AMD RX 6000 series or older; AMD Radion RX 6650 XT / AMD Ryzen 5 5600 | Not provided | Open report |
| build-83 | unknown | Not provided / Not provided | Not provided | Open report |
| build-75 | runs with issues | RTX 3080 / Ryzen 5900X | 12–22 FPS | Open report |
| Not provided | runs with issues | AMD Radeon RX 6600 XT 8 GB / Ryzen 5 5600X | 25–33 FPS | Open report |
| 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 |
Problems or notes: User reports the app crashes when opening the game, with a segmentation fault. They say some earlier builds worked.
Problems or notes: Dynamic FPS is enabled by default, but full gameplay timing has not been verified; CPU Clock Boost/Overclock can affect game speed.
Problems or notes: Issue reporter describes shader problems and gameplay at about 30% speed. A commenter reports that GPU Mode: Fast restored normal speed and reached 60 FPS in most areas; build-83 held 60 FPS after the shader cache warmed up. The commenter also reports stutter while new shader pipelines are built.
Problems or notes: Reported that the game slows when booting; the reporter restarted the emulator and game and changed settings, but did not state a resolution.
Problems or notes: The release says the perf9 build was tested successfully in Ocarina of Time, but provides no gameplay duration or specific tested hardware.
Problems or notes: Outdoor areas have excessive fog and glow, performance is about 12–22 fps, and three rare shaders remain unsupported.
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.
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.
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.
Problems or notes: A commenter reports approximately 3 minutes of gameplay before a black screen, driver crash, and crash to desktop.
Problems or notes: Gameplay testing in Kokiri Forest reported no crashes; normal game speed was below 60 FPS with #216. GPU accuracy was Low.
Problems or notes: A commenter reports having the same issue without further details.
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
Also listed as: OoT
| Build | Status | GPU / CPU | FPS | Details |
|---|---|---|---|---|
| Not provided | unknown | RTX 3080 Ti / i9-12900K | 46–47.8 FPS | Open report |
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.
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 |
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.
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 |
| Not provided | runs with issues | NVIDIA RTX 30 series or older / Not provided | Not provided | Open report |
| Not provided | runs with issues | AMD RX 9060 XT / Not provided | Not provided | Open report |
| nx2-build-83 | runs with issues | AMD RX 9000 series / Not provided | 41 FPS | Open report |
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.
Problems or notes: Audio plays a different part of the game than the image during the intro; the audio is clean but out of sync by a scene. A follow-up report says the game uses StreamType::Render and that traced sink appends were complete with no samples dropped. Another user reports the same issue with a 7800X3D, RTX 5070, and 32gb DDR5.
Problems or notes: A commenter reports a driver crash and black screen after the intro on the MSVC build. The PGO build reportedly shows only 2D elements such as the logo or menu.
Problems or notes: User reports audio running ahead of video, cutting out and repeating during the opening cutscene, followed by a system freeze at the Deku Tree cutscene requiring a forced shutdown. Settings reported: Vulkan, GPU Mode Fast, Docked, Bilinear window adapting filter, and no anti-aliasing.
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
| Build | Status | GPU / CPU | FPS | Details |
|---|---|---|---|---|
| build-75 | runs with issues | NVIDIA RTX 30 series or older / Not provided | Not provided | Open report |
Problems or notes: The report describes audio with no visuals. A commenter reports the title screen at 60 FPS followed by a black screen when starting a new game, with an AV1 decoder error. Other users report black screens, crashes, very low FPS, missing textures, lighting and graphics artifacts, and a blown-out white image.
Current: build-75 (1 record); previous: build-70 (0 records).
Known issues from Lichii sources
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.
On RTX 50-series GPUs, the GPU device can still be lost after a scene change.
Recorded fix: Try NVIDIA driver 610.88.
Gameplay is capped at about 30 fps, even though the game asks for 60.
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.
Some textures are still black, and the game can crash later in play.
Some races still stall while shaders build.
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.
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.
In stages past the first one, the gameplay screen is black while the UI remains visible; pausing shows the world rendered in the background.
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.
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.
On some AMD GPUs, the UI may remain visible while the 3D world is black; reports also describe AMD driver timeouts or crashes.
User reports a performance regression in Build 75 on Linux with an AMD RX 6000 series or older GPU: around 10 FPS on the title screen, barely reaching 15 FPS with constant stuttering, GPU usage at 100%, and RAM usage increasing nonstop.
Only character outlines and UI are visible after launching the game.
User-reported reproducible freeze when walking deeper into the pot room in Hyrule Castle Town, near the guard.
Shrubbery, bushes, and grass turn dead-looking when approached in Hyrule Castle, especially in Zelda's garden. A user reports that it still occurs in build 83.
User reports describe gameplay performance below 60 FPS on multiple systems and builds. One report also describes a black 3D screen in Handheld mode; switching to Docked allowed rendering.
A user report says resolution 2X caused flicker or line artifacts; a separate candidate-build report says the release's overexposure warning was not cleared by its limited test.
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.
Commenters report rendering failures, black screens, and AMD driver crashes; one reports that audio continues while rendering is crashed.
A half-resolution layer drawn by pixel shader c72b6ea746c00433 causes dark blotches and translucent patches over objects in reported scenes. Users traced the issue to an occlusion-depth copy being wiped by deferred clears before the layer samples it.
Recorded fix: A user-reported workaround is EDEN_NX2_REJECT_HASH=c72b6ea746c00433; it removes the blotches in tested scenes but removes the river's visible water surface. Another user described PR #185 as fixing the ordering issue, but did not provide a tested result for that fix.
The Deku Tree exterior cutscene can render black except for a small area around Navi; a user also reported an AMD graphics-driver crash while building graphics pipelines in that scene.
Users reported missing grass, ferns, and broadleaf vegetation, with associated haze or overexposure in Kokiri Forest. A user reported that a local build with listed rendering commits restored grass and ferns and removed heavy haze in one location; a later comment proposed PR #204 for stale occlusion-query reads, but did not report a test result for that PR.
A user reported river-water flicker depending on sun direction relative to the camera; the proposed link to lighting or light volumes was unconfirmed.
A user reported zero-format texture assertions, Unmapped Device ReadBlock errors, and flickering terrain and subtitles; causation was not established.
On AMD RDNA2 GPUs, the game may freeze during shader or pipeline building, sometimes with background audio continuing. A commenter also reports black-screen or shader-building hangs with asynchronous shader compilation enabled.
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.
Recorded fix: Leave the game at the intro for about 20 minutes once so both pipelines finish and are cached; later boots reportedly pass the intro immediately until the driver or Lichii is updated. Alternatively, set `EDEN_NX2_REJECT_HASH=eff3ccbe1438679d,f9ea14a22394f5b1`; this avoids the wait but leaves parts of the picture black.
In the measurement-only experiment, disabling per-fence Preflushable downloads or batching downloads by 64 fences caused overexposure in Kokiri Forest.
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.
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.
Slows when booting.
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.
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.
On Windows build-83, shutdown can hang at “Closing software…” after gameplay. Some sessions completed shutdown successfully; the cause is undetermined.
A user reports missing textures and buggy visuals after booting, occasional startup crashes, and crashes when playing the Grand Prix race on build-83 with Intel integrated graphics on Windows 11.
Persistent graphics pipeline cache entries are reportedly rebuilt on the GPU thread during gameplay on repeated boots, causing a visible hitch.
With GPU Mode: Accurate (High), gameplay may run in slow motion at about 30 FPS; shader compilation can cause stutter on new content.
Recorded fix: Set GPU Mode to Fast; the commenter reports this resolved the slow gameplay for their setup.
Black screen after boot; some reports say sound and the title/logo work.
On build-83, one user reports a solid-green displayed image although a screen capture shows the game rendering correctly.
On build 83, a user reports device loss at gameplay start with VK_ERROR_DEVICE_LOST.
User reports GPU driver timeout or device loss when gameplay starts on AMD Windows systems, including RX 7900 XTX and RX 9060 XT. Reports associate the issue with #150 pointer-binding changes, but this is an unconfirmed hypothesis.
PGO artifact crashes in dynarmic with Unhandled SIGSEGV after 2–10 minutes on the reported machine.
After the startup screen, audio plays but the screen is black.
The emulator closes while loading shaders before a game is opened; the report says it used 20GB of RAM. Reports mention Windows 11 and Linux, and AMD GPUs.
User reports the game crashes after about 15 to 20 minutes.
User reports the game blacks out when booted in build 83; they state it worked in build 75.
The emulator crashes after 5 to 10 minutes of gameplay on Linux with an AMD RX 9000 series GPU.
Clean audio from a different point of the game plays while the intro image is displayed; audio and picture are substantially out of sync.
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.
Textures and surfaces flicker with Low GPU accuracy and EDEN_NX2_SPLIT=2 on Radeon RX 9070 XT; some surfaces remain white temporarily.
Outdoor haze is very strong, and the river surface can appear dark or black.
A commenter reports being unable to load a save, with the PC hard-locking or freezing before recovering after a driver crash or timeout; same GPU, 32GB RAM, and i7 9700K.
On Windows builds 70 and 75, terrain/world renders solid white while the HUD and characters still render. On build 75, EDEN_NX2_RESETFIX=0 changes the ground to black with no texture or lighting.
The emulator force quits after being stuck on the "Loading Shaders" screen for about 2 seconds.
The 3D gameplay scene can appear black while the HUD remains visible.
Recorded fix: Switch to Docked mode; one commenter reported this resolved the black screen. Other reports say this workaround did not help.
A commenter reported stuttering, FPS drops, and overexposure after switching to Docked mode.
A commenter reported flickering shadows and trees with no leaves.
A commenter reported audio playing ahead of the video during the intro.
Black screen after the first cutscene in handheld mode and VHS-like visual filter in docked mode.
After the intro, the scene where the deku tree is talking is completely black with very slow, stuttery dialogue.
Boots to a black screen with audio on macOS.
Recorded fix: Clear the cache and launch again.
On Radeon RX 580, hangs at a black screen at 0 FPS while building compute pipelines as the intro video starts.
Black screen after starting a new game, with audio continuing; a commenter also reports an FFmpeg error stating there is no decoder for video/av1.
Recorded fix: A commenter reports that using the MSVC build instead of the PGO build worked for them. Other commenters report that shared settings resolved the black screen, and one reports that switching from handheld to docked mode resolved it.
Very low FPS and graphics problems, including missing textures, lighting or ambient occlusion issues, and a blown-out white image.
With use_disk_shader_cache = true, subsequent boots hang indefinitely at Loading Shaders 25 / 27.
Recorded fix: Delete cache/shader/0400486024dec000 and set use_disk_shader_cache = false; the reporter says this resolves the startup freeze.
Black screen after the intro on AMD RX 9070 XT; the game's 1080p upscaler shader is rejected.
Recorded fix: Comment reports that #112 fixes the shader rejection; its CI build is fix/oot-upscaler-gathers / 7459f10 (build-80), and the fix is on nx2, but not in a release yet.
On AMD, the world is black except around Navi and Link; an RX 6800 XT reporter says the workaround still leaves all 3D geometry black.
Recorded fix: Comment reports that #127 fixes AMD-only demote reordering. Before it is merged, setting EDEN_NX2_REJECT_HASH=e40561a7a0f7a0b3 in %APPDATA%\eden\nx2_switches.txt makes the world visible on the RX 9070 XT report; another reporter says it does not resolve 3D rendering on the RX 6800 XT.
Texture flicker with Low GPU accuracy and GPU thread split on AMD RX 9070 XT.
Handheld mode is reported as much brighter and blurrier than Docked mode.
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.
On Linux with AMD/RADV, AV1 intro cutscene video renders solid green while audio and subtitles work.
On Windows 10 with AMD, the intro AV1 cutscene shows a black video layer with working audio and subtitles, then the emulator hangs indefinitely.
Black screen or intermittent black-screen flashes during gameplay and GDT; additional reports describe distorted docked rendering, overly bright and low-resolution handheld rendering, and intro audio ahead of video.
A local ClangCL build of b8c812b18 stalled at max present 8 and showed no frames; a local MSVC build of the same commit stalled at max present 8 and died within a minute, unlike the reported build-75 release.
User reports a black background at the title screen and a black screen after starting a new game, with sound still audible.
User reports audio/video desynchronization on the title screen and intro; a commenter reports slow-motion live-rendered title-screen video with audio leading by approximately three seconds, worsening by the initial dream cutscene.
User reports a black screen after the game's AV1 video streams fail to decode; FFmpeg reports no decoder for "video/av1". The game idles indefinitely on a black frame.
Music disappears during the cutscene after booting the game.
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.
The game crashes while building shaders after the title card fades.
On Adreno 740 with Turnip, large native compute-shader pipelines can keep Vulkan pipeline-builder workers busy, consume substantial memory, and result in a black screen; some tests also reported GPU hangs or device loss.
The emulator closes about a minute after gameplay begins on Windows 11 with an NVIDIA RTX 50 series GPU.
An error appears after the cinematic and remains on screen, blocking the view.
Black screen during cinematic after the main menu appears; reported on Windows 11 with an AMD RX 6000 series or older GPU.
Users report crashes before the training mission begins and during the campaign.
Infinite startup launch loop when booting the .NUP version.
Issue reporter says Zelda Ocarina Of Time Remake stays on "Launching..." indefinitely; the log records an emulated program break with error F001. Other reports mention an infinite launch screen.
A user reports severe shader problems with white visuals; handheld mode shows a black screen.
A user reports a black screen past the title screen.
A user reports repeated Unmapped Write64 errors, possible audio popping, and an emulation crash when closing the game.
The 3D gameplay scene is black while HUD elements remain visible; menus and item preview can render correctly.
Terrain is visible through solid objects after getting past the intro.
FMVs and pre-rendered videos are skipped, including the opening cut-scene.
On build 70 (286117c), the MSVC zip aborts after 133.8 seconds of gameplay with 0xC0000409 at lichii.exe+0x2ecd3bd. The MinGW PGO zip reportedly aborts on the intro screen at the same offset.
A black rectangle appears in a mini-example guide; the reporter says it persists on build-70.
Weird artifacts, especially on shadows.
User reports a black screen while loading in Build 65.
Freezes while menu preview videos play on build 65. A comment reports a custom kirby-test build log showing the game aborting (2162-0001) during menu videos.
Recent release notes
Build build-88 · Not provided
Build build-88 · Not provided
Build build-88 · Not provided
Build build-88 · Zelda: Ocarina of Time
Build build-83 · Ocarina of Time
Choosing a build
build-75 · Published November 5, 2026
12 published download assets for this build.
Try the latest available release: build-88. Keep a working build as a fallback while you test.
Compatibility FAQ
Apply the game, status, GPU, and build filters, then copy the page URL. An exact game link opens its report card.
Check whether the game reaches menus or gameplay in other reports. Note your driver and renderer, then search the game or error in troubleshooting.
Driver versions, graphics settings, CPU load, and the part of the game being tested can change the result. Compare those details before changing your setup.
Use the official Lichii issue tracker. Include the game, build tag, hardware, driver, settings, and steps that reproduce what you saw.