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 76 entrées par jeu et environnement, et 175 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 |
|---|---|---|---|---|
| Not provided | runs with issues | RX 5700 / Not provided | Not provided | Open report |
| Not provided | runs with issues | AMD Radeon RX 7900 XTX / Not provided | Not provided | Open report |
| Not provided | runs with issues | AMD Radeon RX 7900 XTX / Not provided | Not provided | Open report |
| nx2-build-88 (55532f2) | runs with issues | NVIDIA GeForce RTX 5060 (8 GB VRAM) / AMD Ryzen 5 5600G (6C/12T) | Not provided | Open report |
| nx2-build-93 | runs with issues | RTX 2060 6 GB / Xeon E5-1620 v3 (4C/8T) | Not provided | Open report |
Problems or notes: The local ClangCL build of b8c812b18 stalled at max present 8 and showed no frames. A local MSVC build of the same commit also stalled at max present 8 and died within a minute.
Problems or notes: User reports GPU hang or device loss when gameplay starts on local build 27226d2. A separate local build with #150 reverted, #127 kept, and docked mode reportedly avoids the hang and renders the full scene at about 24 FPS; another configuration without #127 renders only areas lit by Navi.
Problems or notes: A user reports a local 27226d2 build with #150 pointer-binding commits reverted ran for 5+ minutes past the point where the original build timed out; grass and trees were reportedly still missing.
Problems or notes: In a 1h 49m gameplay session, the reporter observed severe 1.3–6.59 second freezes, continuous frame-time micro-stutters, repeated GPU-thread shader translation stalls, and 579,265+ synchronous OnCPURead waits. The session had 0 crashes. Vulkan, 1x, GPU Mode Accurate, Async GPU and async shader compilation enabled, and Enable Reactive Flushing enabled.
Problems or notes: A user follow-up reports FPS averages falling from 53 in the first 10-minute bucket to about 23 in the 80–90-minute bucket during a 98-minute session with Reactive Flushing enabled, alongside 365,889 OnCPURead events and stalls over 2 seconds. In additional roughly 100-minute sessions, OnCPURead growth occurred with Reactive Flushing both on and off; with it off, FPS averages were 16–33 after the first 10 minutes and stalls reached 12 seconds, with one around 49 seconds. The reporter notes the comparison is not conclusive.
Current: build-83 (1 record); previous: build-75 (2 records).
Also listed as: OoT
| Build | Status | GPU / CPU | FPS | Details |
|---|---|---|---|---|
| build-93 | runs with issues | AMD Radeon RX 6900 XT / AMD Ryzen 9 5900X | 24–30 FPS | Open report |
| build-93 | runs with issues | RX 5700 (RDNA1) / Not provided | 10–24 FPS | Open report |
| build-93 | runs with issues | RX 7900XT / Ryzen 7 5700X3D | 25–55 FPS | Open report |
| build-93 | runs with issues | RX 9070 XT / Ryzen 7 9800X3D | 14–37 FPS | Open report |
| build-83 | runs with issues | RTX 5090 / Ryzen 7 9800X3D | 34.04–46.28 FPS | Open report |
Problems or notes: Severe lighting flickering and overexposure or corrupted lighting effects; significant slowdowns in some sequences; audio desynchronization during cinematics; initial shader compilation takes considerable time. The user reports approximately 24 FPS in Kokiri Forest and approximately 30 FPS in menus and some cinematics.
Problems or notes: User comment reports rendering and gameplay from the tree interior into Link's house without crashes, device loss, or fence timeouts. Reports 23–24 FPS in the first rooms and 14–15 FPS in Kokiri Forest; another session reports 22–24 FPS in the Deku Tree interior and Link's house. User characterizes performance as playable but not comfortable.
Problems or notes: User comment reports stable 25–30 FPS generally and spikes around 55 FPS indoors in close environments; no errors, crashes, or timeouts reported.
Problems or notes: User reports title-screen boot and gameplay through the intro into Kokiri Forest without crashes or driver timeouts. Reports slow motion because gameplay speed follows frame rate; heavy bloom and overexposure in bright areas, and the Great Deku Tree renders as a dark silhouette in its intro scene. FPS: approximately 18 by default, 17 with async shaders on and GPU accuracy Normal, 14 with async shaders on and GPU accuracy High, approximately 29 with logging filtered to errors, high process priority, and Xbox Game Bar capture off; intro cutscenes run 32–37 FPS.
Problems or notes: User report: Native gameplay remained below 60 FPS after shader warmup. Measurements varied by scene and settings; walking, camera movement, ladder climbing, NPC dialogue, autosave, and loading an outdoor save worked in a limited test. Audio was not assessed.
Current: build-93 (4 records); previous: build-88 (0 records).
Showing 51–60 of 114 reports
Known issues from Lichii sources
On build 93, FPS fluctuates approximately between 20 and 60, with frequent periods around 30 and drops to 25–28 FPS in the Dragon Layer; GameSir G7 Pro rumble can be excessive, occur without an obvious trigger, or continue longer than expected.
On an AMD Radeon RX 6700 XT with AMD Software (Adrenalin) 26.10.2, Lichii closes during the first shader rebuild after about 9-10 minutes; Event Viewer reports an access violation in amdvlk64.dll.
Constant 4 FPS in-game on AMD Radeon RX 570 4GB.
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.
The mountain on the way up to Zora's Domain following the river is invisible.
On a GPU without VK_EXT_mesh_shader, the user reports missing scene geometry during gameplay; mesh/task draws may be skipped and logged only as "Draw skipped (no pipeline)". The cause of the reported missing geometry was not confirmed on screen.
User reports a crash when loading a save on AMD RX 6000 series or older under Windows 11.
Rhythmic wavy effect on edges in the main area, described as depth of field toggling on and off.
A user reports sound glitches and improper rendering after booting Mario tennis.
User reports a GPU and emulator crash within seconds of starting Green Hat Kid on Linux with an AMD RX 9000 series graphics card, producing VK_ERROR_DEVICE_LOST.
Recorded fix: User reports that running with EDEN_NX2_NO_MESH=1 avoids the crash.
Showing 111–120 of 188 issues
Notes de version récentes
Version build-94 · Ocarina of Time
Version build-94 · Non renseigné
Version build-94 · Non renseigné
Version build-94 · Non renseigné
Version build-94 · Non renseigné
Choix d’une version
build-75 · Publiée le November 5, 2026
12 fichiers à télécharger pour cette version.
Essayez la dernière version disponible : build-94. 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é.