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: Ocarina of Time, Zelda: Ocarina of Time, OoT, Zelda OoT, TLoZ: OoT
| Build | Status | GPU / CPU | FPS | Details |
|---|---|---|---|---|
| Frizti v2 (765659af4) | playable | RTX 5090 / Ryzen 9800X3D | 53.66 FPS | Open report |
| build 80 (Lichii Development Build | fix/oot-upscaler-gathers-build-80) | runs with issues | Radeon RX 9070 16 GB / Ryzen 5 7500F | Not provided | Open report |
| current nx2 | playable | RTX 4070 SUPER / Not provided | Not provided | Open report |
| nx2-build-83 | runs with issues | AMD RX 9000 series / Not provided | 41 FPS | Open report |
| Not provided | runs with issues | RX 7900 XTX / Not provided | Not provided | Open report |
| build -88 MSVC 19.44.35229.0 | runs with issues | AMD RX 9000 series; RX 9060XT 16GIG / Ryzen 7 5700X | Not provided | Open report |
| nx2-build-88 | not booting | AMD Radeon RX 6600 / AMD Ryzen 5 5600 6-Core Processor | 0 FPS | Open report |
| v93 | runs with issues | RX 9070 XT and RX 5700 / Not provided | 15–30 FPS | Open report |
| Not provided | runs with issues | AMD Radeon RX 7800 XT / Not provided | Not provided | Open report |
| build 95 | runs with issues | AMD Radeon RX 9070 XT / Not provided | Not provided | Open report |
Problems or notes: A user comment reports 53.66 presents/s in a stationary village view and a limited continuous gameplay check through the training-area crawl passage to the maze entrance and back to the east pond/Mido approach. Native 60 FPS was not locked; the Deku Tree and later areas were not tested, and the release's overexposure warning was not cleared.
Problems or notes: The title screen rendered normally, but after starting a new game the world rendered almost entirely black, with only the HUD, areas lit by Navi and around Link's feet, and some blown-out white shapes visible. Multi-second stalls of 6.4 s and 5.6 s occurred during pipeline building and ASTC decodes. The report used Vulkan, 1x resolution, ScaleForce, and FIFO vsync on Windows 11 25H2. The closing comment says later builds include many Ocarina of Time fixes but does not confirm this issue was fixed.
Problems or notes: Commenter reports the over-bright, washed-out rendering is gone and says the title was played for about 20 minutes without stretched/exploded environment geometry recurring. The specific build changes responsible are unknown.
Problems or notes: The issue author reports audio running ahead of the video, cutting out and repeating during the opening cutscene, followed by a full computer freeze at the Deku Tree cutscene. Reported settings: Vulkan, GPU Mode Fast, Docked, Bilinear window adapting filter, and no anti-aliasing.
Problems or notes: A commenter reports an AMD driver timeout and GPU reset when control of Link begins, attributing it to an ambient-lighting compute dispatch. They say PR #206 fixes that timeout in their testing, but note it does not fix separate pipeline-build crashes or black-world problems.
Problems or notes: The user reports audio delays after scenes, followed by a black screen and emulator crash. A commenter reports a similar crash on Linux with AMD graphics.
Problems or notes: User reports a permanent black-screen freeze at “Building: 13 shader(s)” during the initial AV1 title screen video decoding sequence with Vulkan, GPU Mode Low/Fast, and Asynchronous Shaders enabled. The emulator shows 0 FPS and requires forced termination. The same user reports that an NVIDIA RTX 2060 boots and renders 3D gameplay with the same portable-folder configuration. Another user reports the issue on an RX 6600M.
Problems or notes: A user reports FPS between 15 and 30 with constant drops and GPU usage frequently reaching 100%.
Problems or notes: A user reported a magenta zigzag line along the Hyrule Field mountain ridge, then reported that a proposed shader-output write-mask fix removed it. This was a user report, not a maintainer-confirmed test.
Problems or notes: A user reported coloured blocks along the Hyrule Field horizon on an earlier local build, with a separate distant-horizon glow. They reported the coloured blocks gone after applying #353 in a later build; the glow remained.
Current: build-117 (2 records); previous: build-116 (0 records).
Showing 31–40 of 142 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-75 · Veröffentlicht am November 5, 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.