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
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.
Fire EmblemReported platform: unknownruns with issues2 reports
Problems or notes: The user reported that audio played and the game was interactive, but the render was completely black. A later user comment said rendering seemed fixed in Eglantine nx2 build 129 (a407703).
Problems or notes: A user reports entering gameplay but no Game DLSS network detection or NVIDIA DLSS evaluation; the game's tensor operations instead run on cooperative matrices, with higher GPU usage. They report this on a copy of Fire Emblem: Fortune's Weave, update version 1.0.
Problems or notes: Fire Emblem: Fortune's Weave shows a black screen and then crashes with VK_ERROR_DEVICE_LOST. The issue reporter says it does not happen on Windows on the same system. A commenter reports the crash persists in Lichii build 95.
Problems or notes: ZL input is not detected during the shield tutorial, leaving it stuck in a loop. Rebinding ZL to L or using the keyboard does not resolve the issue.
Problems or notes: The user reports black 3D content in docked mode while the GUI overlay and main menu render. Handheld mode renders the game. The user reports approximately 20 FPS after reboot, the same as the last build, and says this is lower than build 88.
Problems or notes: A commenter reports the same bug at the start.
build 75 (c9ebb5c) report
Statusruns with issues
GPUAMD RX 9000 series; RX 9060 XT 16GB
CPUNot provided
DriverNot provided
Recorded FPSNot provided
Problems or notes: An on-screen error appears after the cinematic and remains visible, blocking the view.
80 report
Statusruns with issues
GPUNVIDIA RTX 40 series
CPUNot provided
DriverNot provided
Recorded FPSNot provided
Problems or notes: In stages past the first one, the screen is black while the UI remains visible; when paused, the world renders in the background. The reporter says it worked on older builds of eglantine.
Problems or notes: User reports a crash after a few minutes when moving between areas or into a large open field. The log shows images exceeding the VRAM memory budget, use of an unbacked sparse image, and an assertion at texture_cache.h:2710: assert false && "Unimplemented!".
A user reports a freeze about 40 seconds after boot, with texture rendering failure and overbright world brightness beforehand. A dump showed GPUBack waiting on the guest page table lock while in the texture garbage collector; the user suspects a lock cycle.
Other / not listed
The mountain on the way up to Zora's Domain following the river is invisible.
Donkey Kong Bananza
User reports a crash when loading a save on AMD RX 6000 series or older under Windows 11.
Splatoon Raiders
Rhythmic wavy effect on edges in the main area, described as depth of field toggling on and off.
Other / not listed
A user reports sound glitches and improper rendering after booting Mario tennis.
The Legend of Zelda: Ocarina of Time Remake
Crashes at the same moment as it flies under the user's feet; the log reports an application error in amdvlk64.dll.
Ocarina of Time
User reports freezing while loading a game and a subsequent emulator crash on macOS; in Build 93, pressing A on a controller reportedly does nothing when attempting to return to the title screen.
Other / not listed
The game start cutscene renders only in the bottom half on an RX 6800.
Donkey Kong Bananza
A VP9 video reaching end of stream triggers error 2111-3604 and freezes emulation; the video panel appears as a solid yellow box in stable-1.0.0.
Donkey Kong Bananza
User reports the game is locked at 20 FPS, including menus and title screen, on Windows 11.
Showing 271–280 of 361 issues
Notas de versão recentes
Mudanças na compatibilidade nas versões mais recentes
Versão build-117 · Ocarina of Time
Fixed a crash during shader building on Windows drivers for RX 6000 (RDNA2), RX 5000 (RDNA1), Vega, and Polaris cards. The faster matrix path now runs only on RDNA3 and newer.
Versão build-116 · Zelda: Ocarina of Time
Ocarina of Time is described as very stable; foliage and Hyrule Field grass rendering are fixed, and many users get 60+ fps.
Versão build-116 · Zelda: Ocarina of Time
NVIDIA DLSS Super Resolution can replace the game's own upscaler on RTX cards; the setting is experimental.
Versão build-116 · Zelda: Ocarina of Time
A new option turns off the game's sharpening anti-aliasing; the default Game setting behaves as before, and DLSS takes priority if both are enabled.
Versão build-116 · Mario Tennis Fever
The game runs fully at 60 fps, and texture glitches are fixed.
Escolha da versão
Qual versão devo usar?
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
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.