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-83 | playable | RTX 4070 Ti / Ryzen 7 7700X | Not provided | 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.
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 |
|---|---|---|---|---|
| build-83 | runs with issues | AMD Radeon RX 9060 XT 16 GB / Intel i7-9700K | Not provided | Open report |
Problems or notes: User reports say the game reaches gameplay and then loses the GPU device. The report also mentions black output after rejecting selected shaders and a later device loss. All tried settings and environment-variable changes still resulted in device loss.
Current: build-83 (1 record); previous: build-75 (2 records).
Also listed as: OoT
| Build | Status | GPU / CPU | FPS | Details |
|---|---|---|---|---|
| build-83 | runs with issues | RTX 5090 / Ryzen 7 9800X3D | 34.04–46.28 FPS | Open report |
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-83 (1 record); previous: build-75 (1 record).
| Build | Status | GPU / CPU | FPS | Details |
|---|---|---|---|---|
| build-83 | runs with issues | RX 9060 XT 16 GB / Not provided | Not provided | Open report |
Problems or notes: User reports that the black-screen behavior is gone and the game reaches gameplay, but it device-loses at gameplay start with VK_ERROR_DEVICE_LOST.
Current: build-83 (1 record); previous: build-75 (0 records).
Also listed as: OoT
| Build | Status | GPU / CPU | FPS | Details |
|---|---|---|---|---|
| build-83 | not booting | AMD RX 6000 series or older; AMD RX 6600 8GB / Not provided | Not provided | Open report |
Problems or notes: The issue reporter says the emulator begins loading and then stays on a black screen. This is an open issue.
Current: build-83 (1 record); previous: build-75 (0 records).
Also listed as: OoT
| Build | Status | GPU / CPU | FPS | Details |
|---|---|---|---|---|
| build-83 | runs with issues | RTX 5090 / Ryzen 7 9800X3D | Not provided | Open report |
Problems or notes: Opening rendered and controllable Kokiri Forest gameplay was reached. Some sessions hung at “Closing software…” during shutdown, while others exited successfully. The source does not establish a cause or fix.
Current: build-83 (1 record); previous: build-75 (0 records).
Also listed as: OoT
| Build | Status | GPU / CPU | FPS | Details |
|---|---|---|---|---|
| build-83 | runs with issues | RTX 4070 SUPER 12 GB / i5-14600KF | 30 FPS | Open report |
| build-83 | unknown | AMD RX 6000 series or older; AMD Radion RX 6650 XT / AMD Ryzen 5 5600 | Not provided | Open report |
| build-83 | unknown | Not provided / Not provided | Not provided | Open report |
Problems or notes: Issue reporter describes shader problems and gameplay at about 30% speed. A commenter reports that GPU Mode: Fast restored normal speed and reached 60 FPS in most areas; build-83 held 60 FPS after the shader cache warmed up. The commenter also reports stutter while new shader pipelines are built.
Problems or notes: Reported that the game slows when booting; the reporter restarted the emulator and game and changed settings, but did not state a resolution.
Problems or notes: The release says the perf9 build was tested successfully in Ocarina of Time, but provides no gameplay duration or specific tested hardware.
Current: build-83 (3 records); previous: build-75 (1 record).
Showing 1–9 of 9 reports
Known issues from Lichii sources
Slows when booting.
Community comments describe AMD black or corrupted-world output, fragment-pipeline compiler crashes on Windows, later timeouts or TFB stalls, corrupted output, and a RADV depth-image SPIR-V failure. These are separate reported cases; the comments do not establish a universal cause or resolution.
User reports a segfault during gameplay on Linux with an AMD RX 9000-series GPU and RADV, when a graphics pipeline is built for an invalid fragment shader.
On Windows build-83, shutdown can hang at “Closing software…” after gameplay. Some sessions completed shutdown successfully; the cause is undetermined.
A user reports missing textures and buggy visuals after booting, occasional startup crashes, and crashes when playing the Grand Prix race on build-83 with Intel integrated graphics on Windows 11.
Persistent graphics pipeline cache entries are reportedly rebuilt on the GPU thread during gameplay on repeated boots, causing a visible hitch.
With GPU Mode: Accurate (High), gameplay may run in slow motion at about 30 FPS; shader compilation can cause stutter on new content.
Recorded fix: Set GPU Mode to Fast; the commenter reports this resolved the slow gameplay for their setup.
Black screen after boot; some reports say sound and the title/logo work.
On build-83, one user reports a solid-green displayed image although a screen capture shows the game rendering correctly.
On build 83, a user reports device loss at gameplay start with VK_ERROR_DEVICE_LOST.
Showing 31–40 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
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-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é.