Compatibilité des jeux
Vous avez un jeu en tête ? Voyez comment il tourne dans Lichii, repérez les problèmes et choisissez une version à essayer.
Trouver un jeu
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
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 |
|---|---|---|---|---|
| 4.1 | runs with issues | NVIDIA RTX 40 series / Not provided | Not provided | Open report |
Problems or notes: When gameplay begins, graphics remain a black screen while the UI and button prompts work. The cutscene and opening title display correctly.
| Build | Status | GPU / CPU | FPS | Details |
|---|---|---|---|---|
| build-70 | runs with issues | Not provided / Not provided | Not provided | Open report |
| nx2-build-88 | runs with issues | AMD BC-250 (Oberon APU) — RADV GFX1013 / Not provided | 37 FPS | Open report |
Problems or notes: Some textures are still black, and it can crash later in play.
Problems or notes: Reaches gameplay and remains responsive, but the 3D scene is black while the HUD renders. Three graphics programs are rejected, causing draws to be skipped; compute shader dispatches are also rejected. The reported frame time is approximately 37 fps.
Current: build-70 (1 record); previous: build-65 (0 records).
| Build | Status | GPU / CPU | FPS | Details |
|---|---|---|---|---|
| build-93 | runs with issues | RX 9060 XT 16 GB / i7-9700K | 19–36 FPS | Open report |
Problems or notes: A user reports that frame_gen and game_dlss_network enabled caused a near-white presented frame; setting both to false produced a correct image. White flashes were associated with async_presentation=true; async_presentation=false reduced white pixels in a 40-frame capture to 0.2% but lowered performance to about 19-25 FPS in a heavy Kokiri scene. The approximately 36 FPS result required async presentation, which flashed.
Current: build-93 (1 record); previous: build-88 (0 records).
| Build | Status | GPU / CPU | FPS | Details |
|---|---|---|---|---|
| nx2-build-75 [PGO] | not booting | AMD Radeon RX 6650 XT (RDNA2) / Intel Core i5-10400F | Not provided | Open report |
| nx2-build-83 | runs with issues | Radeon RX 6800 / Not provided | 43–47 FPS | Open report |
Problems or notes: The render area stays black after boot in both handheld and docked modes. The reporter also tried build 75 and pre-release #80; the black screen persisted. The associated comment describes the game ID as 0400486024DEC000.
Problems or notes: The reporter says the game renders correctly in a screen capture, including the title screen, logo, and menu, but the presented display is solid green. They report about 43 fps from presents and a 47 fps OSD in the capture.
| Build | Status | GPU / CPU | FPS | Details |
|---|---|---|---|---|
| build-83 | runs with issues | RX 9060 XT 16 GB / Not provided | Not provided | Open report |
| build-75 | not booting | AMD RX 6000 series or older / Not provided | Not provided | Open report |
Problems or notes: The reporter says the black-screen issue is gone and the game reaches gameplay, but the device is lost at gameplay start with VK_ERROR_DEVICE_LOST, followed by a crash.
Problems or notes: The reporter says the game boots with sound and the Zelda logo, then remains on a black screen.
Current: build-83 (1 record); previous: build-75 (1 record).
Also listed as: OoT, Zelda, Ocarina of Time
| Build | Status | GPU / CPU | FPS | Details |
|---|---|---|---|---|
| build-93 | boots | RX 9060XT 16GB / Ryzen 5 7600 | Not provided | Open report |
| Lichii nx2 build 93 (09b78bd) | runs with issues | AMD RX 9070XT / Not provided | 30–40 FPS | Open report |
Problems or notes: A commenter reports that starting with Accurate GPU enabled loaded the main menu; audio had issues. They say settings could sometimes be changed back, but the issue could recur.
Problems or notes: Initially crashed after the screen went black while loading into the game. With EDEN_NX2_NO_MESH=1, it reached Link's house at 30-40 fps, but walls and other geometry were missing and there were shading issues.
Current: build-93 (1 record); previous: build-88 (0 records).
Showing 271–280 of 308 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
Notes de version récentes
Version build-117 · Ocarina of Time
Version build-116 · Zelda: Ocarina of Time
Version build-116 · Zelda: Ocarina of Time
Version build-116 · Zelda: Ocarina of Time
Version build-116 · Mario Tennis Fever
Choix d’une version
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é
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.
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.
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.
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é.