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.

Ocarina of Time dans Lichii Emulator, d’après le ticket nº 201 sur GitHub
Source : ticket nº 201 sur GitHub. Ocarina of Time · Capture en jeu de la communauté.
Latest recorded build build-117 Published November 7, 2026

Trouver un jeu

Rechercher des jeux compatibles avec Lichii

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

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.

The Legend of Zelda: Ocarina of Time Reported platform: unknown playable runs with issues unknown not booting 45 reports

Also listed as: Ocarina of Time, Zelda: Ocarina of Time, OoT, Zelda OoT, TLoZ: OoT

Lichii compatibility reports for The Legend of Zelda: Ocarina of Time
Build Status GPU / CPU FPS Details
build-95 (`nx2-build-95`) runs with issues RTX 4060 Laptop, 8 GB, 45 W max power limit / Intel Core i7-12650H (6P+4E, 16 threads) 9.4–51.4 FPS Open report
build 95 runs with issues Radeon 890M / Ryzen AI Z2 Extreme 23–25 FPS Open report
build 117 (PGO) runs with issues Radeon 890M / Ryzen AI Z2 Extreme 42–44 FPS Open report
nx2-build-95 runs with issues NVIDIA GeForce RTX 2070 / Intel Core i7-12700KF Not provided Open report
Not provided not booting NVIDIA GeForce RTX 3050 / Not provided Not provided Open report
build 88 and 93 runs with issues GTX 1060 6gb / Ryzen 5 5600 Not provided Open report
Not provided unknown RTX 5060 / Not provided Not provided Open report
Not provided playable RTX 4090 / Ryzen 9 7950x3D Not provided Open report
Not provided runs with issues Integrated graphics AMD (Radeon 860M, Ryzen AI 7 350, RADV / Mesa) / Ryzen AI 7 350 22–23 FPS Open report

build-95 (`nx2-build-95`) report

Statusruns with issues
GPURTX 4060 Laptop, 8 GB, 45 W max power limit
CPUIntel Core i7-12650H (6P+4E, 16 threads)
Driver610.78
Recorded FPS9.4–51.4 FPS

Problems or notes: User reports multi-second stalls while draws are held for unbuilt pipelines with async shaders enabled; in about 8 minutes, mean performance was 25.8 fps and six present windows had a maximum frame time over 1 s (worst 4.9 s). A fresh config used slow defaults and ran at 10–15 fps with stalls up to 8.9 s and blurry/pixelated Handheld resolution. Settings for the measured build-95 session were GPU accuracy Low, async shaders and async presentation enabled, Docked, 8 GB memory layout, and NVDEC GPU. The report also describes Frizti v3 behavior separately: it skipped draws with no pipeline, averaging 26.0 fps in 30-fps mode (range 16.4–30), with revisits at 30.0 fps and no frames over 100 ms.

build 95 report

Statusruns with issues
GPURadeon 890M
CPURyzen AI Z2 Extreme
Driver32.0.32015.5008
Recorded FPS23–25 FPS

Problems or notes: The intro, Deku Tree cutscene, and initial gameplay rendered correctly, but the game froze at 0 FPS when Navi passed the Kokiri guard on the path to the Deku Tree. The report mentions texture format asserts and Unmapped Device ReadBlock errors.

build 117 (PGO) report

Statusruns with issues
GPURadeon 890M
CPURyzen AI Z2 Extreme
Driver32.0.32015.5008
Recorded FPS42–44 FPS

Problems or notes: The intro and cutscenes ran at 42–44 FPS and the game reached Kokiri Forest, but Unmapped Device ReadBlock errors and multi-second stalls were followed by a hard freeze before Navi reached the guard. The same errors occurred with memory layout set to both 12 GB and 4 GB.

nx2-build-95 report

Statusruns with issues
GPUNVIDIA GeForce RTX 2070
CPUIntel Core i7-12700KF
Driver616.92
Recorded FPSNot provided

Problems or notes: User reports that after the Kaepora Gaebora cutscene near Hyrule Castle, the area appears empty and foggy, Link falls through the world, and repeated void-outs prevent progression. Reported on Windows 11 25H2 in Handheld mode with Vulkan. The user says the issue reproduces 100% with the same save; listed configuration changes and disabling a built-in patch did not fix it.

Not provided report

Statusnot booting
GPUNVIDIA GeForce RTX 3050
CPUNot provided
Driver621.14.0.0
Recorded FPSNot provided

Problems or notes: Crashes during boot about 9–13 seconds after launch, after presenting its first frame, at an unimplemented nx2:vi2 function 201. The same crash is reported on builds 93 and 95.

build 88 and 93 report

Statusruns with issues
GPUGTX 1060 6gb
CPURyzen 5 5600
DriverNot provided
Recorded FPSNot provided

Problems or notes: A commenter reports missing textures in the Deku Tree after loading a save, across two game versions and builds 88 and 93. They also report that it worked the first time.

Not provided report

Statusunknown
GPURTX 5060
CPUNot provided
DriverNot provided
Recorded FPSNot provided

Problems or notes: The user says the game cannot run at 60 fps in the base village; no actual FPS or gameplay-start status is stated.

Not provided report

Statusplayable
GPURTX 4090
CPURyzen 9 7950x3D
DriverNot provided
Recorded FPSNot provided

Problems or notes: A commenter reports freezes of about 3 seconds with each step due to shader compilation. Another commenter says the game is completely playable for them and describes shader-compilation stuttering; no performance or sustained-play details are provided.

Not provided report

Statusruns with issues
GPUIntegrated graphics AMD (Radeon 860M, Ryzen AI 7 350, RADV / Mesa)
CPURyzen AI 7 350
DriverRADV / Mesa
Recorded FPS22–23 FPS

Problems or notes: During gameplay, the texture collector remains in aggressive mode, causing heavy image creation/deletion churn and frequent full GPU waits. Reporter measured 22.3 fps in two default runs and 22.5 fps in two override runs; these are standing FPS measurements, not a general performance result.

Related game issues

Compared with Previous Build

Current: build-117 (2 records); previous: build-116 (0 records).

The Legend of Zelda: Ocarina of Time Reported platform: Windows 11 runs with issues unknown playable not booting 8 reports

Also listed as: OoT

Lichii compatibility reports for The Legend of Zelda: Ocarina of Time
Build Status GPU / CPU FPS Details
build-93 runs with issues AMD Radeon RX 6900 XT / AMD Ryzen 9 5900X 24–30 FPS Open report

build-93 report

Statusruns with issues
GPUAMD Radeon RX 6900 XT
CPUAMD Ryzen 9 5900X
DriverNot provided
Recorded FPS24–30 FPS

Problems or notes: Severe lighting flickering and overexposure or corrupted lighting effects; significant slowdowns in some sequences; audio desynchronization during cinematics; initial shader compilation takes considerable time. The user reports approximately 24 FPS in Kokiri Forest and approximately 30 FPS in menus and some cinematics.

Related game issues

Compared with Previous Build

Current: build-93 (1 record); previous: build-88 (0 records).

Showing 71–80 of 194 reports

Known issues from Lichii sources

Known Game Issues

The Legend of Zelda: Ocarina of Time

The emulator closes when loading Hyrule Market after the user exits Kokiri Forest and enters Hyrule Castle.

Zelda: Ocarina of Time

The console restarts after the scene on Linux with a lenovo legion go 2 z2 and egpu 7600xt; the report names versions 83 et 93.

The Legend of Zelda: Ocarina of Time (Switch 2)

Two hidden/minimized Windows CLI launches crashed in nvoglv64.dll with exception 0xc0000094 at offset 0xEFC9BB. Static findings identify stale SDL visibility state and no zero-extent guard as possible leads, but neither is proven to cause the crash.

Other / not listed

An AMD Linux report describes GPU/display blackout and VK_ERROR_DEVICE_LOST on entering gameplay without EDEN_NX2_NO_MESH=1; the user reports at least five minutes of gameplay with the option enabled. Another AMD Linux report describes intermittent SIGSEGV crashes that occur with or without the option.

Other / not listed

Random dynarec crashes during gameplay, reported on Linux with AMD graphics cards; one report specifies an AMD RX 7000 series GPU.

Other / not listed

Overexposure in specific areas, including the lower part of Saria's house and the right side of the entrance to hyrule castle.

Ocarina of Time

Audio and video become desynchronized on the title screen, intro, and initial dream cutscene; a commenter reports slow-motion live-rendered video and an audio lead of approximately 3 seconds.

The Legend of Zelda: Ocarina of Time

On an AMD Radeon RX 6700 XT with AMD Software (Adrenalin) 26.10.2, Lichii closes during the first shader rebuild after about 9-10 minutes; Event Viewer reports an access violation in amdvlk64.dll.

Donkey Kong Bananza

On build 93, FPS fluctuates approximately between 20 and 60, with frequent periods around 30 and drops to 25–28 FPS in the Dragon Layer; GameSir G7 Pro rumble can be excessive, occur without an obvious trigger, or continue longer than expected.

Zelda: OoT Remake

Constant 4 FPS in-game on AMD Radeon RX 570 4GB.

Showing 261–270 of 361 issues

Notes de version récentes

Changements de compatibilité dans les dernières versions

Choix d’une version

Quelle version utiliser ?

Essayez la dernière version disponible : build-117. 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é.