The Legend of Zelda: Ocarina of Time
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.
Compatibilidade de jogos
Tem um jogo em mente? Veja como ele roda no Lichii, confira os problemas conhecidos e escolha uma versão para testar.
Encontre um jogo
Os dados atuais incluem 76 registros de jogo e ambiente e 175 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
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 |
|---|---|---|---|---|
| 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 |
| nx2-build-88 (55532f2) | runs with issues | NVIDIA GeForce RTX 5060 (8 GB VRAM) / AMD Ryzen 5 5600G (6C/12T) | Not provided | Open report |
| nx2-build-93 | runs with issues | RTX 2060 6 GB / Xeon E5-1620 v3 (4C/8T) | Not provided | Open report |
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.
Problems or notes: In a 1h 49m gameplay session, the reporter observed severe 1.3–6.59 second freezes, continuous frame-time micro-stutters, repeated GPU-thread shader translation stalls, and 579,265+ synchronous OnCPURead waits. The session had 0 crashes. Vulkan, 1x, GPU Mode Accurate, Async GPU and async shader compilation enabled, and Enable Reactive Flushing enabled.
Problems or notes: A user follow-up reports FPS averages falling from 53 in the first 10-minute bucket to about 23 in the 80–90-minute bucket during a 98-minute session with Reactive Flushing enabled, alongside 365,889 OnCPURead events and stalls over 2 seconds. In additional roughly 100-minute sessions, OnCPURead growth occurred with Reactive Flushing both on and off; with it off, FPS averages were 16–33 after the first 10 minutes and stalls reached 12 seconds, with one around 49 seconds. The reporter notes the comparison is not conclusive.
Current: build-83 (1 record); previous: build-75 (2 records).
Also listed as: OoT
| Build | Status | GPU / CPU | FPS | Details |
|---|---|---|---|---|
| build-93 | runs with issues | AMD Radeon RX 6900 XT / AMD Ryzen 9 5900X | 24–30 FPS | Open report |
| build-93 | runs with issues | RX 5700 (RDNA1) / Not provided | 10–24 FPS | Open report |
| build-93 | runs with issues | RX 7900XT / Ryzen 7 5700X3D | 25–55 FPS | Open report |
| build-93 | runs with issues | RX 9070 XT / Ryzen 7 9800X3D | 14–37 FPS | Open report |
| build-83 | runs with issues | RTX 5090 / Ryzen 7 9800X3D | 34.04–46.28 FPS | Open report |
Problems or notes: Severe lighting flickering and overexposure or corrupted lighting effects; significant slowdowns in some sequences; audio desynchronization during cinematics; initial shader compilation takes considerable time. The user reports approximately 24 FPS in Kokiri Forest and approximately 30 FPS in menus and some cinematics.
Problems or notes: User comment reports rendering and gameplay from the tree interior into Link's house without crashes, device loss, or fence timeouts. Reports 23–24 FPS in the first rooms and 14–15 FPS in Kokiri Forest; another session reports 22–24 FPS in the Deku Tree interior and Link's house. User characterizes performance as playable but not comfortable.
Problems or notes: User comment reports stable 25–30 FPS generally and spikes around 55 FPS indoors in close environments; no errors, crashes, or timeouts reported.
Problems or notes: User reports title-screen boot and gameplay through the intro into Kokiri Forest without crashes or driver timeouts. Reports slow motion because gameplay speed follows frame rate; heavy bloom and overexposure in bright areas, and the Great Deku Tree renders as a dark silhouette in its intro scene. FPS: approximately 18 by default, 17 with async shaders on and GPU accuracy Normal, 14 with async shaders on and GPU accuracy High, approximately 29 with logging filtered to errors, high process priority, and Xbox Game Bar capture off; intro cutscenes run 32–37 FPS.
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.
Current: build-93 (4 records); previous: build-88 (0 records).
Showing 51–60 of 114 reports
Known issues from Lichii sources
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.
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.
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.
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.
On some AMD GPUs, the UI may remain visible while the 3D world is black; reports also describe AMD driver timeouts or crashes.
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.
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.
Showing 161–170 of 188 issues
Notas de versão recentes
Versão build-94 · Ocarina of Time
Versão build-94 · Não informado
Versão build-94 · Não informado
Versão build-94 · Não informado
Versão build-94 · Não informado
Escolha da versão
build-75 · Publicada em November 5, 2026
12 arquivos para download nesta versão.
Experimente a versão mais recente disponível: build-94. Guarde uma versão que funcione para poder voltar a ela durante os testes.
Dúvidas sobre compatibilidade
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.
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.
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.
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.