Ocarina of Time
A user reports approximately 23–25 FPS in Kokiri Forest on Fritchii v4, with CPU and GPU not saturated.
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
| Build | Status | GPU / CPU | FPS | Details |
|---|---|---|---|---|
| nx2 5a50f50e0b; official PGO artifact of build-80 and local non-PGO nx2-latest | runs with issues | AMD RX 9070 XT (RDNA4, 16 GB) / Ryzen 7 5800X3D (8C/16T) | 28–35 FPS | Open report |
| local non-PGO nx2 @ 4c173bb792 with PR #345 merged (4647895acc) | playable | Radeon RX 9070 XT (RADV GFX1201) / Ryzen 7 5800X3D (8C/16T) | Not provided | Open report |
| Lichii nx2 build 93, Windows release | runs with issues | RX 9070 XT 16 GB / Ryzen 7 7800X3D (8C/16T) | 18 FPS | Open report |
| Lichii nx2-build-83 non-PGO AppImage | runs with issues | RX 9070 XT 16 GB (RADV GFX1201) / Ryzen 7 5700X (AM4, 8C/16T, non-X3D) | 20–35 FPS | Open report |
Problems or notes: On Bazzite (Fedora Atomic 45), gameplay was reported at 28-35 fps with 31-36 ms frame times despite no saturated thread. The PGO artifact crashed in dynarmic with Unhandled SIGSEGV after 2-10 minutes; the local non-PGO build was stable over several sessions.
Problems or notes: In a Deku Tree interior test, the reporter measured 16.8-18.6 ms frame times and reported the area was at the present cap. White flashes were confirmed gone there. Kokiri Village and Hyrule Field remained untested, and runtime pipeline builds caused isolated frame spikes.
Problems or notes: On Windows 11 Enterprise LTSC 2024, gameplay was reported at about 18 fps (about 56 ms per frame) with no saturated thread. New-content pipeline compilation caused first-visit hitches. A later follow-up on Frizti v3 reported about 20 fps in a busy view and about 60 fps looking at the floor; the reporter attributed the heavy-view limit to host GPU load, but that follow-up did not identify the build as build 93.
Problems or notes: On CachyOS, gameplay commonly ran at 20-35 FPS and in slow motion; menus were about 60 FPS and intro video/audio stuttered. The non-PGO AppImage rendered and reached gameplay. The PGO AppImage produced audio but no video output, and clearing the shader cache did not resolve it. The stated FPS range is the reporter's gameplay observation, not the table's median window FPS.
| Build | Status | GPU / CPU | FPS | Details |
|---|---|---|---|---|
| build-93 | runs with issues | AMD Radeon RX 9070 XT / Not provided | Not provided | Open report |
Problems or notes: Severe bright pink, cyan, and white lines appear along mountain silhouettes, especially where mountains meet the sky, in Kakariko Village. Shader compilation continues during gameplay, especially when moving or rotating the camera.
Current: build-93 (1 record); previous: build-88 (0 records).
Showing 1–5 of 5 reports
Known issues from Lichii sources
A user reports approximately 23–25 FPS in Kokiri Forest on Fritchii v4, with CPU and GPU not saturated.
Gameplay graphics remain black while UI and button prompts work; the cutscene and opening title display correctly.
Foliage, leaves, walls, doors, and other geometry can be missing on GPUs without VK_EXT_mesh_shader because task/mesh shader draws are skipped.
A draft compute-based task/mesh shader fallback rendered some foliage on GTX 1070 but produced flickering geometry and still missed canopies, grass, and house walls.
The in-game language did not change to Portuguese (Brazil) after configuring the emulator system language to Portuguese.
On Linux with NVIDIA GPUs, gameplay can lead to a GPU hang after roughly five minutes. Reports include Xid 109 CTX SWITCH TIMEOUT or a GPU stuck at 100% utilization without an Xid.
Random white splotches appear in Hyrule Field after beating King Dodongo.
The whole PC crashes right after the intro movie on Linux with an AMD ATI Radeon RX 9060 XT.
White squares appear in Kakariko village.
On the reported NVIDIA systems using driver 581.29, the game crashes with Vulkan device loss during shader and pipeline compilation after the intro cinematic; reports include repeated Unmapped Device ReadBlock errors and Windows nvlddmkm Event ID 153.
Recorded fix: One user reports that updating to the official NVIDIA Game Ready 621.14 driver and rebooting resolved the issue on their system. Another comment says it started working after installing the latest Nvidia driver.
Showing 21–30 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
Aucune version testée et téléchargeable n’est associée à Ocarina of Time. Consultez les versions disponibles ou la discussion du ticket correspondant.
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é.