Other / not listed
User reports a crash at the first cutscene and emulator shutdown after compiling existing shaders on reboot.
Compatibilité des jeux
Compatibilité des jeux avec Lichii Emulator
Vous avez un jeu en tête ? Voyez comment il tourne dans Lichii, repérez les problèmes et choisissez une version à essayer.
Latest recorded build
build-117
Published November 7, 2026
Trouver un jeu
Rechercher des jeux compatibles avec Lichii
Les données actuelles comptent 108 entrées par jeu et environnement, et 308 rapports sur Lichii.
Un jeu manque ? Un résultat vide indique qu’aucun rapport sur ce jeu n’est encore répertorié pour Lichii. Cela ne signifie pas que le jeu a échoué à un test.
Consultez la plateforme indiquée pour distinguer les différentes versions d’un jeu.
Signification des statuts : « Unknown » : aucune conclusion. « Not booting » : le jeu ne démarre pas. « Boots » : seul le démarrage a été constaté. « Runs with issues » : des problèmes surviennent en jeu. « Playable » : la personne ayant testé le jeu a pu continuer à jouer.
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 Emblem Reported platform: unknown
| Build | Status | GPU / CPU | FPS | Details |
|---|---|---|---|---|
| build-65 | runs with issues | RTX 4060 (8gb) / AMD Ryzen 5 5600 6-Core Processor (3.50 GHz) | 30 FPS | Open report |
build-65 report
Statusruns with issues
GPURTX 4060 (8gb)
CPUAMD Ryzen 5 5600 6-Core Processor (3.50 GHz)
DriverNot provided
Recorded FPS30 FPS
Problems or notes: The user reported that the screen and camera began shaking during play.
Related game issues
- DLSS does not work in FE Fortune's Weave - no Game DLSS Network detection (open)
- [Crash] VK_ERROR_DEVICE_LOST, FEFW (Linux + AMD) (open)
- [GBug] Fire Emblem Fortunes Weave - FMVs Skipped/Do not play. (closed)
- Screen Shaking (Fire Emblem Fortune's Weave) (closed)
- Release note: A user reports that DLSS replacement does not detect the game's DLSS evaluation in Fire Emblem: Fortune's Weave: no Game DLSS network or NVIDIA DLSS (Streamline) line appears, while guest tensor operations run on cooperative matrices and GPU usage is high.
- Release note: On Linux with AMD graphics, Fire Emblem: Fortune's Weave can crash after a black screen with VK_ERROR_DEVICE_LOST and a GPU reset.
- Release note: A user reported that Fortunes Weave skips pre-rendered videos, including the opening cut-scene.
- Release note: Screen and camera shaking during play on build 65.
Compared with Previous Build
Current: build-70 (1 record); previous: build-65 (1 record).
Fire Emblem Reported platform: macOS
| Build | Status | GPU / CPU | FPS | Details |
|---|---|---|---|---|
| Eglantine nx2 build 34 (3140648) | runs with issues | M5 PRO 20 core gpu / M5 PRO 18 core | Not provided | Open report |
Eglantine nx2 build 34 (3140648) report
Statusruns with issues
GPUM5 PRO 20 core gpu
CPUM5 PRO 18 core
DriverNot provided
Recorded FPSNot provided
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).
Related game issues
- DLSS does not work in FE Fortune's Weave - no Game DLSS Network detection (open)
- [Crash] VK_ERROR_DEVICE_LOST, FEFW (Linux + AMD) (open)
- [GBug] Fire Emblem Fortunes Weave - FMVs Skipped/Do not play. (closed)
- Screen Shaking (Fire Emblem Fortune's Weave) (closed)
- Release note: A user reports that DLSS replacement does not detect the game's DLSS evaluation in Fire Emblem: Fortune's Weave: no Game DLSS network or NVIDIA DLSS (Streamline) line appears, while guest tensor operations run on cooperative matrices and GPU usage is high.
- Release note: On Linux with AMD graphics, Fire Emblem: Fortune's Weave can crash after a black screen with VK_ERROR_DEVICE_LOST and a GPU reset.
- Release note: A user reported that Fortunes Weave skips pre-rendered videos, including the opening cut-scene.
- Release note: Screen and camera shaking during play on build 65.
Compared with Previous Build
Fire Emblem Reported platform: Windows
| Build | Status | GPU / CPU | FPS | Details |
|---|---|---|---|---|
| nx2-build-117 | runs with issues | NVIDIA GeForce RTX 4090 / AMD Ryzen 7 9800X3D | Not provided | Open report |
nx2-build-117 report
Statusruns with issues
GPUNVIDIA GeForce RTX 4090
CPUAMD Ryzen 7 9800X3D
Driver617.14
Recorded FPSNot provided
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.
Related game issues
- DLSS does not work in FE Fortune's Weave - no Game DLSS Network detection (open)
- [Crash] VK_ERROR_DEVICE_LOST, FEFW (Linux + AMD) (open)
- [GBug] Fire Emblem Fortunes Weave - FMVs Skipped/Do not play. (closed)
- Screen Shaking (Fire Emblem Fortune's Weave) (closed)
- Release note: A user reports that DLSS replacement does not detect the game's DLSS evaluation in Fire Emblem: Fortune's Weave: no Game DLSS network or NVIDIA DLSS (Streamline) line appears, while guest tensor operations run on cooperative matrices and GPU usage is high.
- Release note: On Linux with AMD graphics, Fire Emblem: Fortune's Weave can crash after a black screen with VK_ERROR_DEVICE_LOST and a GPU reset.
- Release note: A user reported that Fortunes Weave skips pre-rendered videos, including the opening cut-scene.
- Release note: Screen and camera shaking during play on build 65.
Compared with Previous Build
Fire Emblem Reported platform: Linux
| Build | Status | GPU / CPU | FPS | Details |
|---|---|---|---|---|
| build 93 (09b78bd) | not booting | AMD RX 9000 series; RX9070XT / R5 3600 | Not provided | Open report |
build 93 (09b78bd) report
Statusnot booting
GPUAMD RX 9000 series; RX9070XT
CPUR5 3600
DriverNot provided
Recorded FPSNot provided
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.
Related game issues
- DLSS does not work in FE Fortune's Weave - no Game DLSS Network detection (open)
- [Crash] VK_ERROR_DEVICE_LOST, FEFW (Linux + AMD) (open)
- [GBug] Fire Emblem Fortunes Weave - FMVs Skipped/Do not play. (closed)
- Screen Shaking (Fire Emblem Fortune's Weave) (closed)
- Release note: A user reports that DLSS replacement does not detect the game's DLSS evaluation in Fire Emblem: Fortune's Weave: no Game DLSS network or NVIDIA DLSS (Streamline) line appears, while guest tensor operations run on cooperative matrices and GPU usage is high.
- Release note: On Linux with AMD graphics, Fire Emblem: Fortune's Weave can crash after a black screen with VK_ERROR_DEVICE_LOST and a GPU reset.
- Release note: A user reported that Fortunes Weave skips pre-rendered videos, including the opening cut-scene.
- Release note: Screen and camera shaking during play on build 65.
Compared with Previous Build
green-hat game Reported platform: Windows 10
| Build | Status | GPU / CPU | FPS | Details |
|---|---|---|---|---|
| build-93 | runs with issues | AMD RX 6000 series or older / Not provided | Not provided | Open report |
build-93 report
Statusruns with issues
GPUAMD RX 6000 series or older
CPUNot provided
DriverNot provided
Recorded FPSNot provided
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.
Related game issues
Compared with Previous Build
Current: build-93 (1 record); previous: build-88 (0 records).
green-hat kid adventure Reported platform: Linux (Debian)
| Build | Status | GPU / CPU | FPS | Details |
|---|---|---|---|---|
| c0a03141a4-nx2 | runs with issues | NVIDIA GeForce RTX 4060 Ti / Intel(R) Core(TM) i5-4690K CPU @ 3.50GHz | 20 FPS | Open report |
c0a03141a4-nx2 report
Statusruns with issues
GPUNVIDIA GeForce RTX 4060 Ti
CPUIntel(R) Core(TM) i5-4690K CPU @ 3.50GHz
DriverNot provided
Recorded FPS20 FPS
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.
Related game issues
Compared with Previous Build
Hyrule Warriors Reported platform: Windows 11
| Build | Status | GPU / CPU | FPS | Details |
|---|---|---|---|---|
| build-88 | runs with issues | nvidia rtx 40 series / Not provided | Not provided | Open report |
| build 75 (c9ebb5c) | runs with issues | AMD RX 9000 series; RX 9060 XT 16GB / Not provided | Not provided | Open report |
| 80 | runs with issues | NVIDIA RTX 40 series / Not provided | Not provided | Open report |
| Lichii Development Build | nx2-build-95 | runs with issues | AMD Radeon RX 6600 / AMD Ryzen 5 5600X | Not provided | Open report |
build-88 report
Statusruns with issues
GPUnvidia rtx 40 series
CPUNot provided
DriverNot provided
Recorded FPSNot provided
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.
Lichii Development Build | nx2-build-95 report
Statusruns with issues
GPUAMD Radeon RX 6600
CPUAMD Ryzen 5 5600X
DriverAMD proprietary driver 2.0.353, Vulkan 1.4.315
Recorded FPSNot provided
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!".
Related game issues
- [Crash] Memory exhaustion, then an unimplemented path (closed)
- [VBug] (closed)
- [VBug] (closed)
- Release note: On the reported Windows 11 setup with an AMD Radeon RX 6600, Vulkan logs VRAM memory-budget warnings and an unimplemented-path assertion before a crash after a few minutes of gameplay.
- Release note: Black screen with visible UI during gameplay in stages past the first one, while the world renders in the background when paused.
- Release note: An on-screen error appears after the cinematic and remains visible, blocking the view.
Compared with Previous Build
Current: build-88 (1 record); previous: build-83 (0 records).
Showing 21–30 of 308 reports
Known issues from Lichii sources
Known Game Issues
Other / not listed
Much of Gerudo does not render correctly, appearing like the skybox; resetting shaders reportedly changes it to physical forms and shapes with skybox textures.
The Legend of Zelda: Ocarina of Time Remake
User reports missing geometry, walls, buildings, and caves in the Great Deku Tree on a GTX 1070 Ti; the issue worsens deeper into the area.
Ocarina of Time
User reported sky-coloured holes in distant mountains of Hyrule Field on nx2 a7a28175 (same content as build-93) + local patches; a later user comment says they could no longer reproduce them on a newer local build.
Zelda Ocarina Of Time Remake
User reports excessive bloom outside the Great Deku Tree and invisible boxes and walls inside it.
The Legend of Zelda: Ocarina of Time Remake
Crashes after the intro sequence on an AMD GPU; another report describes a persistent driver crash with an RX 9070 XT.
The Legend of Zelda: Ocarina of Time (Switch 2)
Heavy stuttering during shader compilation, sometimes dropping to 0 FPS, with poor reported performance.
The Legend of Zelda: Ocarina of Time (Switch 2)
On Radeon RX 580 (Polaris / GCN4), the game hangs at 0 FPS with a black screen while building compute pipelines as the intro video starts.
The Legend of Zelda: Ocarina of Time
A commenter reports subsequent boots hang at Loading Shaders 25 / 27 with use_disk_shader_cache = true.
Recorded fix: Delete cache/shader/0400486024dec000 and set use_disk_shader_cache = false.
The Legend of Zelda: Ocarina of Time
A commenter reports a black screen after the intro on AMD, attributed in the comment to rejection of the game's 1080p upscaler shader.
Showing 221–230 of 361 issues
Notes de version récentes
Changements de compatibilité dans les dernières versions
Version 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.
Version 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.
Version build-116 · Zelda: Ocarina of Time
NVIDIA DLSS Super Resolution can replace the game's own upscaler on RTX cards; the setting is experimental.
Version 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.
Version build-116 · Mario Tennis Fever
The game runs fully at 60 fps, and texture glitches are fixed.
Choix d’une version
Quelle version utiliser ?
Choisissez un jeu ci-dessus pour voir quelles versions testées sont disponibles au téléchargement. En attendant, utilisez la dernière version disponible et lisez ses notes.
Essayez la dernière version disponible : build-117. Gardez une version fonctionnelle sous la main pendant vos essais.
Questions sur la compatibilité
FAQ sur la compatibilité des jeux
Comment partager un jeu avec ces filtres ?
Appliquez les filtres de jeu, de statut, de GPU et de version, puis copiez l’URL de la page. Un lien vers un jeu précis ouvre sa fiche.
Que faire si j’obtiens un écran noir ?
Vérifiez dans d’autres rapports si le jeu atteint les menus ou une partie jouable. Notez votre pilote et le moteur de rendu, puis recherchez le jeu ou l’erreur dans le guide de dépannage.
Pourquoi un même GPU peut-il donner des résultats différents ?
La version du pilote, les réglages graphiques, la charge du processeur et la partie du jeu testée peuvent influer sur le résultat. Comparez ces détails avant de modifier votre configuration.
Où puis-je soumettre un résultat manquant ?
Utilisez le suivi officiel des tickets de Lichii. Indiquez le jeu, le tag de la version, le matériel, le pilote, les réglages et les étapes pour reproduire ce que vous avez observé.