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.
Also listed as: OoT
| Build | Status | GPU / CPU | FPS | Details |
|---|---|---|---|---|
| build 95 | runs with issues | RX 7600 (RADV) / Ryzen 7 7700 | 15–20 FPS | Open report |
Problems or notes: The report says open areas remain CPU-bound at about 15–20 FPS; indoor and small areas were fine.
| Build | Status | GPU / CPU | FPS | Details |
|---|---|---|---|---|
| build-93 | runs with issues | Radeon 5700 XT / AMD Ryzen 6 3600 | Not provided | Open report |
Problems or notes: User reports the emulator hangs and crashes at 11/14 shaders loaded when booting Ocarina Of Time Remake. They say the issue also occurs in Build-88, while Build-83 works; results are the same handheld or docked and on x11 or wayland. The report also identifies the graphics card as AMD RX 6000 series or older.
Current: build-93 (1 record); previous: build-88 (0 records).
| Build | Status | GPU / CPU | FPS | Details |
|---|---|---|---|---|
| build-117 | runs with issues | NVIDIA RTX 50 series; RTX 5090 / 9800x3d | Not provided | Open report |
| build-93 | runs with issues | AMD RX 7000 series; Radeon RX 7900 XTX / AMD Ryzen 9 7900X | Not provided | Open report |
| build-93 | runs with issues | NVIDIA RTX 50 series / Not provided | Not provided | Open report |
| 95 | runs with issues | NVIDIA RTX 30 series or older; 3080TI / 9800X3D | ?–60 FPS | Open report |
Problems or notes: The user reports frequent freezes or frame drops during movement, camera movement, and attacks. On older builds, they experienced occasional hangs requiring them to close and restart the game.
Problems or notes: Title screen and first cutscene work, but the game crashes immediately after the first cutscene. The report identifies the game as “Other / not listed” and refers to it as Ocarina of Time Remake (Update 1.1.1).
Problems or notes: A user reports the game freezes when pressing a button in the ocarina menu.
Problems or notes: While walking or spinning, the “Building X Shaders” status message coincides with freezing or stuttering and drops to 15 or fewer FPS; performance is reported as 40–60 FPS otherwise. The commenter reports first-visit shader stutter.
Current: build-117 (1 record); previous: build-116 (0 records).
| Build | Status | GPU / CPU | FPS | Details |
|---|---|---|---|---|
| build-93 | runs with issues | Radeon 9060 XT / Ryzen 7700x | Not provided | Open report |
| nx2-build-95 (222877d) | runs with issues | RTX 5070 Ti / Not provided | Not provided | Open report |
Problems or notes: User reported an extremely bright sky obscuring visibility in open areas such as Hyrule Field. A comment attributed the white haze to light-volume probe data being read further into memory than was bound, and mentioned a separate NaN-safe min/max change that could spread bloom on AMD. The comment said these changes were not yet in a published release.
Problems or notes: User reports that preloaded pipelines were evicted after 9000 frames, leading to runtime pipeline rebuilds and stutter when moving into a new area.
Current: build-93 (1 record); previous: build-88 (0 records).
| Build | Status | GPU / CPU | FPS | Details |
|---|---|---|---|---|
| 95 | runs with issues | RTX2060 / Not provided | 15–22 FPS | Open report |
Problems or notes: The user reports delayed AV1 cinematics and audio playing faster. Normal gameplay is reported at about 15–22 FPS.
| Build | Status | GPU / CPU | FPS | Details |
|---|---|---|---|---|
| build-75 | runs with issues | NVIDIA RTX 50 series / Not provided | Not provided | Open report |
Problems or notes: The issue reports a hard black screen outside captions in handheld mode and a vaseline-like image in docked mode. Comments report black screens during gameplay and the introductory cinematic, intermittent black flashes, excessively bright and low-resolution handheld visuals, and audio playing ahead of the video.
Current: build-75 (1 record); previous: build-70 (0 records).
Showing 81–90 of 308 reports
Known issues from Lichii sources
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.
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.
Distant mountains remain overexposed with a white glow after the coloured blocks are removed; the source identifies this as a separate bloom/exposure issue.
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.
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.
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.
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.
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.
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.
AV1 cinematics are delayed, with audio playing faster.
Showing 161–170 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
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
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.