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 58 entrées par jeu et environnement, et 114 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-75 | runs with issues | RTX 5070 Ti / Not provided | Not provided | Open report |
| 99ac3d595 plus listed cherry-picked commits | playable | RTX 5070 Ti / Not provided | 38 FPS | Open report |
Problems or notes: Docked, 1x. User reported missing vegetation, heavy white glow, and visual blotches in tested scenes. Rejecting shaders with EDEN_NX2_REJECT_HASH visibly improved Link and the foreground, but removed bloom accumulation and the river surface.
Problems or notes: Docked, 1x, in front of the Deku Tree in Kokiri Forest. Grass and ferns drew and the heavy haze was gone in a short, still-camera test. Other areas, interiors, cutscenes, long sessions, river rendering, and blotches were not verified. User reported about 38 FPS.
Current: build-75 (1 record); previous: build-70 (0 records).
| Build | Status | GPU / CPU | FPS | Details |
|---|---|---|---|---|
| Frizti v2 (oot-gather-fix @ 765659a) plus port of #204 | runs with issues | NVIDIA RTX 3090 / Ryzen 9 9950X3D | Not provided | Open report |
Problems or notes: Linux 7.0, Vulkan, GPU accuracy Low, docked, 1x, async shaders on. User reported river-water flicker that depended on the sun's position relative to the camera.
| Build | Status | GPU / CPU | FPS | Details |
|---|---|---|---|---|
| nx2 with extra PRs | runs with issues | RX 6650 XT / Not provided | Not provided | Open report |
Problems or notes: Handheld, 1x. During gameplay, user observed zero-format texture assertions and Unmapped Device ReadBlock errors; terrain and subtitles flickered. The user did not establish whether the assertions caused the flicker.
| Build | Status | GPU / CPU | FPS | Details |
|---|---|---|---|---|
| build-83 | playable | RTX 4070 Ti / Ryzen 7 7700X | Not provided | Open report |
| 3724db9a5c | playable | RTX 4070 / i9-12400F | 16 FPS | Open report |
Problems or notes: Vulkan, docked, 2x, GPU accuracy Low, game version 1.1. User reported haze gone and Link and Kokiri Forest clearly visible in gameplay, but FPS was described as low. Handheld mode was not tested.
Problems or notes: Vulkan, docked, 1x. User reported grass visible and the tree clearly visible through grey fog in front of the Deku Tree; 16 FPS was a single in-game counter reading.
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
| Build | Status | GPU / CPU | FPS | Details |
|---|---|---|---|---|
| 8813b44 | runs with issues | RX 6800 XT / Not provided | Not provided | Open report |
Problems or notes: At 1x in Link's house and Kokiri Forest, user reported blotches from a half-resolution layer. A diagnostic depth-clear change removed the blotches in Link's house, but the river water remained dark with ripples and no visible lit contribution.
| Build | Status | GPU / CPU | FPS | Details |
|---|---|---|---|---|
| build-80 | runs with issues | AMD RX 6700 XT / Not provided | Not provided | Open report |
Problems or notes: Docked, 1x. The opening cinematic and title screen rendered correctly, but the Deku Tree exterior cutscene remained black except for Navi's light radius. User also reported a deterministic AMD driver crash while building graphics pipelines in that scene.
| Build | Status | GPU / CPU | FPS | Details |
|---|---|---|---|---|
| 62ba83427e | runs with issues | Radeon 8060S / Ryzen AI MAX+ 395 | 31–37 FPS | Open report |
Problems or notes: Docked, 1x, Kokiri Forest. User reported haze, blotches, and a translucent band. Rejecting fog and layer shaders removed some artifacts but also removed in-game fog and darkened the river. Two starts remained black from launch, one with music playing; closing and reopening cleared the black screen.
| Build | Status | GPU / CPU | FPS | Details |
|---|---|---|---|---|
| b4716fc | runs with issues | RX 6700 XT / Not provided | Not provided | Open report |
Problems or notes: Docked, 1x. The Deku Tree exterior cutscene showed a black screen except for a small circle around Navi; the title screen and earlier cinematics rendered correctly.
Showing 1–10 of 77 reports
Known issues from Lichii sources
User reports audio/video desynchronization during the opening cutscene and a system freeze at the Deku Tree cutscene on Vulkan with an AMD RX 9000 series GPU. Comments report crashes on AMD GPUs, including while building shaders. One commenter reports that OpenGL GLSL stops the crashes but leaves only the UI visible.
On some AMD GPUs, the UI may remain visible while the 3D world is black; reports also describe AMD driver timeouts or crashes.
User reports a performance regression in Build 75 on Linux with an AMD RX 6000 series or older GPU: around 10 FPS on the title screen, barely reaching 15 FPS with constant stuttering, GPU usage at 100%, and RAM usage increasing nonstop.
Only character outlines and UI are visible after launching the game.
User-reported reproducible freeze when walking deeper into the pot room in Hyrule Castle Town, near the guard.
Shrubbery, bushes, and grass turn dead-looking when approached in Hyrule Castle, especially in Zelda's garden. A user reports that it still occurs in build 83.
User reports describe gameplay performance below 60 FPS on multiple systems and builds. One report also describes a black 3D screen in Handheld mode; switching to Docked allowed rendering.
A user report says resolution 2X caused flicker or line artifacts; a separate candidate-build report says the release's overexposure warning was not cleared by its limited test.
The issue reporter using an AMD RX 6600 8GB on Windows 10 reports that the emulator starts loading and then remains on a black screen.
Commenters report rendering failures, black screens, and AMD driver crashes; one reports that audio continues while rendering is crashed.
Showing 11–20 of 98 issues
Notes de version récentes
Version build-88 · Non renseigné
Version build-88 · Non renseigné
Version build-88 · Non renseigné
Version build-88 · Zelda: Ocarina of Time
Version build-83 · Ocarina of Time
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-88. 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é.