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
nx2 a7a28175 + #292, local MSVC build runs with issues AMD RX 7000 series / Not provided Not provided Open report
Not provided playable RX 7800 XT / Not provided Not provided Open report
nx2 @ 09b78bd2df runs with issues NVIDIA GeForce GTX 1070 (Pascal) / Not provided Not provided Open report
nx2-build-93 runs with issues NVIDIA GeForce RTX 5090 / AMD Ryzen 7 7800X3D Not provided Open report
Not provided runs with issues RTX 5070 / Intel Core i5-14400F Not provided Open report
Lichii nx2 build 93 (09b78bd) runs with issues NVIDIA RTX 50 series / Not provided Not provided Open report
Not provided runs with issues Radeon 860M / Ryzen AI 7 350 22 FPS Open report
bf4c42e223 runs with issues RX 9070 XT / Ryzen 9 9950X 26–57 FPS Open report
Lichii nx2 build 95 (222877d) runs with issues AMD Radeon RX 9070 XT / Not provided Not provided Open report
Build 88, 93, and 95 not booting Radeon RX 5700 XT / AMD Ryzen 5 3600 Not provided Open report

nx2 a7a28175 + #292, local MSVC build report

Statusruns with issues
GPUAMD RX 7000 series
CPUNot provided
DriverNot provided
Recorded FPSNot provided

Problems or notes: After outdoor play, the sky turns flat yellow-white and the river shimmers green until reboot. The report attributes the full-screen spread to NaNs handled differently by AMD and NVIDIA.

Not provided report

Statusplayable
GPURX 7800 XT
CPUNot provided
DriverNot provided
Recorded FPSNot provided

Problems or notes: Not provided

nx2 @ 09b78bd2df report

Statusruns with issues
GPUNVIDIA GeForce GTX 1070 (Pascal)
CPUNot provided
Driver580.178.4
Recorded FPSNot provided

Problems or notes: User reports missing scene elements, including a door and most vegetation, during gameplay. The report attributes dropped mesh-shader draws to the GPU lacking VK_EXT_mesh_shader, but says the missing elements were not confirmed to be those draws.

nx2-build-93 report

Statusruns with issues
GPUNVIDIA GeForce RTX 5090
CPUAMD Ryzen 7 7800X3D
Driver581.29
Recorded FPSNot provided

Problems or notes: Boots and plays the intro cinematic, then crashes during shader and pipeline compilation with Vulkan device loss. The report says the same behavior also occurred on nx2-build-95. Another user reports that updating to NVIDIA Game Ready 621.14 and rebooting resolved the issue on their system, reaching gameplay with working controller input.

Not provided report

Statusruns with issues
GPURTX 5070
CPUIntel Core i5-14400F
Driver581.29 (Vulkan 1.4.312)
Recorded FPSNot provided

Problems or notes: A user reports gameplay consistently failed after the opening cinematic or when loading a save, with 16 Unmapped Device ReadBlock errors followed by device loss and Windows nvlddmkm Event ID 153. Updating to NVIDIA Game Ready 621.14 and rebooting resolved the issue on this system; gameplay and controller input worked.

Lichii nx2 build 93 (09b78bd) report

Statusruns with issues
GPUNVIDIA RTX 50 series
CPUNot provided
DriverNot provided
Recorded FPSNot provided

Problems or notes: The user reports that the emulator crashes to desktop within a few seconds of entering the Guardhouse in Hyrule Castle Town. Reported environment: Windows 11, Vulkan, Docked, Fast GPU mode, FSR 1, FXAA.

Not provided report

Statusruns with issues
GPURadeon 860M
CPURyzen AI 7 350
DriverRADV
Recorded FPS22 FPS

Problems or notes: About 22 FPS in Kokiri Forest. Reported stalls while the front GPU thread waits for the back thread.

bf4c42e223 report

Statusruns with issues
GPURX 9070 XT
CPURyzen 9 9950X
DriverMesa 26.2.6 RADV
Recorded FPS26–57 FPS

Problems or notes: 48–57 FPS in light areas and about 26–33 FPS in busy areas, with thread hand-offs contributing to frame time.

Lichii nx2 build 95 (222877d) report

Statusruns with issues
GPUAMD Radeon RX 9070 XT
CPUNot provided
DriverNot provided
Recorded FPSNot provided

Problems or notes: User reports a white daytime sky and washed-out distant scenery in Hyrule Field, and black distant terrain and water at night. GPU accuracy Fast and Accurate do not resolve the reported issue. A comment reports crashing during loading on an RX 9070 XT, but does not establish that this game report shares the same setup.

Build 88, 93, and 95 report

Statusnot booting
GPURadeon RX 5700 XT
CPUAMD Ryzen 5 3600
DriverNot provided
Recorded FPSNot provided

Problems or notes: The reporter says builds 88–95 fail after the game previously worked in build 93; the emulator hangs on “Loading...” and exits about 10 seconds later. A build-95 log from another report records an unhandled SIGSEGV and a null-pointer dereference. User comments report other differing failures, including black screens and 0 FPS.

Related game issues

Compared with Previous Build

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

Showing 41–50 of 142 reports

Known issues from Lichii sources

Known Game Issues

The Legend of Zelda: Ocarina of Time

Day-only garbage graphics in the Bombchu Bowling Alley: stones and ovens flash pink, yellow, red, or black, and the sign displays garbage, noise, and fragments of another image. It looks correct at night after leaving and returning, and was still present in build-117.

The Legend of Zelda: Ocarina of Time

After outdoor play, the sky becomes flat yellow-white and water shimmers green until reboot, due to NaNs spreading through bloom. The report says the NaNs probably originate from fog/foliage probe reads beyond the 64 MiB graphics table-pointer cap.

Recorded fix: Use NaN-safe min/max/clamp handling and fix table-pointer reads beyond the old 64 MiB cap; the reporter confirmed normal visuals after both fixes.

The Legend of Zelda: Ocarina of Time

Foliage and vegetation near the player may turn into dead-looking variants or lose leaves up close, including hedges and plants in Hyrule Castle; reports also mention trees, Kokiri Forest bushes, Castle Town hedges, and Hyrule Field grass. One user describes the behavior as an inverted LOD.

Ocarina of Time

On macOS/MoltenVK with an Apple M1, the Switch 2 NSO version boots and plays audio but presents a black image from startup, with approximately 1 FPS and occasional red/green block artifacts.

The Legend of Zelda: Ocarina of Time

On AMD GPUs, Ocarina of Time's compute shaders can fail compilation with VK_ERROR_OUT_OF_HOST_MEMORY or cause the AMD driver to crash. The issue report describes missing intro video and an eventual process crash; a later user reports an access violation inside amdvlk64.dll.

The Legend of Zelda: Ocarina of Time

OpenGL is reported not to work for this game because GLSL task and mesh programs are not implemented, resulting in repeated errors and an emulator hang.

The Legend of Zelda: Ocarina of Time

Rejecting shader hashes before translation skips their dispatches and can result in missing output or a black screen; a user reports the environment switch did not affect the tested Vulkan compute-pipeline path.

Recorded fix: For testing shader rejection, keep the disk shader cache off or delete it before each run; the maintainer says cached shaders are loaded without checking the rejection list.

The Legend of Zelda: Ocarina of Time

Performance slows in crowded or busy areas, with front/back GPU-thread synchronization drains and waits; short freezes while attacking are also reported.

The Legend of Zelda: Ocarina of Time

Shader compilation can cause freezes of about 3 seconds with each step, according to a user report.

The Legend of Zelda: Ocarina of Time

On integrated AMD graphics, device-memory thresholds can keep the texture cache collector in aggressive mode even though deleting all images cannot reduce total usage below the threshold. This causes extensive image churn and GPU waits during gameplay.

Showing 31–40 of 361 issues

Aktuelle Release-Hinweise

Kompatibilitätsänderungen in den neuesten Builds

Den passenden Build finden

Welchen Build soll ich verwenden?

build-75 · Veröffentlicht am November 5, 2026

OOT

  • runs with issues · GPU NVIDIA RTX 50 series · CPU Nicht angegeben · Treiber Nicht angegeben

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.