The Legend of Zelda: Ocarina of Time (Switch 2)
User reports that rejecting shader programs containing native opcode 0x4a4 avoids a Metal page fault, but may leave the run stalled at the end of the video with semaphore waits and GPU-thread abort.
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 108 registros de jogo e ambiente e 308 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.
Also listed as: Ocarina of Time, Zelda: Ocarina of Time, OoT, Zelda OoT, TLoZ: OoT
| Build | Status | GPU / CPU | FPS | Details |
|---|---|---|---|---|
| Not provided | playable | Not provided / Not provided | Not provided | Open report |
| Not provided | runs with issues | 1080 Ti / Ryzen 5600X | Not provided | Open report |
| Not provided | runs with issues | GTX 1050 Ti / 7th gen i5 | 18–27 FPS | Open report |
| Not provided | playable | RTX 3070 Ti / Ryzen 7 2700X | Not provided | Open report |
| build-95 (`nx2-build-95`) | runs with issues | RTX 4060 Laptop, 8 GB, 45 W max power limit / Intel Core i7-12650H (6P+4E, 16 threads) | 9.4–51.4 FPS | Open report |
| build 95 | runs with issues | Radeon 890M / Ryzen AI Z2 Extreme | 23–25 FPS | Open report |
| build 117 (PGO) | runs with issues | Radeon 890M / Ryzen AI Z2 Extreme | 42–44 FPS | Open report |
| nx2-build-95 | runs with issues | NVIDIA GeForce RTX 2070 / Intel Core i7-12700KF | Not provided | Open report |
| Not provided | not booting | NVIDIA GeForce RTX 3050 / Not provided | Not provided | Open report |
| build 88 and 93 | runs with issues | GTX 1060 6gb / Ryzen 5 5600 | Not provided | Open report |
Problems or notes: A commenter says everything works on their Mac with the latest main branch; hardware and build details are not stated.
Problems or notes: A commenter reports objects and doors failing to appear.
Problems or notes: A commenter reports invisible push blocks, making progress difficult.
Problems or notes: A commenter reports testing the draft shader warm-up and says first-visit freezes were gone. The comment gives no broader gameplay or session-duration evidence.
Problems or notes: User reports multi-second stalls while draws are held for unbuilt pipelines with async shaders enabled; in about 8 minutes, mean performance was 25.8 fps and six present windows had a maximum frame time over 1 s (worst 4.9 s). A fresh config used slow defaults and ran at 10–15 fps with stalls up to 8.9 s and blurry/pixelated Handheld resolution. Settings for the measured build-95 session were GPU accuracy Low, async shaders and async presentation enabled, Docked, 8 GB memory layout, and NVDEC GPU. The report also describes Frizti v3 behavior separately: it skipped draws with no pipeline, averaging 26.0 fps in 30-fps mode (range 16.4–30), with revisits at 30.0 fps and no frames over 100 ms.
Problems or notes: The intro, Deku Tree cutscene, and initial gameplay rendered correctly, but the game froze at 0 FPS when Navi passed the Kokiri guard on the path to the Deku Tree. The report mentions texture format asserts and Unmapped Device ReadBlock errors.
Problems or notes: The intro and cutscenes ran at 42–44 FPS and the game reached Kokiri Forest, but Unmapped Device ReadBlock errors and multi-second stalls were followed by a hard freeze before Navi reached the guard. The same errors occurred with memory layout set to both 12 GB and 4 GB.
Problems or notes: User reports that after the Kaepora Gaebora cutscene near Hyrule Castle, the area appears empty and foggy, Link falls through the world, and repeated void-outs prevent progression. Reported on Windows 11 25H2 in Handheld mode with Vulkan. The user says the issue reproduces 100% with the same save; listed configuration changes and disabling a built-in patch did not fix it.
Problems or notes: Crashes during boot about 9–13 seconds after launch, after presenting its first frame, at an unimplemented nx2:vi2 function 201. The same crash is reported on builds 93 and 95.
Problems or notes: A commenter reports missing textures in the Deku Tree after loading a save, across two game versions and builds 88 and 93. They also report that it worked the first time.
Current: build-117 (2 records); previous: build-116 (0 records).
Showing 171–180 of 308 reports
Known issues from Lichii sources
User reports that rejecting shader programs containing native opcode 0x4a4 avoids a Metal page fault, but may leave the run stalled at the end of the video with semaphore waits and GPU-thread abort.
Dynamic FPS does not maintain normal game speed at 30-40 FPS; another report says gameplay speeds up at 30 FPS when CPU Clocks is set to Boost.
Recorded fix: Set CPU Clocks to Normal to resolve the sped-up gameplay reported with Boost enabled.
With an AMD RX 9000 series graphics card on Windows 11, the game crashes as the Great Deku Tree cutscene is about to begin, showing a black screen and an AMD driver timeout. A commenter reports a similar crash with AMD graphics on Linux.
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.
A user reports a crash when launching the game; the log reports failed backing-memory and fallback-buffer allocation.
With GPU Mode: Accurate, gameplay runs at about 30 fps and in slow motion; the commenter attributes this to the GPU thread split not starting at high GPU accuracy. Shader pipeline builds can also cause stutter on new content.
Recorded fix: The commenter reports that changing GPU Mode to Fast resolved the slow-motion speed issue for them. For shader-build stutter, they report that an opt-in EDEN_NX2_ASYNC_DISCARD=1 skips draws while pipelines build.
Black video on the PGO build; the game works well on MSV.
A commenter reports crashes with AMD graphics cards related to mesh shaders and says a similar issue occurs on Windows and Linux.
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.
Recorded fix: Set EDEN_NX2_FRAMES_AHEAD=0. The reporter found this stopped the dialogue panel flicker, with a frame-rate cost; another reporter said the remaining occasional flicker was rare and could not be reproduced on demand.
Black screen with visible UI during gameplay in stages past the first one, while the world renders in the background when paused.
Showing 291–300 of 361 issues
Notas de versão recentes
Versão build-117 · Ocarina of Time
Versão build-116 · Zelda: Ocarina of Time
Versão build-116 · Zelda: Ocarina of Time
Versão build-116 · Zelda: Ocarina of Time
Versão build-116 · Mario Tennis Fever
Escolha da versão
Escolha um jogo acima para ver quais versões testadas estão disponíveis para download. Enquanto isso, baixe a versão mais recente disponível e leia as notas dela.
Experimente a versão mais recente disponível: build-117. 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.