Mario Kart World
The user reports missing textures and buggy visuals, occasional startup crashes, and crashes during Grand Prix races on Intel integrated graphics.
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
98 Einträge zu Spielen und Testumgebungen sowie 275 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 |
|---|---|---|---|---|
| 31 | runs with issues | RX 6600 / i5-12400 | Not provided | Open report |
| Not provided | unknown | NVIDIA RTX 50 series / Not provided | Not provided | Open report |
Problems or notes: Crashes while loading before the expected main menu.
Problems or notes: The issue is labeled [Crash] and marked as a regression, but it does not describe the crash behavior or provide a working build.
Current: build-83 (1 record); previous: build-75 (0 records).
| Build | Status | GPU / CPU | FPS | Details |
|---|---|---|---|---|
| build-117 | runs with issues | NVIDIA RTX 30 series or older / Not provided | Not provided | Open report |
| build-116 | playable | Not provided / Not provided | 60 FPS | Open report |
Problems or notes: The user reports that characters have no shadows.
Problems or notes: Not provided
Current: build-117 (1 record); previous: build-116 (1 record).
| Build | Status | GPU / CPU | FPS | Details |
|---|---|---|---|---|
| build 88 (55532f2), also reproducible on build 75 | runs with issues | NVIDIA GeForce RTX 3050 Ti Laptop GPU / 12th Gen Intel(R) Core(TM) i7-12700H | Not provided | Open report |
Problems or notes: The game reaches a controller screen, but a two-player motion game cannot start: it remains on “Playing with 1 Joy-Con” and reports that the Joy-Con connection was lost. The issue reporter's log shows controller type 5 is unsupported and the emulator disconnects the controller; it also logs no response from a Joy-Con. The left Joy-Con's battery level is not reported. These are user reports, not maintainer-confirmed findings.
| Build | Status | GPU / CPU | FPS | Details |
|---|---|---|---|---|
| build-117 | runs with issues | Other / Apple M1 | 1 FPS | Open report |
Problems or notes: Boots and plays audio, but the image is completely black from startup; intermittent red/green block artifacts are reported. Approximately 1 FPS.
Current: build-117 (1 record); previous: build-116 (0 records).
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.
Showing 51–60 of 275 reports
Known issues from Lichii sources
The user reports missing textures and buggy visuals, occasional startup crashes, and crashes during Grand Prix races on Intel integrated graphics.
Black 3D gameplay scene with HUD or menus still visible; some reports also mention stuttering, audio problems, flickering shadows, or missing tree leaves.
Recorded fix: One commenter reported that switching to Docked mode resolved the black screen. Another reported that the scene rendered after upgrading from build-75 to Windows MSVC build-88, but settings also changed and the cause was not isolated.
The Deku Tree exterior cutscene can render black except for a small circle around Navi, even when the title screen, intro, and earlier cinematics render correctly. A later report also observed a deterministic AMD driver crash while building graphics pipelines in the same scene.
A half-resolution layer can produce dark blotches and translucent patches over Link, terrain, and other objects. User reports traced the issue to a depth image being cleared after a depth copy; one report says PR #185 addresses the ordering, but reports do not establish a confirmed released fix.
River water may be dark or lack visible lit contribution, and one user reported flickering that depends on the sun's position relative to the camera.
Outdoor scenes may remain severely white/yellow and washed out on clean upstream nx2, despite substantial improvements to vegetation and atmosphere.
Texture-format and texture-index assertions were reported during gameplay; a separate report associated a period of such assertions with terrain and subtitle flickering, without establishing causation.
Only character outlines and UI are visible after launching the game.
On Windows build-83, shutdown can hang at “Closing software…” after gameplay. Some sessions completed shutdown successfully; the cause is undetermined.
User reports the game blacks out when booted in build 83; they state it worked in build 75.
Showing 271–280 of 287 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.