Spielekompatibilität
Du hast ein bestimmtes Spiel im Sinn? Erfahre, wie es mit Lichii läuft, welche Probleme bekannt sind und welchen Build du ausprobieren kannst.
Ein Spiel finden
108 Einträge zu Spielen und Testumgebungen sowie 308 Lichii-Berichte sind derzeit erfasst.
Dein Spiel fehlt? Ein leeres Suchergebnis bedeutet, dass noch kein Lichii-Bericht erfasst ist. Daraus lässt sich kein fehlgeschlagener Test ableiten.
An der Plattformangabe erkennst du, welche Version eines Spiels gemeint ist.
Was die Statuswerte bedeuten: Unknown bedeutet, dass kein Ergebnis feststeht. Not booting heißt, dass das Spiel nicht startete. Boots steht dafür, dass nur der Start gelang. Runs with issues bezeichnet Probleme beim Spielen. Playable heißt, dass der Tester weiterspielen konnte.
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, Ocarina of Time, OOT REMAKE
| Build | Status | GPU / CPU | FPS | Details |
|---|---|---|---|---|
| nx2 fork at 99ac3d5955 with local patches (commit 1e53321757) | runs with issues | RTX 5080 / Ryzen 9 7950X3D | Not provided | Open report |
| 09b78bd2df | runs with issues | GTX 1070 / Not provided | Not provided | Open report |
| Not provided | runs with issues | GTX 1070 / Not provided | Not provided | Open report |
| a7a281757da390ce45070e772784e0333831bb25 | runs with issues | NVIDIA GeForce GTX 1080 / AMD Ryzen 9 3900X | Not provided | Open report |
| build-95 | runs with issues | RTX 4070 Ti SUPER / Not provided | Not provided | Open report |
| 95 | not booting | AMD Radeon RX 7900 XTX (RADV) / Intel Core i7-11700K | 0 FPS | Open report |
| Build 95 | not booting | AMD Radeon RX 5700 XT (RADV NAVI10) / AMD Ryzen 5 3600 6-Core Processor | Not provided | Open report |
| Build 95 | not booting | NVIDIA GeForce RTX 3050 Laptop GPU / i5-12500H | Not provided | Open report |
| nx2 @ 89440b29a9 | runs with issues | Not provided / Not provided | Not provided | Open report |
Problems or notes: A user comment reports a median frame time of 22.4 ms in Kokiri Forest and CPU time concentrated on the GPUBack thread, with the GPU front thread mostly waiting. This is a user measurement, not an official compatibility result.
Problems or notes: A merged user report says a door and most vegetation are missing. It attributes the symptom to mesh-shader pipelines being skipped when VK_EXT_mesh_shader is unavailable; the reporter could not confirm on screen that the missing objects corresponded exactly to those draws.
Problems or notes: A draft compute-based fallback reportedly rendered falling leaves, ground leaves, and some foliage shadows with correct textures, but the emulated geometry flickered and canopies, grass, and house walls remained missing.
Problems or notes: Missing leaves, foliage, walls, textures, and other geometry. The report says attempted recompilation and builds 78, 88, 92, Fritzi v2, and perf/Fritzi-Intergrated did not resolve the issue; comments report that #395, #434, and #430 did not restore the geometry.
Problems or notes: Large flat red patches appear across the wet stream bed by the road from Castle Town Market to Hyrule Castle. Another user later reported that stream as clean with their build, attributing the earlier difference possibly to missing #432 and #351; this report's setup used build-95.
Problems or notes: Stalls at a black screen; repeated native MME macro execution failures are reported. Enabling compute pipelines, clearing pipeline caches, and disabling implicit Vulkan layers did not resolve the issue.
Problems or notes: A user-provided build-95 log shows the game loading, followed by a compute pipeline compilation error and an unhandled SIGSEGV. The user later supplied crash details indicating a null-pointer dereference. The log identifies KDE neon User Edition as the host OS.
Problems or notes: Black screen at the intro video after the loading shaders screen; music continues, FPS counter stays at 0, and GPU channels wait on unreleased semaphores. Build 93 reaches gameplay on the same machine. Two other users report the same build 95 hang on Linux with NVIDIA RTX 3060 and RTX 3090 systems. Two users say EDEN_NX2_SPLIT=1 makes the game work.
Problems or notes: User reports that motion controls are affected: Motion 1/Motion 2 mapping does not detect shaking, and gyro/accelerometer input stops after the controller reconnects or after a few seconds with Steam running.
Current: build-93 (3 records); previous: build-88 (0 records).
Also listed as: OoT
| Build | Status | GPU / CPU | FPS | Details |
|---|---|---|---|---|
| Not provided | not booting | AMD Radeon RX 6700 XT (12 GB) / AMD Ryzen 9 5900X | Not provided | Open report |
Problems or notes: On first launch, shader rebuild runs for about 9-10 minutes, then Lichii closes with no error message. The reported Event Viewer faulting module is amdvlk64.dll with exception code 0xc0000005.
Showing 91–100 of 194 reports
Known issues from Lichii sources
On Build 95 Non-PGO in Linux AMD RADV, the game remains black-screened while intro audio plays, even after shader compilation. The symptom persisted across the reported Wayland/XWayland and environment-variable tests, and after removing Vulkan Pipeline Cache and Cache Storage.
Build 117 renders again, but the user reports substantial FPS and frametime variability, including drops to 19 FPS.
Severe performance, around 8 FPS (approximately 123 ms frame time), on macOS with Apple M5 using Vulkan / MoltenVK at 1x resolution; the report also says MoltenVK fallback warnings occur. A commenter reports the same issue on Mac M4.
A user reports that DLSS replacement does not detect the game's DLSS evaluation in Fire Emblem: Fortune's Weave: no Game DLSS network or NVIDIA DLSS (Streamline) line appears, while guest tensor operations run on cooperative matrices and GPU usage is high.
Building mesh shaders can cause a hard crash on AMD 7000 series and some other AMD cards; on Linux this may freeze the system, while on Windows it crashes the emulator.
Recorded fix: A commenter reports that setting EDEN_NX2_FORCE_MESH_FALLBACK = "1" allowed loading a save without a crash by using the compute fallback. Another commenter confirmed the setting worked and said they entered the game.
On build 117, the game shows a black screen while background music plays and does not load, reported with an AMD RX 6000 series or older GPU on Windows 11.
AMD GPU users report Vulkan VK_ERROR_DEVICE_LOST crashes around the intro-to-gameplay transition or while loading a save. Reports include RX 7800 XT, RX 9070 XT, and RX 6900 XT systems; the issue is not universal across all reports or tested builds.
Some users report crashes or black screens after trying the EDEN_NX2_NO_MESH=1 workaround; results vary by GPU, operating system, and build.
Water Temple walls have missing textures and appear invisible; a commenter confirmed that the reported ROM dump was missing data.
Recorded fix: Use a clean game dump; one user reported that this resolved the issue.
A commenter reports white flashes or missing textures on Windows 11 with some RTX and AMD graphics cards, and another reports missing textures in the Deku Tree after loading a save.
Showing 41–50 of 361 issues
Aktuelle Release-Hinweise
Build build-117 · Ocarina of Time
Build build-116 · Zelda: Ocarina of Time
Build build-116 · Zelda: Ocarina of Time
Build build-116 · Zelda: Ocarina of Time
Build build-116 · Mario Tennis Fever
Den passenden Build finden
build-117 · Veröffentlicht am November 7, 2026
12 veröffentlichte Downloaddateien für diesen Build.
Probiere den neuesten verfügbaren Release aus: build-117. Behalte beim Testen einen funktionierenden Build, zu dem du zurückkehren kannst.
Fragen zur Kompatibilität
Setze die Filter für Spiel, Status, GPU und Build und kopiere anschließend die Seitenadresse. Ein direkter Link zum Spiel öffnet dessen Berichtskarte.
Prüfe in anderen Berichten, ob das Spiel bis zum Menü oder ins Spielgeschehen gelangt. Notiere Treiber und Renderer und suche nach dem Spiel oder dem Fehler in der Anleitung zur Fehlerbehebung.
Treiberversion, Grafikeinstellungen, CPU-Auslastung und die getestete Spielszene können das Ergebnis beeinflussen. Vergleiche diese Details, bevor du deine Konfiguration änderst.
Nutze den offiziellen Issue-Tracker von Lichii. Nenne das Spiel, den Build-Tag, Hardware, Treiber, Einstellungen und die Schritte, mit denen sich deine Beobachtung reproduzieren lässt.