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 |
|---|---|---|---|---|
| Not provided | unknown | RTX 5060 / Not provided | Not provided | Open report |
| Not provided | playable | RTX 4090 / Ryzen 9 7950x3D | Not provided | Open report |
| Not provided | runs with issues | Integrated graphics AMD (Radeon 860M, Ryzen AI 7 350, RADV / Mesa) / Ryzen AI 7 350 | 22–23 FPS | Open report |
Problems or notes: The user says the game cannot run at 60 fps in the base village; no actual FPS or gameplay-start status is stated.
Problems or notes: A commenter reports freezes of about 3 seconds with each step due to shader compilation. Another commenter says the game is completely playable for them and describes shader-compilation stuttering; no performance or sustained-play details are provided.
Problems or notes: During gameplay, the texture collector remains in aggressive mode, causing heavy image creation/deletion churn and frequent full GPU waits. Reporter measured 22.3 fps in two default runs and 22.5 fps in two override runs; these are standing FPS measurements, not a general performance result.
Current: build-117 (2 records); previous: build-116 (0 records).
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 |
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.
Current: build-93 (1 record); previous: build-88 (0 records).
Showing 61–70 of 142 reports
Known issues from Lichii sources
When fastmem could not be created, guest code ran about 1.4x slower; Kokiri Forest ran at 22.2–26.6 FPS rather than 28.5–33.8 FPS. The report attributes the slow boots to failure to allocate 14336 MiB of backing memory.
Recorded fix: Change #645 retries the section after a private commit that grows the page file; in eight back-to-back boots, all three initial failures recovered on the second attempt and none ran slowly.
Graphics fail to load in the Water Temple; a commenter describes the area as unplayable.
Recorded fix: A commenter reports resolving the issue by using a NUP containing the missing texture files, described as 23.8 GB rather than 23.3 GB.
Many Water Temple rooms are invisible, with transparent walls. A comment attributes this to a damaged texture file in the game dump; another user reports the issue was resolved by making a fresh dump with a NUP with a higher file size.
On AMD Windows proprietary drivers, older builds can lose the GPU device when gameplay or a save starts; build-83 and build-88 reports include this problem.
Recorded fix: A Windows RX 9060 XT report found the issue absent in build-93. A Windows RX 7900 XTX report also found it absent in the CI build at 18cfe85.
On AMD RADV Mesa 26.2.4, task/mesh shader use can hang the GPU and cause device loss during 3D gameplay.
Recorded fix: The reporter found that updating to Mesa RADV 26.2.6 avoided the hang on the same GPU with the same build. If using a distrobox in gamescope gaming mode, the reporter says to install the gamescope package in the container so its Vulkan WSI layer is present.
On build-95, the user reports draws held while unbuilt pipelines are being built, causing multi-second stalls, even with async shaders enabled.
The user reports that a fresh build-95 config starts with slow defaults, including High GPU accuracy, asynchronous shaders off, async presentation off, Handheld mode, 4 GB memory layout, and CPU NVDEC; the game ran at 10–15 fps with stalls up to 8.9 s and blurry/pixelated Handheld resolution.
Recorded fix: The user reports that writing the six listed settings before launch helped: gpu_accuracy=0, use_asynchronous_shaders=true, async_presentation=true, nvdec_emulation=2, memory_layout_mode=2, and use_docked_mode=1; set each key's \default= line to false as well.
User reports a black-screen stall after the first AV1 frame with async GPU emulation enabled on AMD Radeon RX 6800 XT; with async GPU emulation disabled, the game later froze during gameplay.
Users report failure to start, black screens with 0 FPS, or emulator crashes in builds 88–95, including a build-95 Linux report with an unhandled SIGSEGV and null-pointer dereference. The comments caution that the reports may have different causes.
The user reports performance remaining at 20 FPS with music glitches on macOS.
Showing 121–130 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.