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-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
| Build | Status | GPU / CPU | FPS | Details |
|---|---|---|---|---|
| 62ba83427e | runs with issues | Radeon 8060S / Ryzen AI MAX+ 395 | 31–37 FPS | Open report |
Problems or notes: In Kokiri Forest, haze, blotches, and a translucent band appear in a fullscreen pass. Rejecting shader 3ddfb1d7a854c849 removed the haze and blotches in that test, while rejecting 780c0536b89fc89e removed fog but left blotches; these workarounds also remove game effects. Two starts stayed black from the beginning, one with music. A reported 31–37 FPS comparison against build-75 used views that were not identical.
Also listed as: OOT Remake, OoT
| Build | Status | GPU / CPU | FPS | Details |
|---|---|---|---|---|
| 3724db9a5c | playable | RTX 4070 / i9-12900F | 16 FPS | Open report |
| b8c812b18 | runs with issues | RX 5700 / Not provided | Not provided | Open report |
| build 95 | playable | RX 7900 XTX / Ryzen 7 9800X3D | 60 FPS | Open report |
| nx2 @ 27226d2 plus two measurement-only commits | runs with issues | RTX 5060 Laptop (8 GB) / Ryzen AI 9 365 | Not provided | Open report |
Problems or notes: The tester reported visible grass and a clear view of the tree through grey fog in front of the Deku Tree. The in-game counter showed 16 FPS in that view; this was a single reading.
Problems or notes: A user reported a local ClangCL build stalled with no frames (maximum 8 presents); a local MSVC build also stalled and died within a minute. In comparison, the user's build-75 release run presented frames at 32 FPS. The maintainer said the report was from an old commit and may no longer apply.
Problems or notes: Not provided
Problems or notes: In the Kokiri Forest scene, disabling per-fence Preflushable downloads or batching them by 64 fences increased GPU back-thread draws per second but broke auto-exposure, leaving the scene overexposed. Default downloads preserved correct exposure. The issue reports measurements, not a gameplay FPS result.
Showing 1–10 of 194 reports
Known issues from Lichii sources
The Fairy Fountain in the Lost Woods does not render. A comment attributes this to a damaged game-data file, not an emulator rendering bug.
Recorded fix: A comment says PR #267 adds a workaround that serves a closest sound sibling when a NUP .zs member has no zstd header; the comment asks the reporter to test whether it works.
A user reports a black screen with title music and unresponsive controls until shaders loaded; after entering gameplay, they reported severe glitches and lag, freezes lasting about 20 seconds during shader building, and a steady 18 FPS.
On an RX 6900 XT with AMD proprietary driver 2.0.353, the driver crashes while compiling shaders during gameplay; rejecting one shader hash does not prevent a subsequent crash at the same driver fault offset. The reject check may not help when the shader is already in the disk cache.
A user reports the frame rate drops to 2.5 FPS when shader loading begins, after the initial cutscene runs at 50–60 FPS.
The game cover/icon is missing among the collection covers when the emulator is opened with the game in the ROM path.
On build 95, Linux and SteamOS users report black-screen hangs with audio still playing; comments associate the issue with repeated `Native MME (split front) failed` errors.
A commenter reports reaching the main menu by starting with GPU accuracy set to Accurate, but reports audio issues and possible recurrence after changing settings.
On Windows 11 with an AMD RX 9000 series GPU and proprietary driver 2.0.416, gameplay is around 20 FPS with large variance, light/haze artifacts, and desynchronized, stuttering audio.
On Linux with an AMD Radeon RX 6700 XT, gameplay is around 20 FPS with audio crackling below full speed. On Windows with the same PC, only subtitles rendered.
With Mesa 25.0.7 and kernel 6.12.115, gameplay was followed after about nine minutes by a Vulkan device loss and an unrecovered display; this was not seen again after updating Mesa and the kernel.
Recorded fix: Update to Mesa 26.1.6 and kernel 7.2.11; the reporter did not see the device loss again afterward.
Showing 171–180 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
Aucune version testée et téléchargeable n’est associée à Ocarina of Time. Consultez les versions disponibles ou la discussion du ticket correspondant.
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é.