After: Dynamic FPS mod bundled and enabled by default; automatic patching is restricted to the supported game build and checks for patch conflicts.
build-83 → build-88
Compatibilité des jeux
Compatibilité des jeux avec Lichii Emulator
Vous avez un jeu en tête ? Voyez comment il tourne dans Lichii, repérez les problèmes et choisissez une version à essayer.
Latest recorded build
build-88
Pre-release
Published November 6, 2026
Trouver un jeu
Rechercher des jeux compatibles avec Lichii
Les données actuelles comptent 58 entrées par jeu et environnement, et 114 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
Game Compatibility Results
Recorded performance
Performance by Build and Hardware
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.
Zelda: Ocarina of Time Reported platform: Windows 11
Also listed as: OoT
| Build | Status | GPU / CPU | FPS | Details |
|---|---|---|---|---|
| Not provided | runs with issues | NVIDIA RTX 30 series or older / Not provided | Not provided | Open report |
| Not provided | runs with issues | AMD RX 9060 XT / Not provided | Not provided | Open report |
| nx2-build-83 | runs with issues | AMD RX 9000 series / Not provided | 41 FPS | Open report |
Not provided report
Statusruns with issues
GPUNVIDIA RTX 30 series or older
CPUNot provided
DriverNot provided
Recorded FPSNot provided
Problems or notes: Audio plays a different part of the game than the image during the intro; the audio is clean but out of sync by a scene. A follow-up report says the game uses StreamType::Render and that traced sink appends were complete with no samples dropped. Another user reports the same issue with a 7800X3D, RTX 5070, and 32gb DDR5.
Not provided report
Statusruns with issues
GPUAMD RX 9060 XT
CPUNot provided
Driver28.10.2
Recorded FPSNot provided
Problems or notes: A commenter reports a driver crash and black screen after the intro on the MSVC build. The PGO build reportedly shows only 2D elements such as the logo or menu.
nx2-build-83 report
Statusruns with issues
GPUAMD RX 9000 series
CPUNot provided
DriverNot provided
Recorded FPS41 FPS
Problems or notes: User reports audio running ahead of video, cutting out and repeating during the opening cutscene, followed by a system freeze at the Deku Tree cutscene requiring a forced shutdown. Settings reported: Vulkan, GPU Mode Fast, Docked, Bilinear window adapting filter, and no anti-aliasing.
Related game issues
- macOS/MoltenVK: Ocarina of Time (0400486024DEC000) kills or hangs the Metal device at the intro-video boundary (open)
- [Crash] (open)
- [Crash] AMD Crash/AudioDesync (open)
- [AMD RX 9070 XT] Black screen with UI visible and GPU driver timeout (Build 88) (open)
- [Crash] Ocarina of Time (0400486024DEC000): freezes in Hyrule Castle Town pot room near the guard (open)
- [Crash] AMD Ocarina of time Doesn't Start (open)
- [GBug] Ocarina of Time (0400486024DEC000): intro freezes for 6 to 18 minutes on AMD while the driver optimizes two compute shaders (open)
- [Perf] OoT (0400486024DEC000): per-fence Preflushable buffer downloads (~430 MB/s) are the biggest GPU back-thread cost; batching them gives +55% draws/s but breaks exposure (open)
- [VBug] OoT Slows when booting. (open)
- Ocarina of Time harvest fork: findings and open tasks (open)
- [Crash] Linux/RADV (RX 9070 XT): invalid SPIR-V fragment shader (depth image u32 sampled as f32) segfaults in VkPipelineBuild, Ocarina of Time (open)
- [Bug] Windows build-83 can hang on Closing software after OoT gameplay (open)
- [GBug] OoT (0400486024DEC000): the same ~60 cached graphics pipelines are rebuilt on the GPU thread every boot (open)
- [VBug] Oot is in a "nightmare mode"? also gameplay speed is at like 30% (open)
- [GBug] Ocarina of Time on RADV (RX 9070 XT): 28-35 fps, 35 ms frame with no saturated thread (translation/sync bound) (open)
- [GBug] Zelda: Ocarina of Time (0400486024DEC000): the audio plays a different part of the stream than the picture (open)
- [VBug] [nx2-build-75] Zelda: Ocarina of Time (0400486024DEC000) black screen — no AV1 decoder (open)
- [VBug] OoT (0400486024DEC000): world renders black except areas lit by Navi and around Link, AMD RX 9070 (open)
- Release note: Outdoor areas have far too much fog and glow compared with console; performance is about 12–22 fps on a Ryzen 5900X with an RTX 3080, and three rare shaders remain unsupported.
- Release note: On macOS arm64 through MoltenVK, the Metal device may be lost or the GPU thread may hang at the intro-video/gameplay boundary. A commenter attributes the device loss to an attachment-less framebuffer reaching 32768×32768, above the stated Apple GPU limit of 16384.
- Release note: After a local workaround for device loss, a commenter reports that the 3D scene remains black while sound and subtitles work on an older Eglantine fork; current nx2 behavior was not yet checked.
- Release note: User reports a crash when opening the game on Arch Linux with an AMD Radeon AI PRO R9700 (9070XT); the console reports a segmentation fault.
- Release note: User reports audio/video desynchronization during the opening cutscene and a system freeze at the Deku Tree cutscene on Vulkan with an AMD RX 9000 series GPU. Comments report crashes on AMD GPUs, including while building shaders. One commenter reports that OpenGL GLSL stops the crashes but leaves only the UI visible.
- Release note: On some AMD GPUs, the UI may remain visible while the 3D world is black; reports also describe AMD driver timeouts or crashes.
- Release note: User-reported reproducible freeze when walking deeper into the pot room in Hyrule Castle Town, near the guard.
- Release note: The issue reporter using an AMD RX 6600 8GB on Windows 10 reports that the emulator starts loading and then remains on a black screen.
- Release note: Commenters report rendering failures, black screens, and AMD driver crashes; one reports that audio continues while rendering is crashed.
- Release note: On AMD's proprietary Windows driver, two compute pipelines can take 6 to 18 minutes to compile during the intro, leaving the game at 0 FPS while audio continues. Rejecting the shader hashes avoids the wait but causes black areas in the intro, title, and castle scenes.
- Release note: In the measurement-only experiment, disabling per-fence Preflushable downloads or batching downloads by 64 fences caused overexposure in Kokiri Forest.
- Release note: A commenter reports that an experimental compute storage write-extent analysis reduced marked GPU-written data and fence copies while preserving correct auto-exposure. It was described as code on a user's branch, not as an upstream or validated release fix.
- Release note: Static review and a separate research comment describe read-trap bookkeeping and dirty-state issues that can leave stale GPU-written data when per-fence downloads are disabled; proposed corrections and batching remain untested or local experiments.
- Release note: Slows when booting.
- Release note: Community comments describe AMD black or corrupted-world output, fragment-pipeline compiler crashes on Windows, later timeouts or TFB stalls, corrupted output, and a RADV depth-image SPIR-V failure. These are separate reported cases; the comments do not establish a universal cause or resolution.
- Release note: User reports a segfault during gameplay on Linux with an AMD RX 9000-series GPU and RADV, when a graphics pipeline is built for an invalid fragment shader.
- Release note: On Windows build-83, shutdown can hang at “Closing software…” after gameplay. Some sessions completed shutdown successfully; the cause is undetermined.
- Release note: Persistent graphics pipeline cache entries are reportedly rebuilt on the GPU thread during gameplay on repeated boots, causing a visible hitch.
- Release note: With GPU Mode: Accurate (High), gameplay may run in slow motion at about 30 FPS; shader compilation can cause stutter on new content.
- Release note: PGO artifact crashes in dynarmic with Unhandled SIGSEGV after 2–10 minutes on the reported machine.
- Release note: Clean audio from a different point of the game plays while the intro image is displayed; audio and picture are substantially out of sync.
- Release note: In gameplay, the world renders almost entirely black, with only the HUD and some areas near light sources visible; some shapes appear blown out with heavy bloom.
Compared with Previous Build
From build-83 to build-88: follow the gameplay changes described for these two builds.
Zelda Ocarine of time Reported platform: Windows 11
| Build | Status | GPU / CPU | FPS | Details |
|---|---|---|---|---|
| build-75 | runs with issues | NVIDIA RTX 30 series or older / Not provided | Not provided | Open report |
build-75 report
Statusruns with issues
GPUNVIDIA RTX 30 series or older
CPUNot provided
DriverNot provided
Recorded FPSNot provided
Problems or notes: The report describes audio with no visuals. A commenter reports the title screen at 60 FPS followed by a black screen when starting a new game, with an AV1 decoder error. Other users report black screens, crashes, very low FPS, missing textures, lighting and graphics artifacts, and a blown-out white image.
Related game issues
- [VBug] Video doesn't display on Zelda Ocarine of time (open)
- Release note: Black screen after starting a new game, with audio continuing; a commenter also reports an FFmpeg error stating there is no decoder for video/av1.
- Release note: Very low FPS and graphics problems, including missing textures, lighting or ambient occlusion issues, and a blown-out white image.
Compared with Previous Build
Current: build-75 (1 record); previous: build-70 (0 records).
Showing 111–114 of 114 reports
Known issues from Lichii sources
Known Game Issues
Zelda: Ocarina of Time
Slows when booting.
Zelda: Ocarina of Time
Community comments describe AMD black or corrupted-world output, fragment-pipeline compiler crashes on Windows, later timeouts or TFB stalls, corrupted output, and a RADV depth-image SPIR-V failure. These are separate reported cases; the comments do not establish a universal cause or resolution.
Zelda: Ocarina of Time
User reports a segfault during gameplay on Linux with an AMD RX 9000-series GPU and RADV, when a graphics pipeline is built for an invalid fragment shader.
Zelda: Ocarina of Time
On Windows build-83, shutdown can hang at “Closing software…” after gameplay. Some sessions completed shutdown successfully; the cause is undetermined.
Mario Kart World
A user reports missing textures and buggy visuals after booting, occasional startup crashes, and crashes when playing the Grand Prix race on build-83 with Intel integrated graphics on Windows 11.
Zelda: Ocarina of Time
Persistent graphics pipeline cache entries are reportedly rebuilt on the GPU thread during gameplay on repeated boots, causing a visible hitch.
Zelda: Ocarina of Time
With GPU Mode: Accurate (High), gameplay may run in slow motion at about 30 FPS; shader compilation can cause stutter on new content.
Recorded fix: Set GPU Mode to Fast; the commenter reports this resolved the slow gameplay for their setup.
Zelda Ocarina of Time
Black screen after boot; some reports say sound and the title/logo work.
Zelda Ocarina of Time
On build-83, one user reports a solid-green displayed image although a screen capture shows the game rendering correctly.
Zelda Ocarina of Time
On build 83, a user reports device loss at gameplay start with VK_ERROR_DEVICE_LOST.
Showing 31–40 of 98 issues
Notes de version récentes
Changements de compatibilité dans les dernières versions
Version build-88 · Non renseigné
Integrated performance ports and reduced unnecessary writer tracking; added explicit GPU-to-host visibility before buffer readback and submitted native desktop GPU work earlier while preserving conservative synchronization for macro reads and semaphore waits.
Version build-88 · Non renseigné
Added bounded background preparation of cached graphics pipelines and persistent task/mesh shader state. Updated the Vulkan cache to v53 while preserving compatible v52 caches, and made interrupted cache migrations retryable.
Version build-88 · Non renseigné
Fixed temporal history, motion interpolation, image transitions, and descriptor retirement for FSR3 frame generation; frame generation remains off by default.
Version build-88 · Zelda: Ocarina of Time
Bundled Dark's Dynamic FPS mod, enabled by default for Ocarina of Time. Disable it independently in the game's Add-Ons settings. Max Resolution remains a separate Add-On. CPU Clock Normal is recommended when evaluating the mod; Boost/Overclock can affect game speed. Full gameplay timing has not been verified.
Version build-83 · Ocarina of Time
Fixed missing vegetation, incorrect materials and lighting, a glowing doorway, one-frame white flashes, and an AMD black 3D scene. Added Max Resolution (built-in), enabled by default for the supported game build, and Ocarina-specific frame-ahead presentation tuning.
Choix d’une version
Quelle version utiliser ?
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-88. Gardez une version fonctionnelle sous la main pendant vos essais.
Questions sur la compatibilité
FAQ sur la compatibilité des jeux
Comment partager un jeu avec ces filtres ?
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.
Que faire si j’obtiens un écran noir ?
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.
Pourquoi un même GPU peut-il donner des résultats différents ?
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.
Où puis-je soumettre un résultat manquant ?
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é.