Spielekompatibilität
Du hast ein bestimmtes Spiel im Sinn? Erfahre, wie es mit Lichii läuft, welche Probleme bekannt sind und welchen Build du ausprobieren kannst.
Ein Spiel finden
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
Recorded performance
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.
No games match these filters. Try a different name, GPU, or build, or clear a filter to broaden the search.
| Build | Status | GPU / CPU | FPS | Details |
|---|---|---|---|---|
| build-88 | runs with issues | AMD RX 9000 series / Not provided | Not provided | Open report |
Problems or notes: The game shows video and music during the intro, then crashes after Ganondorf makes Link wake up. A commenter reports delayed video followed by an emulator crash with an AMD RX 9060 XT 16gb graphics card. Another report says a suggested procedure did not work on Win11 with an RX 9070 XT 16 GB and Ryzen 7 7700, and that a driver crash remained.
Current: build-88 (1 record); previous: build-83 (0 records).
| Build | Status | GPU / CPU | FPS | Details |
|---|---|---|---|---|
| chuppatricky-amd-testbuild-v13-windows-x86_64.zip | runs with issues | AMD RX 6000 series or older / Not provided | Not provided | Open report |
Problems or notes: Crashes at the same moment as it flies under the user's feet.
| Build | Status | GPU / CPU | FPS | Details |
|---|---|---|---|---|
| Lichii nx2-build-75 | not booting | Radeon RX 580 (Polaris / GCN4), 8 GB / Intel Xeon E5-2667 v4 (8C/16T, AVX2) | 0 FPS | Open report |
Problems or notes: The game boots and the intro AV1 video begins decoding, but the screen remains black and FPS stays at 0 while compute pipelines are built. The report says this persists for over five minutes. Multiple settings and cache-clearing attempts made no difference.
Also listed as: OoT, Ocarina of Time
| Build | Status | GPU / CPU | FPS | Details |
|---|---|---|---|---|
| build-117 | playable | Radeon RX 9070 XT / AMD Ryzen 7 5700X | 19–65 FPS | Open report |
| nx2-build-92 | runs with issues | RX 7800 XT (RADV) / Ryzen 7 7700X | 35–59 FPS | Open report |
| 95 Non-PGO | not booting | AMD Radeon RX 9070 XT / AMD Ryzen 7 5700X (AM4) | Not provided | Open report |
| 83 Non-PGO | boots | AMD Radeon RX 9070 XT / AMD Ryzen 7 5700X (AM4) | Not provided | Open report |
Problems or notes: The user reports rendering works again. In Wayland, around 19–25 FPS, fluctuating. In XWayland with QT_QPA_PLATFORM=xcb, Kokiri Village measured 25–54 FPS, usually around 30 FPS; inside the Deku Tree usually 30–45 FPS while idle, occasional peaks to 65 FPS, and recurring drops to 19 FPS. The user reports normal game speed despite frame drops and says the game is playable; FPS/frametime variability remains substantial.
Problems or notes: Ubuntu 26.04, Docked, GPU accuracy Low. Without EDEN_NX2_NO_MESH=1, device loss occurs while loading a save. With the variable, a single 337-second session ran until the user closed it; approximately 59 FPS with dips to 35–50 and some stutter, 47 draws skipped, and a door was transparent at the start. This was not tested in a new game.
Problems or notes: The game displays a completely black screen while intro audio continues, after shader compilation. The report says this also occurs in native Wayland, XWayland with QT_QPA_PLATFORM=xcb, with EDEN_NX2_NO_MESH=1 alone, and with both environment variables together. Removing Vulkan Pipeline Cache and Cache Storage and recompiling shaders did not resolve it.
Problems or notes: The game renders on the same machine under Wayland without special environment variables, but performance is reported as lower.
Current: build-117 (1 record); previous: build-116 (0 records).
Also listed as: Ocarina of Time
| Build | Status | GPU / CPU | FPS | Details |
|---|---|---|---|---|
| Not provided | not booting | RX 9070 XT 16 GB / Ryzen 7 9850X3D | Not provided | Open report |
Problems or notes: A commenter reports an instant crash despite trying the EDEN_NX2_NO_MESH=1 workaround. Firmware 20.3.0, game version 1.1.1, and game build ID E0F3CCFAF50065AE4EA01EB5AEB13B1A45DA3348 are stated.
| Build | Status | GPU / CPU | FPS | Details |
|---|---|---|---|---|
| nx2 at 8813b44 and 5a50f50; other user tests cite 75 (c9ebb5c), 27226d2, 55532f2, and b06d181 | runs with issues | Not provided / Apple M6 (arm64) | 12–14 FPS | Open report |
| Eglantine fork 0ca2032 and Lichii nx2 build 75 (c9ebb5c) | runs with issues | Not provided / Apple M1 | Not provided | Open report |
Problems or notes: Title screen and intro video render, but the GPU may lose the Metal device during video playback or the GPU thread may hang at the video-to-gameplay transition. The initial report states gameplay is not reached; a later user update says the intro plays end to end after applying proposed changes but transition stalls remain. A separate report gives 25-30 FPS after applying proposed fixes. Reports are user observations.
Problems or notes: User reports Metal device loss at the video-to-gameplay transition. Applying a framebuffer extent clamp avoided device loss for 10 minutes and allowed the game past the title screen on a test build, but after this fix the 3D scene remained black in the reported older fork.
Showing 141–150 of 194 reports
Known issues from Lichii sources
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.
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.
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.
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.
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.
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.
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.
Performance slows in crowded or busy areas, with front/back GPU-thread synchronization drains and waits; short freezes while attacking are also reported.
Shader compilation can cause freezes of about 3 seconds with each step, according to a user report.
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
Build build-117 · Ocarina of Time
Build build-116 · Zelda: Ocarina of Time
Build build-116 · Zelda: Ocarina of Time
Build build-116 · Zelda: Ocarina of Time
Build build-116 · Mario Tennis Fever
Den passenden Build finden
build-117 · Veröffentlicht am November 7, 2026
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
Setze die Filter für Spiel, Status, GPU und Build und kopiere anschließend die Seitenadresse. Ein direkter Link zum Spiel öffnet dessen Berichtskarte.
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.
Treiberversion, Grafikeinstellungen, CPU-Auslastung und die getestete Spielszene können das Ergebnis beeinflussen. Vergleiche diese Details, bevor du deine Konfiguration änderst.
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.