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

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

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 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 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

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.

Not provided report

Statusunknown
GPURTX 5060
CPUNot provided
DriverNot provided
Recorded FPSNot provided

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.

Not provided report

Statusplayable
GPURTX 4090
CPURyzen 9 7950x3D
DriverNot provided
Recorded FPSNot provided

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.

Not provided report

Statusruns with issues
GPUIntegrated graphics AMD (Radeon 860M, Ryzen AI 7 350, RADV / Mesa)
CPURyzen AI 7 350
DriverRADV / Mesa
Recorded FPS22–23 FPS

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.

Related game issues

Compared with Previous Build

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

Showing 71–80 of 194 reports

Known issues from Lichii sources

Known Game Issues

Zelda: Ocarina of Time

On build 95, Linux and SteamOS users report black-screen hangs with audio still playing; comments associate the issue with repeated `Native MME (split front) failed` errors.

Zelda: Ocarina of Time

A commenter reports reaching the main menu by starting with GPU accuracy set to Accurate, but reports audio issues and possible recurrence after changing settings.

The Legend of Zelda: Ocarina of Time

On Windows 11 with an AMD RX 9000 series GPU and proprietary driver 2.0.416, gameplay is around 20 FPS with large variance, light/haze artifacts, and desynchronized, stuttering audio.

The Legend of Zelda: Ocarina of Time

On Linux with an AMD Radeon RX 6700 XT, gameplay is around 20 FPS with audio crackling below full speed. On Windows with the same PC, only subtitles rendered.

The Legend of Zelda: Ocarina of Time

With Mesa 25.0.7 and kernel 6.12.115, gameplay was followed after about nine minutes by a Vulkan device loss and an unrecovered display; this was not seen again after updating Mesa and the kernel.

Recorded fix: Update to Mesa 26.1.6 and kernel 7.2.11; the reporter did not see the device loss again afterward.

Mario Kart World

On Windows 11, connecting an official Nintendo Switch Pro Controller while Lichii is open reportedly floods the host OS with phantom inputs, making desktop mouse clicks unresponsive and keyboard typing erratic. Unplugging the controller reportedly restores normal input.

Nintendo Switch Sports Resort

With Dual Joy-Cons, the game remains on the “Playing with 1 Joy-Con” screen and reports a lost connection, preventing a two-player motion game from starting. The issue reporter's log includes an unsupported controller type disconnection and a Joy-Con sub-command timeout.

Ocarina of Time

The official PGO artifact of build-80 / nx2-latest crashed in dynarmic with Unhandled SIGSEGV after 2-10 minutes on the reporting machine; another report found a PGO AppImage produced audio but no video output.

Ocarina of Time

White flashes were reported before PR #345 in the Deku Tree interior; the sky/lighting colour result from a separate misaligned 64/128-bit SSBO split fix was not verified.

Recorded fix: Use a local non-PGO build with PR #345 merged; the reporter confirmed white flashes were gone after several minutes in the Deku Tree interior.

Ocarina of Time

In a Windows AMD-driver follow-up on Frizti v3, performance was about 20 fps in a busy view and about 60 fps looking at the floor; the reporter said keeping float16 on improved the busy-view result from about 20 to 24-25 fps.

Recorded fix: The reporter found that keeping float16 on improved the measured busy-view performance; this is a user-reported workaround.

Showing 141–150 of 287 issues

Aktuelle Release-Hinweise

Kompatibilitätsänderungen in den neuesten Builds

Den passenden Build finden

Welchen Build soll ich verwenden?

build-117 · Veröffentlicht am November 7, 2026

Ocarina of Time

  • runs with issues · GPU Other · CPU Apple M1 · Treiber Vulkan through MoltenVK

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

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.