Spielekompatibilität

Spielekompatibilität des Lichii Emulators

Du hast ein bestimmtes Spiel im Sinn? Erfahre, wie es mit Lichii läuft, welche Probleme bekannt sind und welchen Build du ausprobieren kannst.

Ocarina of Time im Lichii Emulator, aus GitHub-Issue 201
Quelle: GitHub-Issue 201. Ocarina of Time · Spielaufnahme aus der Community.
Latest recorded build build-117 Published November 7, 2026

Ein Spiel finden

Nach kompatiblen Lichii-Spielen suchen

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

Game Compatibility Results

Recorded performance

Performance by Build and Hardware

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.

The Legend of Zelda: Ocarina of Time Reported platform: unknown playable runs with issues unknown not booting 45 reports

Also listed as: Ocarina of Time, Zelda: Ocarina of Time, OoT, Zelda OoT, TLoZ: OoT

Lichii compatibility reports for The Legend of Zelda: Ocarina of Time
Build Status GPU / CPU FPS Details
Not provided playable Not provided / Not provided Not provided Open report
Not provided runs with issues 1080 Ti / Ryzen 5600X Not provided Open report
Not provided runs with issues GTX 1050 Ti / 7th gen i5 18–27 FPS Open report
Not provided playable RTX 3070 Ti / Ryzen 7 2700X Not provided Open report
build-95 (`nx2-build-95`) runs with issues RTX 4060 Laptop, 8 GB, 45 W max power limit / Intel Core i7-12650H (6P+4E, 16 threads) 9.4–51.4 FPS Open report
build 95 runs with issues Radeon 890M / Ryzen AI Z2 Extreme 23–25 FPS Open report
build 117 (PGO) runs with issues Radeon 890M / Ryzen AI Z2 Extreme 42–44 FPS Open report
nx2-build-95 runs with issues NVIDIA GeForce RTX 2070 / Intel Core i7-12700KF Not provided Open report
Not provided not booting NVIDIA GeForce RTX 3050 / Not provided Not provided Open report
build 88 and 93 runs with issues GTX 1060 6gb / Ryzen 5 5600 Not provided Open report

Not provided report

Statusplayable
GPUNot provided
CPUNot provided
DriverNot provided
Recorded FPSNot provided

Problems or notes: A commenter says everything works on their Mac with the latest main branch; hardware and build details are not stated.

Not provided report

Statusruns with issues
GPU1080 Ti
CPURyzen 5600X
DriverNot provided
Recorded FPSNot provided

Problems or notes: A commenter reports objects and doors failing to appear.

Not provided report

Statusruns with issues
GPUGTX 1050 Ti
CPU7th gen i5
DriverNot provided
Recorded FPS18–27 FPS

Problems or notes: A commenter reports invisible push blocks, making progress difficult.

Not provided report

Statusplayable
GPURTX 3070 Ti
CPURyzen 7 2700X
DriverNot provided
Recorded FPSNot provided

Problems or notes: A commenter reports testing the draft shader warm-up and says first-visit freezes were gone. The comment gives no broader gameplay or session-duration evidence.

build-95 (`nx2-build-95`) report

Statusruns with issues
GPURTX 4060 Laptop, 8 GB, 45 W max power limit
CPUIntel Core i7-12650H (6P+4E, 16 threads)
Driver610.78
Recorded FPS9.4–51.4 FPS

Problems or notes: User reports multi-second stalls while draws are held for unbuilt pipelines with async shaders enabled; in about 8 minutes, mean performance was 25.8 fps and six present windows had a maximum frame time over 1 s (worst 4.9 s). A fresh config used slow defaults and ran at 10–15 fps with stalls up to 8.9 s and blurry/pixelated Handheld resolution. Settings for the measured build-95 session were GPU accuracy Low, async shaders and async presentation enabled, Docked, 8 GB memory layout, and NVDEC GPU. The report also describes Frizti v3 behavior separately: it skipped draws with no pipeline, averaging 26.0 fps in 30-fps mode (range 16.4–30), with revisits at 30.0 fps and no frames over 100 ms.

build 95 report

Statusruns with issues
GPURadeon 890M
CPURyzen AI Z2 Extreme
Driver32.0.32015.5008
Recorded FPS23–25 FPS

Problems or notes: The intro, Deku Tree cutscene, and initial gameplay rendered correctly, but the game froze at 0 FPS when Navi passed the Kokiri guard on the path to the Deku Tree. The report mentions texture format asserts and Unmapped Device ReadBlock errors.

build 117 (PGO) report

Statusruns with issues
GPURadeon 890M
CPURyzen AI Z2 Extreme
Driver32.0.32015.5008
Recorded FPS42–44 FPS

Problems or notes: The intro and cutscenes ran at 42–44 FPS and the game reached Kokiri Forest, but Unmapped Device ReadBlock errors and multi-second stalls were followed by a hard freeze before Navi reached the guard. The same errors occurred with memory layout set to both 12 GB and 4 GB.

nx2-build-95 report

Statusruns with issues
GPUNVIDIA GeForce RTX 2070
CPUIntel Core i7-12700KF
Driver616.92
Recorded FPSNot provided

Problems or notes: User reports that after the Kaepora Gaebora cutscene near Hyrule Castle, the area appears empty and foggy, Link falls through the world, and repeated void-outs prevent progression. Reported on Windows 11 25H2 in Handheld mode with Vulkan. The user says the issue reproduces 100% with the same save; listed configuration changes and disabling a built-in patch did not fix it.

Not provided report

Statusnot booting
GPUNVIDIA GeForce RTX 3050
CPUNot provided
Driver621.14.0.0
Recorded FPSNot provided

Problems or notes: Crashes during boot about 9–13 seconds after launch, after presenting its first frame, at an unimplemented nx2:vi2 function 201. The same crash is reported on builds 93 and 95.

build 88 and 93 report

Statusruns with issues
GPUGTX 1060 6gb
CPURyzen 5 5600
DriverNot provided
Recorded FPSNot provided

Problems or notes: A commenter reports missing textures in the Deku Tree after loading a save, across two game versions and builds 88 and 93. They also report that it worked the first time.

Related game issues

Compared with Previous Build

Current: build-117 (2 records); previous: build-116 (0 records).

Showing 171–180 of 308 reports

Known issues from Lichii sources

Known Game Issues

The Legend of Zelda: Ocarina of Time

Gameplay performance is CPU-bound on the reported Ryzen 7 2700X; resolution scale changes and switching to Handheld did not improve performance.

The Legend of Zelda: Ocarina of Time (Switch 2)

On build 93 with RX 9070 XT, gameplay is slow-motion at reported frame rates, with heavy bloom and overexposure in bright areas and the Great Deku Tree rendered as a dark silhouette in its intro scene.

The Legend of Zelda: Ocarina of Time (Switch 2)

On RX 5700 (RDNA1), Kokiri Forest performance is reported at 14–15 FPS, compared with 22–24 FPS indoors; build 95 is reported to have the same outdoor performance as build 93.

The Legend of Zelda: Ocarina of Time (Switch 2)

On Lichii-AMD 2026.11.07 with RX 9070 XT using GPU Mode Fast, repeated rolling and jumping triggered black game frames while the HUD remained visible; the game continued running. Blackouts recurred in Kokiri Forest and were not accompanied by log output during the reported black periods.

Recorded fix: Switching GPU Mode from Fast to Accurate at runtime restored the picture without restarting; the commenter reports stutter afterward. Accurate mode was also reported to avoid blackouts but cause heavy stutter.

The Legend of Zelda: Ocarina of Time (Switch 2)

With an older configuration retaining GPU accuracy High, GPU thread splitting did not start, leaving work on one GPU thread. The commenter also reports long hitches while native pipelines were built, even with async shaders on.

The Legend of Zelda: Ocarina of Time (Switch 2)

On RX 9070 XT with extracted base-game version 1.0.0, the commenter reports blackouts and a Native compute shader rejected (per-tap gather) log error. They report no blackouts or such error during about 70 minutes of play using version 2.0.0 from a .nup on build 117 PGO.

Other / not listed

User reports a solar flare in the field when looking toward Kakariko and no collision.

Other / not listed

Music randomly cuts out while voices continue playing in the first cinematic.

Other / not listed

A user reports that room textures disappear inside the Water Temple. A commenter says a damaged game-data texture file may prevent its model from being built.

Recorded fix: A commenter describes a workaround in PR #267 that serves the damaged file from a sibling file, but does not confirm that it fixes the Water Temple issue.

Other / not listed

A flash phenomenon occurs when entering Kakariko Village; a comment reports the same issue in Goron City.

Showing 61–70 of 361 issues

Aktuelle Release-Hinweise

Kompatibilitätsänderungen in den neuesten Builds

Den passenden Build finden

Welchen Build soll ich verwenden?

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

Häufige Fragen zur Spielekompatibilität

Wie teile ich ein Spiel mit diesen Filtern?

Setze die Filter für Spiel, Status, GPU und Build und kopiere anschließend die Seitenadresse. Ein direkter Link zum Spiel öffnet dessen Berichtskarte.

Was kann ich bei einem schwarzen Bildschirm versuchen?

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.

Warum kann dieselbe GPU unterschiedliche Ergebnisse liefern?

Treiberversion, Grafikeinstellungen, CPU-Auslastung und die getestete Spielszene können das Ergebnis beeinflussen. Vergleiche diese Details, bevor du deine Konfiguration änderst.

Wo kann ich ein fehlendes Testergebnis melden?

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.