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.
Also listed as: OoT, Ocarina of Time, OOT REMAKE
| Build | Status | GPU / CPU | FPS | Details |
|---|---|---|---|---|
| nx2 fork at 99ac3d5955 with local patches (commit 1e53321757) | runs with issues | RTX 5080 / Ryzen 9 7950X3D | Not provided | Open report |
| 09b78bd2df | runs with issues | GTX 1070 / Not provided | Not provided | Open report |
| Not provided | runs with issues | GTX 1070 / Not provided | Not provided | Open report |
| a7a281757da390ce45070e772784e0333831bb25 | runs with issues | NVIDIA GeForce GTX 1080 / AMD Ryzen 9 3900X | Not provided | Open report |
| build-95 | runs with issues | RTX 4070 Ti SUPER / Not provided | Not provided | Open report |
| 95 | not booting | AMD Radeon RX 7900 XTX (RADV) / Intel Core i7-11700K | 0 FPS | Open report |
| Build 95 | not booting | AMD Radeon RX 5700 XT (RADV NAVI10) / AMD Ryzen 5 3600 6-Core Processor | Not provided | Open report |
| Build 95 | not booting | NVIDIA GeForce RTX 3050 Laptop GPU / i5-12500H | Not provided | Open report |
| nx2 @ 89440b29a9 | runs with issues | Not provided / Not provided | Not provided | Open report |
Problems or notes: A user comment reports a median frame time of 22.4 ms in Kokiri Forest and CPU time concentrated on the GPUBack thread, with the GPU front thread mostly waiting. This is a user measurement, not an official compatibility result.
Problems or notes: A merged user report says a door and most vegetation are missing. It attributes the symptom to mesh-shader pipelines being skipped when VK_EXT_mesh_shader is unavailable; the reporter could not confirm on screen that the missing objects corresponded exactly to those draws.
Problems or notes: A draft compute-based fallback reportedly rendered falling leaves, ground leaves, and some foliage shadows with correct textures, but the emulated geometry flickered and canopies, grass, and house walls remained missing.
Problems or notes: Missing leaves, foliage, walls, textures, and other geometry. The report says attempted recompilation and builds 78, 88, 92, Fritzi v2, and perf/Fritzi-Intergrated did not resolve the issue; comments report that #395, #434, and #430 did not restore the geometry.
Problems or notes: Large flat red patches appear across the wet stream bed by the road from Castle Town Market to Hyrule Castle. Another user later reported that stream as clean with their build, attributing the earlier difference possibly to missing #432 and #351; this report's setup used build-95.
Problems or notes: Stalls at a black screen; repeated native MME macro execution failures are reported. Enabling compute pipelines, clearing pipeline caches, and disabling implicit Vulkan layers did not resolve the issue.
Problems or notes: A user-provided build-95 log shows the game loading, followed by a compute pipeline compilation error and an unhandled SIGSEGV. The user later supplied crash details indicating a null-pointer dereference. The log identifies KDE neon User Edition as the host OS.
Problems or notes: Black screen at the intro video after the loading shaders screen; music continues, FPS counter stays at 0, and GPU channels wait on unreleased semaphores. Build 93 reaches gameplay on the same machine. Two other users report the same build 95 hang on Linux with NVIDIA RTX 3060 and RTX 3090 systems. Two users say EDEN_NX2_SPLIT=1 makes the game work.
Problems or notes: User reports that motion controls are affected: Motion 1/Motion 2 mapping does not detect shaking, and gyro/accelerometer input stops after the controller reconnects or after a few seconds with Steam running.
Current: build-93 (3 records); previous: build-88 (0 records).
Also listed as: OoT
| Build | Status | GPU / CPU | FPS | Details |
|---|---|---|---|---|
| Not provided | not booting | AMD Radeon RX 6700 XT (12 GB) / AMD Ryzen 9 5900X | Not provided | Open report |
Problems or notes: On first launch, shader rebuild runs for about 9-10 minutes, then Lichii closes with no error message. The reported Event Viewer faulting module is amdvlk64.dll with exception code 0xc0000005.
Showing 91–100 of 194 reports
Known issues from Lichii sources
Day-only garbage graphics in the Bombchu Bowling Alley: stones and ovens flash pink, yellow, red, or black, and the sign displays garbage, noise, and fragments of another image. It looks correct at night after leaving and returning, and was still present in build-117.
After outdoor play, the sky becomes flat yellow-white and water shimmers green until reboot, due to NaNs spreading through bloom. The report says the NaNs probably originate from fog/foliage probe reads beyond the 64 MiB graphics table-pointer cap.
Recorded fix: Use NaN-safe min/max/clamp handling and fix table-pointer reads beyond the old 64 MiB cap; the reporter confirmed normal visuals after both fixes.
Foliage and vegetation near the player may turn into dead-looking variants or lose leaves up close, including hedges and plants in Hyrule Castle; reports also mention trees, Kokiri Forest bushes, Castle Town hedges, and Hyrule Field grass. One user describes the behavior as an inverted LOD.
On macOS/MoltenVK with an Apple M1, the Switch 2 NSO version boots and plays audio but presents a black image from startup, with approximately 1 FPS and occasional red/green block artifacts.
On AMD GPUs, Ocarina of Time's compute shaders can fail compilation with VK_ERROR_OUT_OF_HOST_MEMORY or cause the AMD driver to crash. The issue report describes missing intro video and an eventual process crash; a later user reports an access violation inside amdvlk64.dll.
OpenGL is reported not to work for this game because GLSL task and mesh programs are not implemented, resulting in repeated errors and an emulator hang.
Rejecting shader hashes before translation skips their dispatches and can result in missing output or a black screen; a user reports the environment switch did not affect the tested Vulkan compute-pipeline path.
Recorded fix: For testing shader rejection, keep the disk shader cache off or delete it before each run; the maintainer says cached shaders are loaded without checking the rejection list.
Performance slows in crowded or busy areas, with front/back GPU-thread synchronization drains and waits; short freezes while attacking are also reported.
Shader compilation can cause freezes of about 3 seconds with each step, according to a user report.
On integrated AMD graphics, device-memory thresholds can keep the texture cache collector in aggressive mode even though deleting all images cannot reduce total usage below the threshold. This causes extensive image churn and GPU waits during gameplay.
Showing 31–40 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
build-117 · Publiée le November 7, 2026
12 fichiers à télécharger pour cette version.
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é.