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.

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: Windows 11 playable runs with issues boots not booting 9 reports

Also listed as: OOT Remake, OoT

Lichii compatibility reports for Ocarina of Time
Build Status GPU / CPU FPS Details
3724db9a5c playable RTX 4070 / i9-12900F 16 FPS Open report
b8c812b18 runs with issues RX 5700 / Not provided Not provided Open report
build 95 playable RX 7900 XTX / Ryzen 7 9800X3D 60 FPS Open report
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

3724db9a5c report

Statusplayable
GPURTX 4070
CPUi9-12900F
DriverNot provided
Recorded FPS16 FPS

Problems or notes: The tester reported visible grass and a clear view of the tree through grey fog in front of the Deku Tree. The in-game counter showed 16 FPS in that view; this was a single reading.

b8c812b18 report

Statusruns with issues
GPURX 5700
CPUNot provided
Driveramdvlk 32.0.21045.16010
Recorded FPSNot provided

Problems or notes: A user reported a local ClangCL build stalled with no frames (maximum 8 presents); a local MSVC build also stalled and died within a minute. In comparison, the user's build-75 release run presented frames at 32 FPS. The maintainer said the report was from an old commit and may no longer apply.

build 95 report

Statusplayable
GPURX 7900 XTX
CPURyzen 7 9800X3D
DriverAMD driver 2.0.416 / 32.0.32015.7029
Recorded FPS60 FPS

Problems or notes: Not provided

nx2 @ 27226d2 plus two measurement-only commits report

Statusruns with issues
GPURTX 5060 Laptop (8 GB)
CPURyzen AI 9 365
Driver621.01
Recorded FPSNot provided

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.

Lichii nx2 build 88 report

Statusboots
GPUIntel Arc
CPUNot provided
DriverNot provided
Recorded FPS1 FPS

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.

nx2 build 88 report

Statusnot booting
GPUNVIDIA RTX 3060
CPURyzen 7 5700X
Driver617.14
Recorded FPSNot provided

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.

Related game issues

Compared with Previous Build

Showing 1–10 of 142 reports

Known issues from Lichii sources

Known Game Issues

The Legend of Zelda: Ocarina of Time

The emulator closes when loading Hyrule Market after the user exits Kokiri Forest and enters Hyrule Castle.

Zelda: Ocarina of Time

The console restarts after the scene on Linux with a lenovo legion go 2 z2 and egpu 7600xt; the report names versions 83 et 93.

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

Two hidden/minimized Windows CLI launches crashed in nvoglv64.dll with exception 0xc0000094 at offset 0xEFC9BB. Static findings identify stale SDL visibility state and no zero-extent guard as possible leads, but neither is proven to cause the crash.

Ocarina of Time

Audio and video become desynchronized on the title screen, intro, and initial dream cutscene; a commenter reports slow-motion live-rendered video and an audio lead of approximately 3 seconds.

Donkey Kong Bananza

On build 93, FPS fluctuates approximately between 20 and 60, with frequent periods around 30 and drops to 25–28 FPS in the Dragon Layer; GameSir G7 Pro rumble can be excessive, occur without an obvious trigger, or continue longer than expected.

The Legend of Zelda: Ocarina of Time

On an AMD Radeon RX 6700 XT with AMD Software (Adrenalin) 26.10.2, Lichii closes during the first shader rebuild after about 9-10 minutes; Event Viewer reports an access violation in amdvlk64.dll.

Zelda: OoT Remake

Constant 4 FPS in-game on AMD Radeon RX 570 4GB.

Donkey Kong Bananza

User reports a crash when loading a save on AMD RX 6000 series or older under Windows 11.

Splatoon Raiders

Rhythmic wavy effect on edges in the main area, described as depth of field toggling on and off.

The Legend of Zelda: Ocarina of Time Remake

Crashes at the same moment as it flies under the user's feet; the log reports an application error in amdvlk64.dll.

Showing 211–220 of 287 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.