Mario Kart World
A user report says stock build 88 reset the GPU about 25 seconds after launch on Linux RADV.
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: Ocarina of Time, Zelda: Ocarina of Time, OoT, Zelda OoT, TLoZ: OoT
| Build | Status | GPU / CPU | FPS | Details |
|---|---|---|---|---|
| Not provided | playable | Not provided / Not provided | Not provided | Open report |
| Not provided | runs with issues | 1080 Ti / Ryzen 5600X | Not provided | Open report |
| Not provided | runs with issues | GTX 1050 Ti / 7th gen i5 | 18–27 FPS | Open report |
| Not provided | playable | RTX 3070 Ti / Ryzen 7 2700X | Not provided | Open report |
| build-95 (`nx2-build-95`) | runs with issues | RTX 4060 Laptop, 8 GB, 45 W max power limit / Intel Core i7-12650H (6P+4E, 16 threads) | 9.4–51.4 FPS | Open report |
| build 95 | runs with issues | Radeon 890M / Ryzen AI Z2 Extreme | 23–25 FPS | Open report |
| build 117 (PGO) | runs with issues | Radeon 890M / Ryzen AI Z2 Extreme | 42–44 FPS | Open report |
| nx2-build-95 | runs with issues | NVIDIA GeForce RTX 2070 / Intel Core i7-12700KF | Not provided | Open report |
| Not provided | not booting | NVIDIA GeForce RTX 3050 / Not provided | Not provided | Open report |
| build 88 and 93 | runs with issues | GTX 1060 6gb / Ryzen 5 5600 | Not provided | Open report |
Problems or notes: A commenter says everything works on their Mac with the latest main branch; hardware and build details are not stated.
Problems or notes: A commenter reports objects and doors failing to appear.
Problems or notes: A commenter reports invisible push blocks, making progress difficult.
Problems or notes: A commenter reports testing the draft shader warm-up and says first-visit freezes were gone. The comment gives no broader gameplay or session-duration evidence.
Problems or notes: User reports multi-second stalls while draws are held for unbuilt pipelines with async shaders enabled; in about 8 minutes, mean performance was 25.8 fps and six present windows had a maximum frame time over 1 s (worst 4.9 s). A fresh config used slow defaults and ran at 10–15 fps with stalls up to 8.9 s and blurry/pixelated Handheld resolution. Settings for the measured build-95 session were GPU accuracy Low, async shaders and async presentation enabled, Docked, 8 GB memory layout, and NVDEC GPU. The report also describes Frizti v3 behavior separately: it skipped draws with no pipeline, averaging 26.0 fps in 30-fps mode (range 16.4–30), with revisits at 30.0 fps and no frames over 100 ms.
Problems or notes: The intro, Deku Tree cutscene, and initial gameplay rendered correctly, but the game froze at 0 FPS when Navi passed the Kokiri guard on the path to the Deku Tree. The report mentions texture format asserts and Unmapped Device ReadBlock errors.
Problems or notes: The intro and cutscenes ran at 42–44 FPS and the game reached Kokiri Forest, but Unmapped Device ReadBlock errors and multi-second stalls were followed by a hard freeze before Navi reached the guard. The same errors occurred with memory layout set to both 12 GB and 4 GB.
Problems or notes: User reports that after the Kaepora Gaebora cutscene near Hyrule Castle, the area appears empty and foggy, Link falls through the world, and repeated void-outs prevent progression. Reported on Windows 11 25H2 in Handheld mode with Vulkan. The user says the issue reproduces 100% with the same save; listed configuration changes and disabling a built-in patch did not fix it.
Problems or notes: Crashes during boot about 9–13 seconds after launch, after presenting its first frame, at an unimplemented nx2:vi2 function 201. The same crash is reported on builds 93 and 95.
Problems or notes: A commenter reports missing textures in the Deku Tree after loading a save, across two game versions and builds 88 and 93. They also report that it worked the first time.
Current: build-117 (2 records); previous: build-116 (0 records).
Showing 171–180 of 308 reports
Known issues from Lichii sources
A user report says stock build 88 reset the GPU about 25 seconds after launch on Linux RADV.
With EDEN_NX2_PRELOAD_ALL_PIPELINES=1, pipelines not used for 9000 frames are evicted, leading to runtime rebuilds and stutter when entering a new area.
With EDEN_NX2_PRELOAD_ALL_PIPELINES=1, pipelines are evicted after 9000 frames, causing runtime builds, long held draws, and a reported freeze.
Grass and pebbles disappear or flicker during sword attacks; disabling persistent pipeline cache was reported to make grass disappear permanently, while enabling it left flickering.
Recorded fix: A commenter reports the issue was fixed in build-116.
User reports significantly worse performance and that parts of the game are broken in build 117 compared with build 93 on NVIDIA RTX 30 series or older.
Walls, environmental geometry, and some interactive objects are invisible; occasional stuttering is also reported.
A commenter reports invisible push blocks.
A commenter reports that objects and doors do not appear.
Issue reports describe audio desynchronization and crashes or full-system freezes during early cutscenes on AMD graphics cards.
In build 116, a user reports frame generation rapidly switching between idle and auto flowstate, lower frame rates, stuttering, and the texture cache being overwritten. A commenter also reports white flashes on Windows 11.
Showing 101–110 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é.