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 |
|---|---|---|---|---|
| Local nx2 builds 27226d2 and 55532f2, with user patches | runs with issues | Not provided / Apple M3 Max | Not provided | Open report |
| nx2 b06d181 | runs with issues | Not provided / Not provided | 12–14 FPS | Open report |
Problems or notes: User reports VK_ERROR_DEVICE_LOST after a Metal GPU page fault, including during title-screen rendering or when intro-video compute programs run. Rejecting programs containing native opcode 0x4a4 avoided the page fault in the user's patched builds, but this is a user workaround and not a confirmed general fix.
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 (Switch 2), Ocarina of Time
| Build | Status | GPU / CPU | FPS | Details |
|---|---|---|---|---|
| build-75 | not booting | AMD Radeon RX 6750 XT (RDNA2) / Intel Core i7-11700F | Not provided | Open report |
| Not provided | runs with issues | RX 9070 XT 16 GB / Ryzen 7 5800X3D | 17–20 FPS | Open report |
Problems or notes: The game passes the initial launching stage, but the emulator becomes unresponsive at “Building 9 shaders”; background audio works and the game does not progress.
Problems or notes: A short source-build test reached the first room of gameplay without VK_ERROR_DEVICE_LOST, but the cutscene after the intro flickered heavily green/cyan, UI text and legends flickered, and shader compilation caused hitches up to a reported 24-second frame. The reported 17–20 FPS was in a simple interior after shaders stopped compiling. The tester could not determine whether PR #251 or disabling Frame Generation avoided the crash, and did not test the outdoor area.
Current: build-75 (1 record); previous: build-70 (0 records).
Also listed as: OoT, Ocarina of Time
| Build | Status | GPU / CPU | FPS | Details |
|---|---|---|---|---|
| build-93 | runs with issues | RTX 5070 Laptop / i7-13650HX | Not provided | Open report |
| build-93 | runs with issues | RX 5700 (RDNA1) / Not provided | 14–24 FPS | Open report |
| build-93 | runs with issues | RX 7900XT / Ryzen 7 5700X3D | 25–55 FPS | Open report |
| build-93 | runs with issues | RX 9070 XT / Ryzen 7 9800X3D | 14–37 FPS | Open report |
| build-88 | runs with issues | RTX 4070 Ti 12 GB / Ryzen 7 5800X3D | Not provided | Open report |
Problems or notes: Local clang-cl Release nx2 build at 91d1aada6, not PGO. GPU accuracy High prevented GPU thread splitting and ran the work on one busy GPU thread. With GPU mode Fast, async shaders and async presentation on, and NVDEC GPU, splitting was enabled; the reporter notes the second run had a warmer shader cache, so the performance difference is not directly comparable. Profiling also showed GPU idle waits and long hitches while native pipelines were built.
Problems or notes: Renders and runs without crash, device loss, or fence timeouts. Commenter reports 22–24 FPS indoors and 14–15 FPS in Kokiri Forest, with outdoor performance described as uncomfortable.
Problems or notes: Commenter reports stable 25–30 FPS and occasional indoor spikes around 55 FPS; no errors, crashes, or timeouts.
Problems or notes: Boots to title and reaches gameplay without crashes or driver timeouts. Reported approximately 18 FPS on defaults, 17 FPS with async shaders on and GPU accuracy Normal, 14 FPS with async shaders on and GPU accuracy High, and approximately 29 FPS with defaults plus the stated logging, process-priority, and Xbox Game Bar capture changes in Kokiri Forest; intro cutscenes run 32–37 FPS. Gameplay is reported in slow motion. Heavy bloom and overexposure occur in bright areas, and the Great Deku Tree appears as a dark silhouette in its intro scene. One Lichii thread reaches 99% of a core.
Problems or notes: Vulkan reached cutscenes; a visible-window run lasted approximately five minutes without a reported TDR. Two hidden/minimized CLI launches crashed in nvoglv64.dll with exception 0xc0000094 at offset 0xEFC9BB. Pipeline-build stalls and cumulative draw-hold time were reported; the measurements are not frame times or FPS.
Current: build-93 (4 records); previous: build-88 (1 record).
Showing 151–160 of 194 reports
Known issues from Lichii sources
When fastmem could not be created, guest code ran about 1.4x slower; Kokiri Forest ran at 22.2–26.6 FPS rather than 28.5–33.8 FPS. The report attributes the slow boots to failure to allocate 14336 MiB of backing memory.
Recorded fix: Change #645 retries the section after a private commit that grows the page file; in eight back-to-back boots, all three initial failures recovered on the second attempt and none ran slowly.
Graphics fail to load in the Water Temple; a commenter describes the area as unplayable.
Recorded fix: A commenter reports resolving the issue by using a NUP containing the missing texture files, described as 23.8 GB rather than 23.3 GB.
Many Water Temple rooms are invisible, with transparent walls. A comment attributes this to a damaged texture file in the game dump; another user reports the issue was resolved by making a fresh dump with a NUP with a higher file size.
On AMD Windows proprietary drivers, older builds can lose the GPU device when gameplay or a save starts; build-83 and build-88 reports include this problem.
Recorded fix: A Windows RX 9060 XT report found the issue absent in build-93. A Windows RX 7900 XTX report also found it absent in the CI build at 18cfe85.
On AMD RADV Mesa 26.2.4, task/mesh shader use can hang the GPU and cause device loss during 3D gameplay.
Recorded fix: The reporter found that updating to Mesa RADV 26.2.6 avoided the hang on the same GPU with the same build. If using a distrobox in gamescope gaming mode, the reporter says to install the gamescope package in the container so its Vulkan WSI layer is present.
On build-95, the user reports draws held while unbuilt pipelines are being built, causing multi-second stalls, even with async shaders enabled.
The user reports that a fresh build-95 config starts with slow defaults, including High GPU accuracy, asynchronous shaders off, async presentation off, Handheld mode, 4 GB memory layout, and CPU NVDEC; the game ran at 10–15 fps with stalls up to 8.9 s and blurry/pixelated Handheld resolution.
Recorded fix: The user reports that writing the six listed settings before launch helped: gpu_accuracy=0, use_asynchronous_shaders=true, async_presentation=true, nvdec_emulation=2, memory_layout_mode=2, and use_docked_mode=1; set each key's \default= line to false as well.
User reports a black-screen stall after the first AV1 frame with async GPU emulation enabled on AMD Radeon RX 6800 XT; with async GPU emulation disabled, the game later froze during gameplay.
Users report failure to start, black screens with 0 FPS, or emulator crashes in builds 88–95, including a build-95 Linux report with an unhandled SIGSEGV and null-pointer dereference. The comments caution that the reports may have different causes.
The user reports performance remaining at 20 FPS with music glitches on macOS.
Showing 121–130 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é.