Other / not listed
User reports a crash when booting the game in build 88 after it worked in build 75.
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 76 registros de juego y entorno y 175 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-75 | runs with issues | RTX 5070 Ti / Not provided | Not provided | Open report |
| 99ac3d595 plus listed cherry-picked commits | playable | RTX 5070 Ti / Not provided | 38 FPS | Open report |
Problems or notes: Docked, 1x. User reported missing vegetation, heavy white glow, and visual blotches in tested scenes. Rejecting shaders with EDEN_NX2_REJECT_HASH visibly improved Link and the foreground, but removed bloom accumulation and the river surface.
Problems or notes: Docked, 1x, in front of the Deku Tree in Kokiri Forest. Grass and ferns drew and the heavy haze was gone in a short, still-camera test. Other areas, interiors, cutscenes, long sessions, river rendering, and blotches were not verified. User reported about 38 FPS.
Current: build-75 (1 record); previous: build-70 (0 records).
| Build | Status | GPU / CPU | FPS | Details |
|---|---|---|---|---|
| build-94 | not booting | Radeon RX 7800 XT / Not provided | Not provided | Open report |
| build-94 | not booting | RTX 5070 / Ryzen 5 7600X | Not provided | Open report |
Problems or notes: Without the workaround, a black screen with audio and repeated split-front macro errors; only presents #1 through #8 occurred before rendering stopped. With EDEN_NX2_SPLIT=1, the game rendered and reached present #1200 about 47 seconds after launch.
Problems or notes: Black screen and emulator hang about 26 seconds after boot with split-front macro errors. EDEN_NX2_SPLIT=1 was reported to make it run normally in a 60-second test.
Current: build-94 (2 records); previous: build-93 (0 records).
| Build | Status | GPU / CPU | FPS | Details |
|---|---|---|---|---|
| build-93 | runs with issues | AMD RX 7000 series; Radeon RX 7900 XTX / AMD Ryzen 9 7900X | Not provided | Open report |
Problems or notes: Title screen and first cutscene work, but the game crashes immediately after the first cutscene. The report identifies the game as “Other / not listed” and refers to it as Ocarina of Time Remake (Update 1.1.1).
Current: build-93 (1 record); previous: build-88 (0 records).
| Build | Status | GPU / CPU | FPS | Details |
|---|---|---|---|---|
| build-93 | runs with issues | Radeon 5700 XT / AMD Ryzen 6 3600 | Not provided | Open report |
Problems or notes: User reports the emulator hangs and crashes at 11/14 shaders loaded when booting Ocarina Of Time Remake. They say the issue also occurs in Build-88, while Build-83 works; results are the same handheld or docked and on x11 or wayland. The report also identifies the graphics card as AMD RX 6000 series or older.
Current: build-93 (1 record); previous: build-88 (0 records).
| Build | Status | GPU / CPU | FPS | Details |
|---|---|---|---|---|
| build-75 | runs with issues | NVIDIA GeForce RTX 5080 (16 GB) / Intel Core Ultra 7 270K Plus (24 threads) | 28–29 FPS | Open report |
Problems or notes: User report: Docked mode was required to render; Handheld showed a black 3D screen. Gameplay settled at 28–29 FPS, while menus and loading screens ran at 53–59 FPS. The report attributes the limit to CPU load. No attempted settings changes improved the gameplay ceiling.
Current: build-75 (1 record); previous: build-70 (0 records).
| Build | Status | GPU / CPU | FPS | Details |
|---|---|---|---|---|
| build-75 | runs with issues | NVIDIA RTX 3050 Laptop / AMD Ryzen 7 5800H | 30 FPS | Open report |
Problems or notes: User report: The game boots and presents frames at a steady 30 FPS, but remains on a black screen after its AV1 video streams fail because FFmpeg has no decoder for "video/av1". NVDEC Off and Gpu reportedly make no difference; the same result was reported on an AMD Radeon iGPU. Vulkan was used.
Current: build-75 (1 record); previous: build-70 (0 records).
| Build | Status | GPU / CPU | FPS | Details |
|---|---|---|---|---|
| 75 (`nx2-build-75`, Linux x86_64 PGO AppImage) | runs with issues | AMD RX 7000 series (Radeon RX 7600, RADV 26.2.5, Vulkan 1.4.354) / Not provided | Not provided | Open report |
Problems or notes: During the intro AV1 cutscene, the video area is solid green; audio and subtitles work. The report says decoded frames are produced at 60 fps, but the image does not reach the screen.
| Build | Status | GPU / CPU | FPS | Details |
|---|---|---|---|---|
| `nx2-build-75`, MSVC x86_64 (`lichii-windows-x86_64.zip`) | runs with issues | AMD Radeon RX 6700 XT 8 GB, AMD driver 2.0.353, Vulkan 1.4.315 / AMD Ryzen 7 5800X, 32 GB RAM | Not provided | Open report |
Problems or notes: The game renders normally before the intro AV1 cutscene, but the video layer is black while audio and subtitles work, then the emulator hangs indefinitely. The report says the freeze starts when the AV1 decoder opens.
Showing 11–20 of 114 reports
Known issues from Lichii sources
User reports a crash when booting the game in build 88 after it worked in build 75.
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.
Commenters report rendering failures, black screens, and AMD driver crashes; one reports that audio continues while rendering is crashed.
On AMD RX 7000 series, NaNs from FMin, FMax, and FClamp can spread through bloom, producing a yellow-white sky and green shimmering water.
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.
Persistent graphics pipeline cache entries are reportedly rebuilt on the GPU thread during gameplay on repeated boots, causing a visible hitch.
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.
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.
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.
In stages past the first one, the gameplay screen is black while the UI remains visible; pausing shows the world rendered in the background.
Showing 131–140 of 188 issues
Notas de versiones recientes
Versión build-94 · Ocarina of Time
Versión build-94 · No indicado
Versión build-94 · No indicado
Versión build-94 · No indicado
Versión build-94 · No indicado
Elegir una versión
build-75 · Publicada el November 5, 2026
12 archivos para descargar en esta versión.
Prueba la última versión disponible: build-94. 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.