Other / not listed
Translucent shaders flicker on water and garden windows.
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
76 Einträge zu Spielen und Testumgebungen sowie 175 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-75 | runs with issues | NVIDIA GeForce RTX 5080 (16 GB) / Intel Core Ultra 7 270K Plus (24 threads) | 28–29 FPS | Open report |
Problems or notes: User report: Docked mode was required to render; Handheld showed a black 3D screen. Gameplay settled at 28–29 FPS, while menus and loading screens ran at 53–59 FPS. The report attributes the limit to CPU load. No attempted settings changes improved the gameplay ceiling.
Current: build-75 (1 record); previous: build-70 (0 records).
| Build | Status | GPU / CPU | FPS | Details |
|---|---|---|---|---|
| build-75 | runs with issues | NVIDIA RTX 3050 Laptop / AMD Ryzen 7 5800H | 30 FPS | Open report |
Problems or notes: User report: The game boots and presents frames at a steady 30 FPS, but remains on a black screen after its AV1 video streams fail because FFmpeg has no decoder for "video/av1". NVDEC Off and Gpu reportedly make no difference; the same result was reported on an AMD Radeon iGPU. Vulkan was used.
Current: build-75 (1 record); previous: build-70 (0 records).
| Build | Status | GPU / CPU | FPS | Details |
|---|---|---|---|---|
| build-75 | runs with issues | Adreno 740 / Snapdragon 8 Gen 2 | Not provided | Open report |
Problems or notes: Black screen despite booting to the AV1 video stage; pipeline-builder threads remain busy compiling large compute shaders, with memory exhaustion or GPU hangs reported in tests. Audio was intermittent. In a separate Eglantine PR #614 test, it reached the title screen and New Game, then went black at the first in-game frame at about 60 FPS.
Current: build-75 (1 record); previous: build-70 (0 records).
| Build | Status | GPU / CPU | FPS | Details |
|---|---|---|---|---|
| build-75 | not booting | AMD Radeon RX 6750 XT (RDNA2) / Intel Core i7-11700F | Not provided | Open report |
| build-75 | runs with issues | AMD Radeon RX 6800 XT (16 GB, RDNA 2) / AMD Ryzen 5 9600X | Not provided | Open report |
| build-75 | runs with issues | RX 9070 XT / Not provided | Not provided | Open report |
| build-75 | runs with issues | AMD Radeon RX 9060 XT 16 GB (Navi 44) / AMD Ryzen 7 5700 | Not provided | Open report |
Problems or notes: On Windows 11 25H2, the game passes the initial launching stage but becomes unresponsive at “Building 9 shaders”; audio continues and it does not reach gameplay. The report identifies the game as Switch 2 version 1.1.1.
Problems or notes: On Windows 11 Version 26H2, the Start Menu and 2D UI render, but gameplay has a completely black screen for all 3D geometry. With use_disk_shader_cache = true, subsequent boots hang at Loading Shaders 25 / 27; the reporter says deleting cache/shader/0400486024dec000 and setting use_disk_shader_cache = false resolves the startup freeze. The report says the black-screen workaround still does not render 3D scenes on this RDNA 2 card.
Problems or notes: Reporter describes a black screen after the intro caused by a rejected 1080p upscaler shader. They report a second AMD-only rendering issue that leaves the world black except around Navi and Link; with both cited fixes, gameplay renders. Handheld mode is reported as brighter and blurrier than Docked mode. Texture flicker is reported with Low GPU accuracy and GPU thread split; High removes it but disables the split and runs at about 9 fps.
Problems or notes: User reports over-bright bloom/glow, dense fog, incorrect lighting on characters and terrain, and some textures decoded as garbage after entering an outdoor area. The game does not crash. Performance was reported as 33–34 ms/frame until about 80 seconds, then 89.5 ms/frame (about 11 fps) outdoors.
Current: build-75 (4 records); previous: build-70 (0 records).
| Build | Status | GPU / CPU | FPS | Details |
|---|---|---|---|---|
| build-75 | runs with issues | RX 5700 / Not provided | 32 FPS | Open report |
| build-75 | runs with issues | AMD Radeon RX 7900 XTX / Not provided | 12 FPS | Open report |
Problems or notes: The comment reports 4800 to 16800 presents and 32 FPS, and says the game presents frames. This is compared with local builds of commit b8c812b18 that stalled at max present 8 and showed no frames; the difference's cause is unresolved.
Problems or notes: User reports no hang, but the 3D scene is black with HUD only.
Current: build-75 (2 records); previous: build-70 (1 record).
Also listed as: OoT
| Build | Status | GPU / CPU | FPS | Details |
|---|---|---|---|---|
| build-75 | runs with issues | AMD RX 7000 series / AMD Ryzen 5 5600G with Radeon Graphics | Not provided | Open report |
Problems or notes: User reports audio and video desynchronization on the title screen and intro. A commenter reports title-screen video in heavy slow motion, audio leading by approximately 3 seconds and the gap increasing by the initial dream cutscene; changing Frame Pacing (30/60/Auto) or reducing Anisotropic Filtering to 2x did not resolve it.
Current: build-75 (1 record); previous: build-70 (0 records).
Showing 1–10 of 11 reports
Known issues from Lichii sources
Translucent shaders flicker on water and garden windows.
Town vegetation and small clutter render at a distance but disappear when approached; a later report says flowers no longer disappear in builds 94/95, while tree leaves still do.
User reports describe multi-second GPU-thread shader translation stalls, gameplay stuttering, and growing synchronous OnCPURead waits during long sessions.
Blinding white bloom/flare streak in Kakariko Village; a commenter reports it also occurs in the well, later areas, and frozen Zora's domain.
Performance varies by boot on the same build, save, and scene. Heavy boots run 20–25% slower in gameplay, and job workers stay awake about 45% longer.
Plants around the Castle render as dead; a commenter reports bushes render correctly at a distance.
Clean audio from a different point of the game plays while the intro image is displayed; audio and picture are substantially out of sync.
User reports a crash after the intro cinematic when shader and pipeline compilation starts, with Vulkan device loss and NVIDIA driver errors.
Commenters report similar crashes and audio desynchronization during the intro cutscene.
User reports that Fire Emblem: Fortune's Weave crashes on Linux with VK_ERROR_DEVICE_LOST and a GPU reset on AMD Radeon GPUs.
Showing 21–30 of 188 issues
Aktuelle Release-Hinweise
Build build-94 · Ocarina of Time
Build build-94 · Nicht angegeben
Build build-94 · Nicht angegeben
Build build-94 · Nicht angegeben
Build build-94 · Nicht angegeben
Den passenden Build finden
build-75 · Veröffentlicht am November 5, 2026
12 veröffentlichte Downloaddateien für diesen Build.
Probiere den neuesten verfügbaren Release aus: build-94. 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.