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
98 Einträge zu Spielen und Testumgebungen sowie 275 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 @ 27226d2 plus two measurement-only commits | runs with issues | RTX 5060 Laptop (8 GB) / Ryzen AI 9 365 | Not provided | Open report |
| Lichii nx2 build 88 | boots | Intel Arc / Not provided | 1 FPS | Open report |
| nx2 build 88 | not booting | NVIDIA RTX 3060 / Ryzen 7 5700X | Not provided | Open report |
| Not provided | runs with issues | AMD Radeon RX 9070 XT / Not provided | Not provided | Open report |
| Build-93 MSVC 19.44.352995.0 | runs with issues | RX 9060XT 16GB / Ryzen 7 5700X | 1–30 FPS | Open report |
| nx2-9fa4a71fa0-nx2 | runs with issues | AMD Radeon RX 7600, 8 GB / AMD Ryzen 5 5500 | 15 FPS | Open report |
Problems or notes: In the Kokiri Forest scene, disabling per-fence Preflushable downloads or batching them by 64 fences increased GPU back-thread draws per second but broke auto-exposure, leaving the scene overexposed. Default downloads preserved correct exposure. The issue reports measurements, not a gameplay FPS result.
Problems or notes: The issue title reports about 1 FPS in the main menu and first cutscene. A comment reports about 9 FPS in the opening cutscene on an Intel Arc B580 with driver 101.9150 and Lichii v2.
Problems or notes: The user's .NUP dump remains on the Launching screen and does not start. Keys and firmware 23.0.1 were installed, but the issue persisted. The earlier launch log showed an ARM exception after unmapped memory accesses, but may have come from a separate troubleshooting launch and needs confirmation.
Problems or notes: In docked mode, a dotted cyan/magenta line appeared along mountain and sky silhouettes in Hyrule Field. The issue author reports that the line disappeared after the fix was tested.
Problems or notes: User reports occasional audio loss, frame-rate drops from 30 to 1 that recover to 30, a missing sky replaced by bright light, and a missing map. The report also lists AMD RX 9000 series as the graphics card.
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.
| Build | Status | GPU / CPU | FPS | Details |
|---|---|---|---|---|
| nx2-build-88 | runs with issues | Intel Arc B580 (BMG G21) / Ryzen 5 5600X | 8 FPS | Open report |
Problems or notes: A user reports about 8 FPS in the intro after a multi-minute shader stall on first boot. The Kokiri intro cutscene picture froze while presents continued. These are user reports.
| Build | Status | GPU / CPU | FPS | Details |
|---|---|---|---|---|
| build-117 | unknown | Not provided / Not provided | Not provided | Open report |
| Lichii Build 95 | not booting | RTX 3050 6GB / i7-13620H | 0 FPS | Open report |
| Not provided | runs with issues | AMD RX 6000 series or older / Not provided | Not provided | Open report |
Problems or notes: A commenter says it runs much better for them on Linux than on Windows 11; no gameplay or FPS details are provided.
Problems or notes: User reports sound from the intro but no video. A comment says Build 116 was worse; another reports the game ran much better for them on Build 117.
Problems or notes: User reports random freezes after 5–15 minutes of play, I/O spikes up to 6GB/s, RAM use continuing to rise until out-of-memory forces the emulator to crash.
Current: build-117 (1 record); previous: build-116 (0 records).
Showing 11–20 of 194 reports
Known issues from Lichii sources
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.
A user reports a black screen and around 2 FPS on macOS with build 95 on an Apple M1 Pro; shader compilation eventually finishes, but no title screen or gameplay is visible.
During movies, including the title-screen background, the six movie audio voices can pause while the picture continues, resulting in late or silent audio. The issue varied between sessions and was also reported on builds without the movie-sync patch.
Town vegetation and small clutter render at a distance but disappear when approached; reports also mention tree leaves vanishing up close and changing shadows.
ZL input is not detected during the shield tutorial, leaving the tutorial stuck in a loop.
Recorded fix: Fixed in build 95.
User reports pixelated, blurry graphics and somewhat slow FPS on integrated AMD graphics in Windows 11.
Showing 101–110 of 287 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.