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 |
|---|---|---|---|---|
| build-70 | playable | Not provided / M4 Pro | 30–38 FPS | Open report |
| tag/build-65 | not booting | Other / Not provided | 10 FPS | Open report |
Problems or notes: The report says races measured 30–38 fps after macOS performance work.
Problems or notes: Crashes after the loading splash. The issue report says a workaround bypassed the crash but resulted in 10 fps.
Current: build-70 (1 record); previous: build-65 (0 records).
| Build | Status | GPU / CPU | FPS | Details |
|---|---|---|---|---|
| build-117 | runs with issues | NVIDIA RTX 30 series or older / Not provided | Not provided | Open report |
| build-116 | playable | Not provided / Not provided | 60 FPS | Open report |
Problems or notes: The user reports that characters have no shadows.
Problems or notes: Not provided
Current: build-117 (1 record); previous: build-116 (1 record).
| Build | Status | GPU / CPU | FPS | Details |
|---|---|---|---|---|
| build 88 (55532f2), also reproducible on build 75 | runs with issues | NVIDIA GeForce RTX 3050 Ti Laptop GPU / 12th Gen Intel(R) Core(TM) i7-12700H | Not provided | Open report |
Problems or notes: The game reaches a controller screen, but a two-player motion game cannot start: it remains on “Playing with 1 Joy-Con” and reports that the Joy-Con connection was lost. The issue reporter's log shows controller type 5 is unsupported and the emulator disconnects the controller; it also logs no response from a Joy-Con. The left Joy-Con's battery level is not reported. These are user reports, not maintainer-confirmed findings.
| Build | Status | GPU / CPU | FPS | Details |
|---|---|---|---|---|
| build-117 | runs with issues | Other / Apple M1 | 1 FPS | Open report |
Problems or notes: Boots and plays audio, but the image is completely black from startup; intermittent red/green block artifacts are reported. Approximately 1 FPS.
Current: build-117 (1 record); previous: build-116 (0 records).
| Build | Status | GPU / CPU | FPS | Details |
|---|---|---|---|---|
| build 115 | runs with issues | RTX 5070 / Ryzen 5700x | Not provided | Open report |
| build 116 (PGO) | runs with issues | RX 9070 XT / Not provided | 60 FPS | Open report |
Problems or notes: Grass vanishes when swinging the sword.
Problems or notes: User reports that after 9000-frame eviction of preloaded pipelines, runtime builds caused draws to be held for up to 8 seconds per 10-second window and a 19-second freeze. The user says disabling eviction locally kept the game smooth; this is a user workaround, not a confirmed fix.
| Build | Status | GPU / CPU | FPS | Details |
|---|---|---|---|---|
| build-83 | playable | RTX 4070 Ti / Ryzen 7 7700X | Not provided | Open report |
| 55532f2d814215aaf32a76c214cf129f2cb6282b | runs with issues | RTX 5060 Ti / Ryzen 7 7800X3D | 15–51 FPS | Open report |
Problems or notes: In a tested docked 2x gameplay run, haze was gone and Link and Kokiri Forest were clearly visible without shader rejections. FPS was described as low, with no value stated.
Problems or notes: Foliage, grass, shadows, and atmosphere were reported as substantially improved, and the Great Deku Tree exterior dialogue and interior corridor rendered visibly. Some eastern outdoor views remained severely white/yellow and washed out. Outdoor performance varied from 28–31 FPS in other views to about 15 FPS in problematic areas; the Deku Tree exterior dialogue showed 36 FPS and the interior showed 51 FPS. Texture-format and texture-index assertions were logged; one earlier Accurate attempt exited with code -1073740791, while a later session ran about 20m31s and exited normally. No causal link between assertions, lighting, or the earlier crash was established.
From build-75 to build-83: follow the gameplay changes described for these two builds.
Before: Missing vegetation and incorrect material data; affected lighting and colours; a glowing doorway; one-frame white flashes; and on AMD, shaders could produce a black 3D scene.
After: Additional shader pointers and storage-buffer bindings, corrected buffer tracking and mesh-shader register handling, fixed occlusion-query and nested-return handling, and added the Max Resolution add-on and frame-ahead presentation tuning.
build-75 → build-83
Showing 51–60 of 308 reports
Known issues from Lichii sources
On AMD Radeon RX 9070 XT with driver 2.0.416, a dotted cyan/magenta line appeared along mountain and sky silhouettes in Hyrule Field.
Recorded fix: Zero the color write mask of render targets the fragment shader does not store; the issue comment says this fix landed in build 95.
Coloured blocks or a magenta line along the Hyrule Field mountain ridge on AMD GPUs; the original report described NaNs in the scene target that bloom spread into a coloured band.
Recorded fix: The #353 per-component write-mask fix was reported to remove the coloured blocks or line. A temporary workaround is to set EDEN_NX2_REJECT_HASH=fe1f903f1bf52a9d,4f5673eca06ebecb, which drops the draw and loses its far-distance effect.
Distant mountains remain overexposed with a white glow after the coloured blocks are removed; the source identifies this as a separate bloom/exposure issue.
On Linux with AMD RX 9000-series graphics using RADV, an invalid SPIR-V fragment shader can cause a segfault during Vulkan graphics-pipeline construction during gameplay.
Recorded fix: Fixed in build 93 and later releases.
On AMD's proprietary Windows Vulkan driver, the intro could freeze while two compute shaders were optimized, taking 6–18 minutes; long graphics-pipeline builds can also cause substantial in-game stalls.
Recorded fix: Build 93 and later build the two identified compute shaders without driver optimization on AMD's proprietary Vulkan driver. The source says long graphics-pipeline builds are a separate matter and are not covered.
On earlier builds, small details such as leaves, pebbles, and grass flickered or appeared black with Low GPU accuracy and the split GPU thread enabled.
Recorded fix: Update to build 95 or later; the source attributes the fix to buffer usage tracking changes, with additional near-foliage fixes. EDEN_NX2_PERF_VERIFY=1 was an earlier workaround but was reported as no longer needed on build 95.
A user reports that games do not work on a Lenovo Legion Go 2 Z2 with an eGPU 7600xt on Version 95; on Version 93 or earlier, they can see the scene.
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.
On Windows 11, extracting a NUP to a path longer than 260 characters fails even when LongPathsEnabled is set. The issue reports a malformed longPathAware manifest entry as the probable cause.
AV1 cinematics are delayed, with audio playing faster.
Showing 161–170 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é.