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: OoT, Ocarina of Time, OOT REMAKE
| Build | Status | GPU / CPU | FPS | Details |
|---|---|---|---|---|
| nx2 fork at 99ac3d5955 with local patches (commit 1e53321757) | runs with issues | RTX 5080 / Ryzen 9 7950X3D | Not provided | Open report |
| 09b78bd2df | runs with issues | GTX 1070 / Not provided | Not provided | Open report |
| Not provided | runs with issues | GTX 1070 / Not provided | Not provided | Open report |
| a7a281757da390ce45070e772784e0333831bb25 | runs with issues | NVIDIA GeForce GTX 1080 / AMD Ryzen 9 3900X | Not provided | Open report |
| build-95 | runs with issues | RTX 4070 Ti SUPER / Not provided | Not provided | Open report |
| 95 | not booting | AMD Radeon RX 7900 XTX (RADV) / Intel Core i7-11700K | 0 FPS | Open report |
| Build 95 | not booting | AMD Radeon RX 5700 XT (RADV NAVI10) / AMD Ryzen 5 3600 6-Core Processor | Not provided | Open report |
| Build 95 | not booting | NVIDIA GeForce RTX 3050 Laptop GPU / i5-12500H | Not provided | Open report |
| nx2 @ 89440b29a9 | runs with issues | Not provided / Not provided | Not provided | Open report |
Problems or notes: A user comment reports a median frame time of 22.4 ms in Kokiri Forest and CPU time concentrated on the GPUBack thread, with the GPU front thread mostly waiting. This is a user measurement, not an official compatibility result.
Problems or notes: A merged user report says a door and most vegetation are missing. It attributes the symptom to mesh-shader pipelines being skipped when VK_EXT_mesh_shader is unavailable; the reporter could not confirm on screen that the missing objects corresponded exactly to those draws.
Problems or notes: A draft compute-based fallback reportedly rendered falling leaves, ground leaves, and some foliage shadows with correct textures, but the emulated geometry flickered and canopies, grass, and house walls remained missing.
Problems or notes: Missing leaves, foliage, walls, textures, and other geometry. The report says attempted recompilation and builds 78, 88, 92, Fritzi v2, and perf/Fritzi-Intergrated did not resolve the issue; comments report that #395, #434, and #430 did not restore the geometry.
Problems or notes: Large flat red patches appear across the wet stream bed by the road from Castle Town Market to Hyrule Castle. Another user later reported that stream as clean with their build, attributing the earlier difference possibly to missing #432 and #351; this report's setup used build-95.
Problems or notes: Stalls at a black screen; repeated native MME macro execution failures are reported. Enabling compute pipelines, clearing pipeline caches, and disabling implicit Vulkan layers did not resolve the issue.
Problems or notes: A user-provided build-95 log shows the game loading, followed by a compute pipeline compilation error and an unhandled SIGSEGV. The user later supplied crash details indicating a null-pointer dereference. The log identifies KDE neon User Edition as the host OS.
Problems or notes: Black screen at the intro video after the loading shaders screen; music continues, FPS counter stays at 0, and GPU channels wait on unreleased semaphores. Build 93 reaches gameplay on the same machine. Two other users report the same build 95 hang on Linux with NVIDIA RTX 3060 and RTX 3090 systems. Two users say EDEN_NX2_SPLIT=1 makes the game work.
Problems or notes: User reports that motion controls are affected: Motion 1/Motion 2 mapping does not detect shaking, and gyro/accelerometer input stops after the controller reconnects or after a few seconds with Steam running.
Current: build-93 (3 records); previous: build-88 (0 records).
Also listed as: OoT
| Build | Status | GPU / CPU | FPS | Details |
|---|---|---|---|---|
| Not provided | not booting | AMD Radeon RX 6700 XT (12 GB) / AMD Ryzen 9 5900X | Not provided | Open report |
Problems or notes: On first launch, shader rebuild runs for about 9-10 minutes, then Lichii closes with no error message. The reported Event Viewer faulting module is amdvlk64.dll with exception code 0xc0000005.
Showing 91–100 of 194 reports
Known issues from Lichii sources
On Windows 11, connecting an official Nintendo Switch Pro Controller while Lichii is open reportedly floods the host OS with phantom inputs, making desktop mouse clicks unresponsive and keyboard typing erratic. Unplugging the controller reportedly restores normal input.
With Dual Joy-Cons, the game remains on the “Playing with 1 Joy-Con” screen and reports a lost connection, preventing a two-player motion game from starting. The issue reporter's log includes an unsupported controller type disconnection and a Joy-Con sub-command timeout.
Walls and objects are missing/not rendered inside the Deku tree.
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.
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.
Recorded fix: Use a local non-PGO build with PR #345 merged; the reporter confirmed white flashes were gone after several minutes in the Deku Tree interior.
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.
Recorded fix: The reporter found that keeping float16 on improved the measured busy-view performance; this is a user-reported workaround.
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 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.
Plants and bushes in the Castle appear dead up close, while bushes render correctly at a distance.
On Linux, the game froze near the title screen, followed by pixel artefacts and a system crash.
Recorded fix: The user reported that EDEN_NX2_NO_MESH=1 allowed the game to reach the menus, but Grand Prix did not start successfully.
Showing 181–190 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
Nenhuma versão testada com download disponível está associada a Ocarina of Time. Consulte as versões atuais ou veja a discussão na issue do jogo.
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.