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.

Donkey Kong Bananza Reported platform: Windows 11 runs with issues unknown not booting 3 reports
Lichii compatibility reports for Donkey Kong Bananza
Build Status GPU / CPU FPS Details
build-117 runs with issues AMD RX 6000 series or older / Not provided Not provided Open report
build-88 unknown RTX 4070 / i7 13700k 20 FPS Open report
latest prelease build 93 not booting AMD RX 6000 series or older / Not provided Not provided Open report

build-117 report

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

Problems or notes: Crashes after the continue-game loading screen.

build-88 report

Statusunknown
GPURTX 4070
CPUi7 13700k
DriverNot provided
Recorded FPS20 FPS

Problems or notes: User report: locked at 20 FPS, including menus and title screen. The user says they do not know whether this is a regression.

latest prelease build 93 report

Statusnot booting
GPUAMD RX 6000 series or older
CPUNot provided
DriverNot provided
Recorded FPSNot provided

Problems or notes: User reports a crash when loading a save.

Related game issues

Compared with Previous Build

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

Donkey Kong Bananza Reported platform: Windows runs with issues playable 6 reports

Also listed as: dkb

Lichii compatibility reports for Donkey Kong Bananza
Build Status GPU / CPU FPS Details
build-93 runs with issues NVIDIA RTX 50 series / Not provided 20–60 FPS Open report
build-75 runs with issues NVIDIA GeForce RTX 4060 Laptop, 8 GB / Intel Core i7-13650HX 20 FPS Open report
build-70 runs with issues NVIDIA GeForce RTX 4060 Laptop, 8 GB / Intel Core i7-13650HX 20 FPS Open report
build-65 playable NVIDIA GeForce RTX 4060 Laptop, 8 GB / Intel Core i7-13650HX 10–30 FPS Open report
Eglantine NX2 Windows build 2026-10-31 (1.0.0-stable-1.0.0) runs with issues AMD Radeon RX 7600 8 GB / AMD Ryzen 7 7800X3D Not provided Open report
build 70 (286117c) runs with issues AMD RX 6000 series or older / Not provided 57 FPS Open report

build-93 report

Statusruns with issues
GPUNVIDIA RTX 50 series
CPUNot provided
DriverNot provided
Recorded FPS20–60 FPS

Problems or notes: User reports FPS fluctuating approximately between 20 and 60, frequent periods around 30, and 25–28 FPS in the Dragon Layer. With a GameSir G7 Pro, controller rumble is sometimes excessive, occurs without an obvious in-game trigger, and sometimes continues longer than expected.

build-75 report

Statusruns with issues
GPUNVIDIA GeForce RTX 4060 Laptop, 8 GB
CPUIntel Core i7-13650HX
Driver32.0.16.2101
Recorded FPS20 FPS

Problems or notes: Terrain/world renders solid white while the HUD and characters still draw. With EDEN_NX2_RESETFIX=0, the ground renders black without texture or lighting.

build-70 report

Statusruns with issues
GPUNVIDIA GeForce RTX 4060 Laptop, 8 GB
CPUIntel Core i7-13650HX
Driver32.0.16.2101
Recorded FPS20 FPS

Problems or notes: Terrain/world renders solid white while the HUD and characters still draw.

build-65 report

Statusplayable
GPUNVIDIA GeForce RTX 4060 Laptop, 8 GB
CPUIntel Core i7-13650HX
Driver32.0.16.2101
Recorded FPS10–30 FPS

Problems or notes: Not provided

Eglantine NX2 Windows build 2026-10-31 (1.0.0-stable-1.0.0) report

Statusruns with issues
GPUAMD Radeon RX 7600 8 GB
CPUAMD Ryzen 7 7800X3D
DriverAMD proprietary Vulkan driver 2.0.395
Recorded FPSNot provided

Problems or notes: After gameplay starts, a 960x540 VP9 video panel appears as a solid yellow box in stable-1.0.0. When the video reaches end of stream, the game aborts with 2111-3604 and emulation freezes. The report says this reproduces in Eglantine NX2 Windows build 2026-10-31 (1.0.0-stable-1.0.0) and PokeDinner fork 2.1.0 (007f3ac08d). Without EDEN_NX2_TENSOR=1, two compute shaders are rejected and the 3D scene remains flat lavender with only the HUD visible. A later user comment reports that the game played past the tutorial video without the abort.

build 70 (286117c) report

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

Problems or notes: On Windows 11 with Vulkan, the game reportedly held about 57 FPS during gameplay, then the process aborted after 133.8 seconds with 0xC0000409 at lichii.exe+0x2ecd3bd. With the MinGW PGO zip of the same build, it reportedly died on the intro screen seconds after launch.

Related game issues

Compared with Previous Build

Current: build-93 (1 record); previous: build-88 (0 records).

Donkey Kong Bananza Reported platform: unknown runs with issues unknown not booting playable 8 reports

Also listed as: dkb

Lichii compatibility reports for Donkey Kong Bananza
Build Status GPU / CPU FPS Details
build-70 runs with issues NVIDIA RTX 40 series / Not provided Not provided Open report

build-70 report

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

Problems or notes: User reports visual artifacts, especially on shadows.

Related game issues

Compared with Previous Build

Current: build-70 (2 records); previous: build-65 (0 records).

Showing 1–10 of 18 reports

Known issues from Lichii sources

Known Game Issues

Ocarina of Time

On AMD Radeon RX 9070 XT with driver 2.0.416, a dotted cyan/magenta line appeared along mountain and sky silhouettes in Hyrule Field.

Recorded fix: Zero the color write mask of render targets the fragment shader does not store; the issue comment says this fix landed in build 95.

The Legend of Zelda: Ocarina of Time

Coloured blocks or a magenta line along the Hyrule Field mountain ridge on AMD GPUs; the original report described NaNs in the scene target that bloom spread into a coloured band.

Recorded fix: The #353 per-component write-mask fix was reported to remove the coloured blocks or line. A temporary workaround is to set EDEN_NX2_REJECT_HASH=fe1f903f1bf52a9d,4f5673eca06ebecb, which drops the draw and loses its far-distance effect.

The Legend of Zelda: Ocarina of Time

Distant mountains remain overexposed with a white glow after the coloured blocks are removed; the source identifies this as a separate bloom/exposure issue.

Ocarina of Time

On Linux with AMD RX 9000-series graphics using RADV, an invalid SPIR-V fragment shader can cause a segfault during Vulkan graphics-pipeline construction during gameplay.

Recorded fix: Fixed in build 93 and later releases.

The Legend of Zelda: Ocarina of Time

On AMD's proprietary Windows Vulkan driver, the intro could freeze while two compute shaders were optimized, taking 6–18 minutes; long graphics-pipeline builds can also cause substantial in-game stalls.

Recorded fix: Build 93 and later build the two identified compute shaders without driver optimization on AMD's proprietary Vulkan driver. The source says long graphics-pipeline builds are a separate matter and are not covered.

Ocarina of Time

On earlier builds, small details such as leaves, pebbles, and grass flickered or appeared black with Low GPU accuracy and the split GPU thread enabled.

Recorded fix: Update to build 95 or later; the source attributes the fix to buffer usage tracking changes, with additional near-foliage fixes. EDEN_NX2_PERF_VERIFY=1 was an earlier workaround but was reported as no longer needed on build 95.

Other / not listed

A user reports that games do not work on a Lenovo Legion Go 2 Z2 with an eGPU 7600xt on Version 95; on Version 93 or earlier, they can see the scene.

Fire Emblem

On Linux with AMD graphics, Fire Emblem: Fortune's Weave can crash after a black screen with VK_ERROR_DEVICE_LOST and a GPU reset.

The Legend of Zelda: Ocarina of Time

On Windows 11, extracting a NUP to a path longer than 260 characters fails even when LongPathsEnabled is set. The issue reports a malformed longPathAware manifest entry as the probable cause.

Ocarina of time SW2

AV1 cinematics are delayed, with audio playing faster.

Showing 161–170 of 361 issues

Aktuelle Release-Hinweise

Kompatibilitätsänderungen in den neuesten Builds

Den passenden Build finden

Welchen Build soll ich verwenden?

build-70 · Veröffentlicht am November 4, 2026

Donkey Kong Bananza

  • runs with issues · GPU NVIDIA RTX 40 series · CPU Nicht angegeben · Treiber Nicht angegeben
  • playable · GPU Nicht angegeben · 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.