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, OoT
| Build | Status | GPU / CPU | FPS | Details |
|---|---|---|---|---|
| build-88 | playable | AMD Radeon RX 7900 XTX / Ryzen 9 3950X | 24–44 FPS | Open report |
| build-83 | runs with issues | AMD Radeon RX 9060 XT 16 GB / Intel i7-9700K | Not provided | Open report |
| build-75 | runs with issues | AMD Radeon RX 7900 XTX / Not provided | 12 FPS | Open report |
| Lichii build 83 (MSVC) | runs with issues | NVIDIA GeForce GTX 1070 / Intel Core i7-7700 | 18 FPS | Open report |
| official build88 (55532f2), standard MSVC package | playable | RTX 5090 / Ryzen 7 9800X3D | 47.64–59.9 FPS | Open report |
| 95 | playable | NVIDIA RTX 3070 8 GB / Ryzen 7 5700X (8C/16T) | 32.82–40.75 FPS | Open report |
| Not provided | runs with issues | NVIDIA RTX 3060 12 GB / i5-13600KF | Not provided | Open report |
| Not provided | runs with issues | RTX 4080 SUPER / Not provided | 20 FPS | Open report |
| Not provided | runs with issues | RTX 5080 / Ryzen 9 9950X3D | Not provided | Open report |
| Not provided | runs with issues | RX 6700 XT / Not provided | Not provided | Open report |
Problems or notes: Reported performance varied with settings; GPU accuracy Low, reactive flushing off, and asynchronous shaders on improved performance.
Problems or notes: The GPU device was lost when gameplay started.
Problems or notes: The 3D scene was black with only the HUD visible.
Problems or notes: A user comment reports approximately 18 FPS and frequent hangs or stalls; their trigger and duration were not isolated.
Problems or notes: A user comment reports local native-present averages of 59.90 FPS at the Mido viewpoint at 1X, 49.53 FPS in a central village tree view at 1X, and 47.64 FPS in that view at 2X. New-area shader hitches occurred. The village/pond check retained three hearts, but the Training Grounds/maze transition and later game were not verified.
Problems or notes: User reports 32.82 / 34.09 FPS with pinning disabled and 40.75 / 39.84 FPS with pinning enabled; no crash in 2,383 recorded intervals. The user reports that sustained 60 FPS was not achieved. Testing used Vulkan, Fast GPU accuracy, Docked, 1x resolution, and 100% speed.
Problems or notes: Freezes in the Hyrule Castle Town guard house when walking toward the guard or looking toward the wall with windows. The report reproduces on multiple builds and GPUs. A commenter reports that a texture pool patch in Frizti v3 stopped the freeze, but the room still had low performance after further texture-cache changes.
Problems or notes: A commenter reports the guard-house freeze on Frizti v3. A texture pool patch reportedly stopped the freeze, but the room's performance remained low, with a floor of about 20 fps after additional texture-cache changes.
Problems or notes: A commenter reports the same guard-house freeze, both while talking to the guard and while moving around inside.
Problems or notes: A commenter reports crashes in the guard house, reproduced 5/5 times while looking toward the wall with windows and panning the camera. A reported VRAM allocation burst preceded the crashes; whether memory pressure caused them was unclear.
Current: build-93 (1 record); previous: build-88 (2 records).
Showing 221–230 of 308 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
Wähle oben ein Spiel aus, um zu sehen, welche getesteten Builds zum Download verfügbar sind. Bis dahin kannst du den neuesten veröffentlichten Build verwenden und seine Release-Hinweise lesen.
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.