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.

Ocarina of Time Reported platform: Nintendo Switch runs with issues playable 4 reports

Also listed as: OoT

Lichii compatibility reports for Ocarina of Time
Build Status GPU / CPU FPS Details
nx2 5a50f50e0b; official PGO artifact of build-80 and local non-PGO nx2-latest runs with issues AMD RX 9070 XT (RDNA4, 16 GB) / Ryzen 7 5800X3D (8C/16T) 28–35 FPS Open report
local non-PGO nx2 @ 4c173bb792 with PR #345 merged (4647895acc) playable Radeon RX 9070 XT (RADV GFX1201) / Ryzen 7 5800X3D (8C/16T) Not provided Open report
Lichii nx2 build 93, Windows release runs with issues RX 9070 XT 16 GB / Ryzen 7 7800X3D (8C/16T) 18 FPS Open report
Lichii nx2-build-83 non-PGO AppImage runs with issues RX 9070 XT 16 GB (RADV GFX1201) / Ryzen 7 5700X (AM4, 8C/16T, non-X3D) 20–35 FPS Open report

nx2 5a50f50e0b; official PGO artifact of build-80 and local non-PGO nx2-latest report

Statusruns with issues
GPUAMD RX 9070 XT (RDNA4, 16 GB)
CPURyzen 7 5800X3D (8C/16T)
DriverMesa 26.x RADV
Recorded FPS28–35 FPS

Problems or notes: On Bazzite (Fedora Atomic 45), gameplay was reported at 28-35 fps with 31-36 ms frame times despite no saturated thread. The PGO artifact crashed in dynarmic with Unhandled SIGSEGV after 2-10 minutes; the local non-PGO build was stable over several sessions.

local non-PGO nx2 @ 4c173bb792 with PR #345 merged (4647895acc) report

Statusplayable
GPURadeon RX 9070 XT (RADV GFX1201)
CPURyzen 7 5800X3D (8C/16T)
DriverMesa 26.2.6
Recorded FPSNot provided

Problems or notes: In a Deku Tree interior test, the reporter measured 16.8-18.6 ms frame times and reported the area was at the present cap. White flashes were confirmed gone there. Kokiri Village and Hyrule Field remained untested, and runtime pipeline builds caused isolated frame spikes.

Lichii nx2 build 93, Windows release report

Statusruns with issues
GPURX 9070 XT 16 GB
CPURyzen 7 7800X3D (8C/16T)
DriverAMD proprietary driver, Vulkan 2.0.416, Adrenalin 32.0.32015.12012
Recorded FPS18 FPS

Problems or notes: On Windows 11 Enterprise LTSC 2024, gameplay was reported at about 18 fps (about 56 ms per frame) with no saturated thread. New-content pipeline compilation caused first-visit hitches. A later follow-up on Frizti v3 reported about 20 fps in a busy view and about 60 fps looking at the floor; the reporter attributed the heavy-view limit to host GPU load, but that follow-up did not identify the build as build 93.

Lichii nx2-build-83 non-PGO AppImage report

Statusruns with issues
GPURX 9070 XT 16 GB (RADV GFX1201)
CPURyzen 7 5700X (AM4, 8C/16T, non-X3D)
DriverMesa/RADV 26.2.5-1
Recorded FPS20–35 FPS

Problems or notes: On CachyOS, gameplay commonly ran at 20-35 FPS and in slow motion; menus were about 60 FPS and intro video/audio stuttered. The non-PGO AppImage rendered and reached gameplay. The PGO AppImage produced audio but no video output, and clearing the shader cache did not resolve it. The stated FPS range is the reporter's gameplay observation, not the table's median window FPS.

Related game issues

Compared with Previous Build

Ocarina of Time Reported platform: Linux (Fedora 44 / Aurora) runs with issues 1 report
Lichii compatibility reports for Ocarina of Time
Build Status GPU / CPU FPS Details
nx2-build-88 runs with issues Intel Arc B580 (BMG G21) / Ryzen 5 5600X 8 FPS Open report

nx2-build-88 report

Statusruns with issues
GPUIntel Arc B580 (BMG G21)
CPURyzen 5 5600X
DriverMesa 26.2.6 (ANV)
Recorded FPS8 FPS

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.

Related game issues

Compared with Previous Build

Ocarina of Time Reported platform: Windows 10 runs with issues 2 reports

Also listed as: OoT

Lichii compatibility reports for Ocarina of Time
Build Status GPU / CPU FPS Details
b4716fc runs with issues RX 6700 XT / Not provided Not provided Open report
nx2 c9bdbaa runs with issues RX 6600 XT / Not provided 24–48 FPS Open report

b4716fc report

Statusruns with issues
GPURX 6700 XT
CPUNot provided
DriverNot provided
Recorded FPSNot provided

Problems or notes: The title screen, intro, and cinematics before the Deku Tree exterior cutscene render correctly. That cutscene is black except for a small circle around Navi where the world renders.

nx2 c9bdbaa report

Statusruns with issues
GPURX 6600 XT
CPUNot provided
DriverAMD proprietary driver 2.0.353
Recorded FPS24–48 FPS

Problems or notes: A commenter reports 24–25 FPS at the Deku Tree web after watching the New Game intro, versus 44–46 FPS when loading the same save without the intro. With the reported storage-write extent branch, the intro-first sequence gave 44–47 FPS, gameplay about 35–48 FPS, and auto-exposure stayed correct. These are user-reported test results.

Related game issues

Compared with Previous Build

Ocarina of Time Reported platform: Linux unknown not booting runs with issues 3 reports
Lichii compatibility reports for Ocarina of Time
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

build-117 report

Statusunknown
GPUNot provided
CPUNot provided
DriverNot provided
Recorded FPSNot provided

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.

Lichii Build 95 report

Statusnot booting
GPURTX 3050 6GB
CPUi7-13620H
DriverNot provided
Recorded FPS0 FPS

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.

Not provided report

Statusruns with issues
GPUAMD RX 6000 series or older
CPUNot provided
DriverNot provided
Recorded FPSNot provided

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.

Related game issues

Compared with Previous Build

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

Showing 71–80 of 308 reports

Known issues from Lichii sources

Known Game Issues

Other / not listed

Fairy-light flickering and flashing white sky, reported in Sacred Grove and other locations; may occur randomly without clear reproduction steps.

The Legend of Zelda: Ocarina of Time

On AMD RDNA2 GPUs, the 16x16x16 VK_KHR_cooperative_matrix HMMA pipeline path can cause an access violation in amdvlk64.dll during shader or pipeline compilation, typically 30–90 seconds after game startup.

Recorded fix: The source reports that EDEN_NX2_NO_COOP_MATRIX=1 avoids the crash. A later comment states that merged PR #657 fixes it.

Other / not listed

The underground fairy fountain has no environment.

Recorded fix: A commenter says the issue is caused by a dump missing textures and advises using a NUP dumped without missing textures.

Zelda: Ocarina of Time

On Linux, a black screen can occur with the Native MME error "instruction outside uploaded RAM". One report says shaders load and menu music is audible; another says the game opens, reaches 0 FPS, and freezes.

Recorded fix: A comment reports that setting DMA accuracy to Safe works as a workaround. Another comment attributes the error to a GCC 13 miscompile and says a fix was merged but was not yet in a published release.

OoT

Cutscenes play in slow motion, lagging behind audio; the report describes them as locked to 49fps with 99% GPU usage.

OoT

The same slow-motion cutscene problem is reported.

OoT

The same slow-motion cutscene problem is reported.

The Legend of Zelda: Ocarina of Time

After the Kaepora Gaebora cutscene near Hyrule Castle, the scene appears empty and foggy and Link repeatedly falls through the world and voids out, preventing progression.

Mario Kart World

User reports 17–23.8 FPS in 3D races on build-95, compared with 40.0–54.1 FPS on build-93 under the same reported test conditions.

Other / not listed

Black screen when starting in build 95 on Linux; a commenter reports black screen with music. The commenter says build 93 loads normally on their system.

Showing 111–120 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.