Mario Kart World
A user report says stock build 88 reset the GPU about 25 seconds after launch on Linux RADV.
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 |
|---|---|---|---|---|
| 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 |
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.
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.
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.
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.
| Build | Status | GPU / CPU | FPS | Details |
|---|---|---|---|---|
| build-93 | runs with issues | AMD Radeon RX 9070 XT / Not provided | Not provided | Open report |
Problems or notes: Severe bright pink, cyan, and white lines appear along mountain silhouettes, especially where mountains meet the sky, in Kakariko Village. Shader compilation continues during gameplay, especially when moving or rotating the camera.
Current: build-93 (1 record); previous: build-88 (0 records).
Showing 1–5 of 5 reports
Known issues from Lichii sources
A user report says stock build 88 reset the GPU about 25 seconds after launch on Linux RADV.
With EDEN_NX2_PRELOAD_ALL_PIPELINES=1, pipelines not used for 9000 frames are evicted, leading to runtime rebuilds and stutter when entering a new area.
With EDEN_NX2_PRELOAD_ALL_PIPELINES=1, pipelines are evicted after 9000 frames, causing runtime builds, long held draws, and a reported freeze.
Grass and pebbles disappear or flicker during sword attacks; disabling persistent pipeline cache was reported to make grass disappear permanently, while enabling it left flickering.
Recorded fix: A commenter reports the issue was fixed in build-116.
User reports significantly worse performance and that parts of the game are broken in build 117 compared with build 93 on NVIDIA RTX 30 series or older.
Walls, environmental geometry, and some interactive objects are invisible; occasional stuttering is also reported.
A commenter reports invisible push blocks.
A commenter reports that objects and doors do not appear.
Issue reports describe audio desynchronization and crashes or full-system freezes during early cutscenes on AMD graphics cards.
In build 116, a user reports frame generation rapidly switching between idle and auto flowstate, lower frame rates, stuttering, and the texture cache being overwritten. A commenter also reports white flashes on Windows 11.
Showing 101–110 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
Für Ocarina of Time ist kein getesteter Build mit verfügbarem Download verknüpft. Sieh dir die aktuellen Releases oder die Diskussion zum Spiel im Issue-Tracker an.
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.