Other / not listed
Frequent freezing is reported while running at about 30 FPS on Windows 10 with build 117.
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
Frequent freezing is reported while running at about 30 FPS on Windows 10 with build 117.
The user reports very low FPS and rendering artifacts when running on an Intel Arc GPU under Windows 11 with Vulkan.
On an AYN Thor with Adreno 740 and Turnip, large native compute shaders cause pipeline compilation to consume substantial memory and pin Vulkan pipeline-builder threads; reports include black output, GPU device loss, or out-of-memory termination.
On ARM hosts using NCE, the built-in Dynamic FPS by Dark and Max Resolution patches together were reported to trigger an early SIGILL on builds 88 and 94.
Recorded fix: Disable both Dynamic FPS by Dark (built-in) and Max Resolution (built-in) in the game's Add-Ons.
Long shader and pipeline hitches while exploring; the user also reports texture flashes or freezes when new pipelines compile.
A user reports constant CPU-side coil whine while playing on a laptop.
Missing textures were reported on build 95; stuttering and long loading times were reported on build 117.
On build-117, the user reports nonstop freezes or frame drops during gameplay. They report occasional hangs on older builds.
A system-wide GPU error and crash after playing for a few minutes, reported with AMD RX 6000 series or older on Linux in Build 117 PGO.
Crashes during boot at an unimplemented nx2:vi2 function 201; the report also mentions a later unimplemented IGeneralService function 101 assert.
Showing 81–90 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é.