Mario Kart World
The user reports missing textures and buggy visuals, occasional startup crashes, and crashes during Grand Prix races on Intel integrated graphics.
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 98 entrées par jeu et environnement, et 275 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 |
|---|---|---|---|---|
| nx2 b06d181 | runs with issues | Not provided / Not provided | 12–14 FPS | Open report |
Problems or notes: User reports that framebuffer clamping plus a 64 KiB stream-buffer tail, or rejecting native opcode 0x4a4 programs, prevents intro-video page faults in tests. With the clamp and tail, intro playback reached 25-30 FPS and completed, but the video-to-gameplay transition still stalled; a second decoder session was also followed by VK_ERROR_DEVICE_LOST on builds running the native chain.
| Build | Status | GPU / CPU | FPS | Details |
|---|---|---|---|---|
| nx2-build-92 | runs with issues | AMD Radeon RX 9070 XT (16 GB VRAM) / Ryzen 5 5500 | Not provided | Open report |
Problems or notes: A user reports that the black screen issue is gone and the game runs, but performance is poor and shader compilation causes heavy stuttering, sometimes dropping to 0 FPS. Another commenter says they get 60 fps after the start/launch, but does not specify the settings or hardware for that result.
Also listed as: Ocarina of Time
| Build | Status | GPU / CPU | FPS | Details |
|---|---|---|---|---|
| Not provided | not booting | RX 9070 XT 16 GB / Ryzen 7 9850X3D | Not provided | Open report |
Problems or notes: A commenter reports an instant crash despite trying the EDEN_NX2_NO_MESH=1 workaround. Firmware 20.3.0, game version 1.1.1, and game build ID E0F3CCFAF50065AE4EA01EB5AEB13B1A45DA3348 are stated.
Also listed as: OoT, Ocarina of Time
| Build | Status | GPU / CPU | FPS | Details |
|---|---|---|---|---|
| build-117 | playable | Radeon RX 9070 XT / AMD Ryzen 7 5700X | 19–65 FPS | Open report |
| nx2-build-92 | runs with issues | RX 7800 XT (RADV) / Ryzen 7 7700X | 35–59 FPS | Open report |
| 95 Non-PGO | not booting | AMD Radeon RX 9070 XT / AMD Ryzen 7 5700X (AM4) | Not provided | Open report |
| 83 Non-PGO | boots | AMD Radeon RX 9070 XT / AMD Ryzen 7 5700X (AM4) | Not provided | Open report |
Problems or notes: The user reports rendering works again. In Wayland, around 19–25 FPS, fluctuating. In XWayland with QT_QPA_PLATFORM=xcb, Kokiri Village measured 25–54 FPS, usually around 30 FPS; inside the Deku Tree usually 30–45 FPS while idle, occasional peaks to 65 FPS, and recurring drops to 19 FPS. The user reports normal game speed despite frame drops and says the game is playable; FPS/frametime variability remains substantial.
Problems or notes: Ubuntu 26.04, Docked, GPU accuracy Low. Without EDEN_NX2_NO_MESH=1, device loss occurs while loading a save. With the variable, a single 337-second session ran until the user closed it; approximately 59 FPS with dips to 35–50 and some stutter, 47 draws skipped, and a door was transparent at the start. This was not tested in a new game.
Problems or notes: The game displays a completely black screen while intro audio continues, after shader compilation. The report says this also occurs in native Wayland, XWayland with QT_QPA_PLATFORM=xcb, with EDEN_NX2_NO_MESH=1 alone, and with both environment variables together. Removing Vulkan Pipeline Cache and Cache Storage and recompiling shaders did not resolve it.
Problems or notes: The game renders on the same machine under Wayland without special environment variables, but performance is reported as lower.
Current: build-117 (1 record); previous: build-116 (0 records).
| Build | Status | GPU / CPU | FPS | Details |
|---|---|---|---|---|
| 4.1 | runs with issues | NVIDIA RTX 40 series / Not provided | Not provided | Open report |
Problems or notes: When gameplay begins, graphics remain a black screen while the UI and button prompts work. The cutscene and opening title display correctly.
| Build | Status | GPU / CPU | FPS | Details |
|---|---|---|---|---|
| build-70 | runs with issues | Not provided / Not provided | Not provided | Open report |
| nx2-build-88 | runs with issues | AMD BC-250 (Oberon APU) — RADV GFX1013 / Not provided | 37 FPS | Open report |
Problems or notes: Some textures are still black, and it can crash later in play.
Problems or notes: Reaches gameplay and remains responsive, but the 3D scene is black while the HUD renders. Three graphics programs are rejected, causing draws to be skipped; compute shader dispatches are also rejected. The reported frame time is approximately 37 fps.
Current: build-70 (1 record); previous: build-65 (0 records).
Showing 231–240 of 275 reports
Known issues from Lichii sources
The user reports missing textures and buggy visuals, occasional startup crashes, and crashes during Grand Prix races on Intel integrated graphics.
Black 3D gameplay scene with HUD or menus still visible; some reports also mention stuttering, audio problems, flickering shadows, or missing tree leaves.
Recorded fix: One commenter reported that switching to Docked mode resolved the black screen. Another reported that the scene rendered after upgrading from build-75 to Windows MSVC build-88, but settings also changed and the cause was not isolated.
The Deku Tree exterior cutscene can render black except for a small circle around Navi, even when the title screen, intro, and earlier cinematics render correctly. A later report also observed a deterministic AMD driver crash while building graphics pipelines in the same scene.
A half-resolution layer can produce dark blotches and translucent patches over Link, terrain, and other objects. User reports traced the issue to a depth image being cleared after a depth copy; one report says PR #185 addresses the ordering, but reports do not establish a confirmed released fix.
River water may be dark or lack visible lit contribution, and one user reported flickering that depends on the sun's position relative to the camera.
Outdoor scenes may remain severely white/yellow and washed out on clean upstream nx2, despite substantial improvements to vegetation and atmosphere.
Texture-format and texture-index assertions were reported during gameplay; a separate report associated a period of such assertions with terrain and subtitle flickering, without establishing causation.
Only character outlines and UI are visible after launching the game.
On Windows build-83, shutdown can hang at “Closing software…” after gameplay. Some sessions completed shutdown successfully; the cause is undetermined.
User reports the game blacks out when booted in build 83; they state it worked in build 75.
Showing 271–280 of 287 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é.