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
Compatibilidade de jogos
Compatibilidade de jogos no Lichii Emulator
Tem um jogo em mente? Veja como ele roda no Lichii, confira os problemas conhecidos e escolha uma versão para testar.
Latest recorded build
build-88
Pre-release
Published November 6, 2026
Encontre um jogo
Buscar jogos compatíveis com o Lichii
Os dados atuais incluem 58 registros de jogo e ambiente e 114 relatos sobre o Lichii.
Não encontrou um jogo? Um resultado vazio significa que ainda não há um relato sobre ele no Lichii. Isso não indica falha em um teste.
Confira a plataforma indicada para distinguir diferentes versões de um jogo.
O que cada status significa: “Unknown”: sem conclusão. “Not booting”: o jogo não iniciou. “Boots”: só a inicialização foi confirmada. “Runs with issues”: houve problemas durante o jogo. “Playable”: foi possível continuar jogando durante o teste.
Compatibility results
Game Compatibility Results
Recorded performance
Performance by Build and Hardware
Open a game for its test details. Start with a GPU and build close to your own, then explore the driver, FPS, and gameplay notes.
No games match these filters. Try a different name, GPU, or build, or clear a filter to broaden the search.
Zelda: Ocarina of Time Reported platform: Windows 11
Also listed as: OoT
| Build | Status | GPU / CPU | FPS | Details |
|---|---|---|---|---|
| nx2-build-83 | runs with issues | AMD RX 9000 series / Not provided | 41 FPS | Open report |
nx2-build-83 report
Statusruns with issues
GPUAMD RX 9000 series
CPUNot provided
DriverNot provided
Recorded FPS41 FPS
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.
Related game issues
- macOS/MoltenVK: Ocarina of Time (0400486024DEC000) kills or hangs the Metal device at the intro-video boundary (open)
- [Crash] (open)
- [Crash] AMD Crash/AudioDesync (open)
- [AMD RX 9070 XT] Black screen with UI visible and GPU driver timeout (Build 88) (open)
- [Crash] Ocarina of Time (0400486024DEC000): freezes in Hyrule Castle Town pot room near the guard (open)
- [Crash] AMD Ocarina of time Doesn't Start (open)
- [GBug] Ocarina of Time (0400486024DEC000): intro freezes for 6 to 18 minutes on AMD while the driver optimizes two compute shaders (open)
- [Perf] OoT (0400486024DEC000): per-fence Preflushable buffer downloads (~430 MB/s) are the biggest GPU back-thread cost; batching them gives +55% draws/s but breaks exposure (open)
- [VBug] OoT Slows when booting. (open)
- Ocarina of Time harvest fork: findings and open tasks (open)
- [Crash] Linux/RADV (RX 9070 XT): invalid SPIR-V fragment shader (depth image u32 sampled as f32) segfaults in VkPipelineBuild, Ocarina of Time (open)
- [Bug] Windows build-83 can hang on Closing software after OoT gameplay (open)
- [GBug] OoT (0400486024DEC000): the same ~60 cached graphics pipelines are rebuilt on the GPU thread every boot (open)
- [VBug] Oot is in a "nightmare mode"? also gameplay speed is at like 30% (open)
- [GBug] Ocarina of Time on RADV (RX 9070 XT): 28-35 fps, 35 ms frame with no saturated thread (translation/sync bound) (open)
- [GBug] Zelda: Ocarina of Time (0400486024DEC000): the audio plays a different part of the stream than the picture (open)
- [VBug] [nx2-build-75] Zelda: Ocarina of Time (0400486024DEC000) black screen — no AV1 decoder (open)
- [VBug] OoT (0400486024DEC000): world renders black except areas lit by Navi and around Link, AMD RX 9070 (open)
- Release note: Outdoor areas have far too much fog and glow compared with console; performance is about 12–22 fps on a Ryzen 5900X with an RTX 3080, and three rare shaders remain unsupported.
- Release note: On macOS arm64 through MoltenVK, the Metal device may be lost or the GPU thread may hang at the intro-video/gameplay boundary. A commenter attributes the device loss to an attachment-less framebuffer reaching 32768×32768, above the stated Apple GPU limit of 16384.
- Release note: After a local workaround for device loss, a commenter reports that the 3D scene remains black while sound and subtitles work on an older Eglantine fork; current nx2 behavior was not yet checked.
- Release note: User reports a crash when opening the game on Arch Linux with an AMD Radeon AI PRO R9700 (9070XT); the console reports a segmentation fault.
- Release note: User reports audio/video desynchronization during the opening cutscene and a system freeze at the Deku Tree cutscene on Vulkan with an AMD RX 9000 series GPU. Comments report crashes on AMD GPUs, including while building shaders. One commenter reports that OpenGL GLSL stops the crashes but leaves only the UI visible.
- Release note: On some AMD GPUs, the UI may remain visible while the 3D world is black; reports also describe AMD driver timeouts or crashes.
- Release note: User-reported reproducible freeze when walking deeper into the pot room in Hyrule Castle Town, near the guard.
- Release note: The issue reporter using an AMD RX 6600 8GB on Windows 10 reports that the emulator starts loading and then remains on a black screen.
- Release note: Commenters report rendering failures, black screens, and AMD driver crashes; one reports that audio continues while rendering is crashed.
- Release note: On AMD's proprietary Windows driver, two compute pipelines can take 6 to 18 minutes to compile during the intro, leaving the game at 0 FPS while audio continues. Rejecting the shader hashes avoids the wait but causes black areas in the intro, title, and castle scenes.
- Release note: In the measurement-only experiment, disabling per-fence Preflushable downloads or batching downloads by 64 fences caused overexposure in Kokiri Forest.
- Release note: A commenter reports that an experimental compute storage write-extent analysis reduced marked GPU-written data and fence copies while preserving correct auto-exposure. It was described as code on a user's branch, not as an upstream or validated release fix.
- Release note: Static review and a separate research comment describe read-trap bookkeeping and dirty-state issues that can leave stale GPU-written data when per-fence downloads are disabled; proposed corrections and batching remain untested or local experiments.
- Release note: Slows when booting.
- Release note: Community comments describe AMD black or corrupted-world output, fragment-pipeline compiler crashes on Windows, later timeouts or TFB stalls, corrupted output, and a RADV depth-image SPIR-V failure. These are separate reported cases; the comments do not establish a universal cause or resolution.
- Release note: User reports a segfault during gameplay on Linux with an AMD RX 9000-series GPU and RADV, when a graphics pipeline is built for an invalid fragment shader.
- Release note: On Windows build-83, shutdown can hang at “Closing software…” after gameplay. Some sessions completed shutdown successfully; the cause is undetermined.
- Release note: Persistent graphics pipeline cache entries are reportedly rebuilt on the GPU thread during gameplay on repeated boots, causing a visible hitch.
- Release note: With GPU Mode: Accurate (High), gameplay may run in slow motion at about 30 FPS; shader compilation can cause stutter on new content.
- Release note: PGO artifact crashes in dynarmic with Unhandled SIGSEGV after 2–10 minutes on the reported machine.
- Release note: Clean audio from a different point of the game plays while the intro image is displayed; audio and picture are substantially out of sync.
- Release note: In gameplay, the world renders almost entirely black, with only the HUD and some areas near light sources visible; some shapes appear blown out with heavy bloom.
Compared with Previous Build
From build-83 to build-88: follow the gameplay changes described for these two builds.
Showing 61–61 of 61 reports
Known issues from Lichii sources
Known Game Issues
The Legend of Zelda: Ocarina of Time
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.
Star Fox
The emulator closes about a minute after gameplay begins on Windows 11 with an NVIDIA RTX 50 series GPU.
Hyrule Warriors
An error appears after the cinematic and remains on screen, blocking the view.
Other / not listed
Black screen during cinematic after the main menu appears; reported on Windows 11 with an AMD RX 6000 series or older GPU.
Starfox
Users report crashes before the training mission begins and during the campaign.
Other / not listed
Infinite startup launch loop when booting the .NUP version.
The Legend of Zelda: Ocarina of Time
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.
The Legend of Zelda: Ocarina of Time
A user reports severe shader problems with white visuals; handheld mode shows a black screen.
The Legend of Zelda: Ocarina of Time
A user reports a black screen past the title screen.
Starfox
A user reports repeated Unmapped Write64 errors, possible audio popping, and an emulation crash when closing the game.
Showing 81–90 of 98 issues
Notas de versão recentes
Mudanças na compatibilidade nas versões mais recentes
Versão build-88 · Não informado
Integrated performance ports and reduced unnecessary writer tracking; added explicit GPU-to-host visibility before buffer readback and submitted native desktop GPU work earlier while preserving conservative synchronization for macro reads and semaphore waits.
Versão build-88 · Não informado
Added bounded background preparation of cached graphics pipelines and persistent task/mesh shader state. Updated the Vulkan cache to v53 while preserving compatible v52 caches, and made interrupted cache migrations retryable.
Versão build-88 · Não informado
Fixed temporal history, motion interpolation, image transitions, and descriptor retirement for FSR3 frame generation; frame generation remains off by default.
Versão build-88 · Zelda: Ocarina of Time
Bundled Dark's Dynamic FPS mod, enabled by default for Ocarina of Time. Disable it independently in the game's Add-Ons settings. Max Resolution remains a separate Add-On. CPU Clock Normal is recommended when evaluating the mod; Boost/Overclock can affect game speed. Full gameplay timing has not been verified.
Versão build-83 · Ocarina of Time
Fixed missing vegetation, incorrect materials and lighting, a glowing doorway, one-frame white flashes, and an AMD black 3D scene. Added Max Resolution (built-in), enabled by default for the supported game build, and Ocarina-specific frame-ahead presentation tuning.
Escolha da versão
Qual versão devo usar?
build-83 · Publicada em November 6, 2026
The Legend of Zelda: Ocarina of Time
- runs with issues · GPU AMD Radeon RX 9060 XT 16 GB · CPU Intel i7-9700K · Driver AMD proprietary driver 32.0.32015.7029
12 arquivos para download nesta versão.
build-75 · Publicada em November 5, 2026
The Legend of Zelda: Ocarina of Time
- runs with issues · GPU RX 5700 · CPU Não informado · Driver amdvlk 32.0.21045.16010
- runs with issues · GPU AMD Radeon RX 7900 XTX · CPU Não informado · Driver AMD proprietary driver 2.0.416
12 arquivos para download nesta versão.
build-70 · Publicada em November 4, 2026
The Legend of Zelda: Ocarina of Time
- not booting · GPU NVIDIA GeForce RTX 3070 · CPU AMD Ryzen 7 5800X 8-Core Processor · Driver NVIDIA 621.1.0.0
12 arquivos para download nesta versão.
Experimente a versão mais recente disponível: build-88. Guarde uma versão que funcione para poder voltar a ela durante os testes.
Dúvidas sobre compatibilidade
Perguntas frequentes sobre compatibilidade de jogos
Como compartilho um jogo com esses filtros?
Aplique os filtros de jogo, status, GPU e versão e copie a URL da página. Um link para um jogo específico abre o cartão de relatos dele.
O que devo tentar se a tela ficar preta?
Confira nos outros relatos se o jogo chega aos menus ou se dá para jogar. Anote o driver e o renderizador e procure o jogo ou o erro no guia de solução de problemas.
Por que a mesma GPU pode apresentar resultados diferentes?
A versão do driver, as configurações gráficas, a carga da CPU e o trecho do jogo testado podem influenciar o resultado. Compare esses detalhes antes de alterar sua configuração.
Onde posso enviar um resultado que ainda não aparece aqui?
Use a lista oficial de issues do Lichii. Informe o jogo, a tag da versão, o hardware, o driver, as configurações e os passos para reproduzir o que você observou.