Compatibilidad de juegos
¿Tienes un juego en mente? Comprueba cómo funciona en Lichii, revisa los problemas detectados y elige una versión para probar.
Encuentra un juego
Los datos actuales incluyen 58 registros de juego y entorno y 114 informes sobre Lichii.
¿No encuentras un juego? Si no hay resultados, aún no se muestra ningún informe de Lichii sobre ese juego. No significa que haya fallado una prueba.
Fíjate en la plataforma indicada para distinguir entre distintas versiones de un juego.
Qué significa cada estado: «Unknown»: sin conclusión. «Not booting»: el juego no arrancó. «Boots»: solo se confirmó el arranque. «Runs with issues»: hubo problemas durante la partida. «Playable»: la persona que hizo la prueba pudo seguir jugando.
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 |
|---|---|---|---|---|
| build-83 | runs with issues | NVIDIA RTX 50 series / Not provided | Not provided | Open report |
Problems or notes: User reports a crash after about 15 to 20 minutes. The user also reports having 16GB of RAM.
Current: build-83 (1 record); previous: build-75 (0 records).
| Build | Status | GPU / CPU | FPS | Details |
|---|---|---|---|---|
| build-83 | runs with issues | AMD RX 9000 series / Not provided | Not provided | Open report |
Problems or notes: The emulator crashes after 5 to 10 minutes of gameplay.
Current: build-83 (1 record); previous: build-75 (0 records).
| Build | Status | GPU / CPU | FPS | Details |
|---|---|---|---|---|
| build-83 | not booting | Other / Not provided | Not provided | Open report |
Problems or notes: User reports that the game blacks out when booted. They identify this as a regression from build 75.
Current: build-83 (1 record); previous: build-75 (0 records).
| Build | Status | GPU / CPU | FPS | Details |
|---|---|---|---|---|
| build-83 | runs with issues | intel uhd graphics / intel core i5 gen 13th | Not provided | Open report |
Problems or notes: User reports missing textures and buggy visuals after booting, occasional crashes during startup, and crashes when playing the Grand Prix race.
Current: build-83 (1 record); previous: build-75 (0 records).
| Build | Status | GPU / CPU | FPS | Details |
|---|---|---|---|---|
| build-83 | playable | RTX 4070 Ti / Ryzen 7 7700X | Not provided | Open report |
Problems or notes: Vulkan, docked, 2x, GPU accuracy Low, game version 1.1. User reported haze gone and Link and Kokiri Forest clearly visible in gameplay, but FPS was described as low. Handheld mode was not tested.
From build-75 to build-83: follow the gameplay changes described for these two builds.
Before: Missing vegetation and incorrect material data; affected lighting and colours; a glowing doorway; one-frame white flashes; and on AMD, shaders could produce a black 3D scene.
After: Additional shader pointers and storage-buffer bindings, corrected buffer tracking and mesh-shader register handling, fixed occlusion-query and nested-return handling, and added the Max Resolution add-on and frame-ahead presentation tuning.
build-75 → build-83
| Build | Status | GPU / CPU | FPS | Details |
|---|---|---|---|---|
| build-83 | runs with issues | AMD Radeon RX 9060 XT 16 GB / Intel i7-9700K | Not provided | Open report |
Problems or notes: User reports say the game reaches gameplay and then loses the GPU device. The report also mentions black output after rejecting selected shaders and a later device loss. All tried settings and environment-variable changes still resulted in device loss.
Current: build-83 (1 record); previous: build-75 (2 records).
Also listed as: OoT
| Build | Status | GPU / CPU | FPS | Details |
|---|---|---|---|---|
| build-83 | runs with issues | RTX 5090 / Ryzen 7 9800X3D | 34.04–46.28 FPS | Open report |
Problems or notes: User report: Native gameplay remained below 60 FPS after shader warmup. Measurements varied by scene and settings; walking, camera movement, ladder climbing, NPC dialogue, autosave, and loading an outdoor save worked in a limited test. Audio was not assessed.
Current: build-83 (1 record); previous: build-75 (1 record).
| Build | Status | GPU / CPU | FPS | Details |
|---|---|---|---|---|
| build-83 | runs with issues | RX 9060 XT 16 GB / Not provided | Not provided | Open report |
Problems or notes: User reports that the black-screen behavior is gone and the game reaches gameplay, but it device-loses at gameplay start with VK_ERROR_DEVICE_LOST.
Current: build-83 (1 record); previous: build-75 (0 records).
Also listed as: OoT
| Build | Status | GPU / CPU | FPS | Details |
|---|---|---|---|---|
| build-83 | not booting | AMD RX 6000 series or older; AMD RX 6600 8GB / Not provided | Not provided | Open report |
Problems or notes: The issue reporter says the emulator begins loading and then stays on a black screen. This is an open issue.
Current: build-83 (1 record); previous: build-75 (0 records).
Also listed as: OoT
| Build | Status | GPU / CPU | FPS | Details |
|---|---|---|---|---|
| build-83 | runs with issues | RTX 5090 / Ryzen 7 9800X3D | Not provided | Open report |
Problems or notes: Opening rendered and controllable Kokiri Forest gameplay was reached. Some sessions hung at “Closing software…” during shutdown, while others exited successfully. The source does not establish a cause or fix.
Current: build-83 (1 record); previous: build-75 (0 records).
Showing 1–10 of 13 reports
Known issues from Lichii sources
A half-resolution layer drawn by pixel shader c72b6ea746c00433 causes dark blotches and translucent patches over objects in reported scenes. Users traced the issue to an occlusion-depth copy being wiped by deferred clears before the layer samples it.
Recorded fix: A user-reported workaround is EDEN_NX2_REJECT_HASH=c72b6ea746c00433; it removes the blotches in tested scenes but removes the river's visible water surface. Another user described PR #185 as fixing the ordering issue, but did not provide a tested result for that fix.
The Deku Tree exterior cutscene can render black except for a small area around Navi; a user also reported an AMD graphics-driver crash while building graphics pipelines in that scene.
Users reported missing grass, ferns, and broadleaf vegetation, with associated haze or overexposure in Kokiri Forest. A user reported that a local build with listed rendering commits restored grass and ferns and removed heavy haze in one location; a later comment proposed PR #204 for stale occlusion-query reads, but did not report a test result for that PR.
A user reported river-water flicker depending on sun direction relative to the camera; the proposed link to lighting or light volumes was unconfirmed.
A user reported zero-format texture assertions, Unmapped Device ReadBlock errors, and flickering terrain and subtitles; causation was not established.
On AMD RDNA2 GPUs, the game may freeze during shader or pipeline building, sometimes with background audio continuing. A commenter also reports black-screen or shader-building hangs with asynchronous shader compilation enabled.
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.
Recorded fix: Leave the game at the intro for about 20 minutes once so both pipelines finish and are cached; later boots reportedly pass the intro immediately until the driver or Lichii is updated. Alternatively, set `EDEN_NX2_REJECT_HASH=eff3ccbe1438679d,f9ea14a22394f5b1`; this avoids the wait but leaves parts of the picture black.
In the measurement-only experiment, disabling per-fence Preflushable downloads or batching downloads by 64 fences caused overexposure in Kokiri Forest.
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.
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.
Showing 21–30 of 98 issues
Notas de versiones recientes
Versión build-88 · No indicado
Versión build-88 · No indicado
Versión build-88 · No indicado
Versión build-88 · Zelda: Ocarina of Time
Versión build-83 · Ocarina of Time
Elegir una versión
Elige un juego arriba para ver qué versiones probadas puedes descargar. Mientras tanto, usa la descarga más reciente y lee sus notas.
Prueba la última versión disponible: build-88. Conserva una versión que funcione por si necesitas volver a ella durante las pruebas.
Dudas sobre compatibilidad
Aplica los filtros de juego, estado, GPU y versión y copia la URL de la página. Un enlace a un juego concreto abre su ficha de informes.
Revisa en otros informes si el juego llega a los menús o permite jugar. Anota el controlador y el motor de renderizado y busca el juego o el error en la guía de solución de problemas.
La versión del controlador, los ajustes gráficos, la carga de la CPU y el tramo del juego que se prueba pueden cambiar el resultado. Compara estos detalles antes de cambiar tu configuración.
Usa el gestor oficial de incidencias de Lichii. Indica el juego, la etiqueta de la versión, el hardware, el controlador, los ajustes y los pasos para reproducir lo que viste.