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 Remake, OoT
| Build | Status | GPU / CPU | FPS | Details |
|---|---|---|---|---|
| nx2-9fa4a71fa0-nx2 | runs with issues | AMD Radeon RX 7600, 8 GB / AMD Ryzen 5 5500 | 15 FPS | Open report |
Problems or notes: Gameplay and movies run, but movie voices intermittently pause while video continues, causing late or absent audio. Gameplay was reported at about 15 fps in one test; another report recorded 15.4–19.4 average FPS over three sessions on build 9991f27, with hitches of 2–4 seconds and worst frames of several seconds. No driver crash or visual problems were noticed in the tested forest areas. Movie audio was not evaluated in the 9991f27 sessions.
Also listed as: OoT
| Build | Status | GPU / CPU | FPS | Details |
|---|---|---|---|---|
| build-93 | runs with issues | AMD Radeon RX 6900 XT / AMD Ryzen 9 5900X | 24–30 FPS | Open report |
| chuppatricky-amd-testbuild-v13 | not booting | AMD Radeon RX 6700 XT (12 GB) / AMD Ryzen 9 5900X | Not provided | Open report |
| build 97 | runs with issues | AMD RX 9000 series / Not provided | ?–20 FPS | Open report |
| Frizti v3 (tag: frizti-v3, based on Lichii nx2) | runs with issues | NVIDIA RTX 30 series or older / Not provided | Not provided | Open report |
| build 95 (222877d) | unknown | AMD RX 9000 series / Not provided | Not provided | Open report |
| Not provided | playable | AMD Radeon RX 6750 XT (RDNA2) / Ryzen 9 5900X | 26 FPS | Open report |
| Not provided | runs with issues | AMD Radeon RX 6800 XT (RDNA2) / Ryzen 7 9800X3D | Not provided | Open report |
| Not provided | runs with issues | AMD Radeon RX 6900 XT (RDNA2) / Intel i7-9700K | Not provided | Open report |
Problems or notes: Severe lighting flickering and overexposure or corrupted lighting effects; significant slowdowns in some sequences; audio desynchronization during cinematics; initial shader compilation takes considerable time. The user reports approximately 24 FPS in Kokiri Forest and approximately 30 FPS in menus and some cinematics.
Problems or notes: User reports the emulator closes without an error message after about 9–10 minutes of shader rebuilding on first launch. Windows reports exception code 0xc0000005 in amdvlk64.dll. The user says the same fault offset occurred across several launches.
Problems or notes: Around 20 FPS with large variance, bright light/haze-like artifacts, and desynchronized, stuttering audio after gameplay starts. The steps specify Lichii build 93 (MSVC Windows package), while the emulator build field says build 97.
Problems or notes: A massive white bloom streak blows out the upper-left quadrant of the screen in Kakariko Village during daytime; a commenter reports similar effects in the well, later areas, and frozen Zora's domain.
Problems or notes: Extract NUP fails when the output path is 264 characters long, reporting Extraction Failed.
Problems or notes: The report says v14 and v15 builds consistently crashed in amdvlk64.dll within 30–90 seconds. A custom build with the PR #629 fix loaded the main menu and save files, supported gameplay for 8+ minutes without a crash, and required no environment variable or manual workaround.
Problems or notes: Crashes about 50 seconds after boot while the disk pipeline cache is being prebuilt. The report says the latest nx2 build with EDEN_NX2_NO_COOP_MATRIX=1 compiles shaders and launches the game.
Problems or notes: Crashes about a minute after boot while prebuilding the disk pipeline cache. With EDEN_NX2_NO_COOP_MATRIX=1, Kokiri Forest ran for 20+ minutes at 29–31 FPS without a crash.
Current: build-93 (1 record); previous: build-88 (0 records).
| Build | Status | GPU / CPU | FPS | Details |
|---|---|---|---|---|
| build 117 (Windows PGO) | runs with issues | NVIDIA GeForce RTX 4070 Laptop GPU / AMD Ryzen 7 7745HX (laptop CPU) | Not provided | Open report |
Problems or notes: The user reports constant coil whine from the CPU area while playing; GPU usage is around 25-35% and CPU usage around 40-50%.
Showing 11–20 of 28 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
Für Ocarina of Time ist kein getesteter Build mit verfügbarem Download verknüpft. Sieh dir die aktuellen Releases oder die Diskussion zum Spiel im Issue-Tracker an.
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.