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.
Also listed as: OoT, Zelda, Ocarina of Time
| Build | Status | GPU / CPU | FPS | Details |
|---|---|---|---|---|
| build-93 | boots | RX 9060XT 16GB / Ryzen 5 7600 | Not provided | Open report |
Problems or notes: A commenter reports that starting with Accurate GPU enabled loaded the main menu; audio had issues. They say settings could sometimes be changed back, but the issue could recur.
Current: build-93 (1 record); previous: build-88 (0 records).
Also listed as: OoT, Ocarina of Time
| Build | Status | GPU / CPU | FPS | Details |
|---|---|---|---|---|
| build-93 | playable | Not provided / Not provided | 10–25 FPS | Open report |
Problems or notes: The issue title says it was playable at 10–25 FPS; a commenter says it runs almost perfectly.
Current: build-93 (1 record); previous: build-88 (0 records).
Also listed as: OoT, Ocarina of Time
| Build | Status | GPU / CPU | FPS | Details |
|---|---|---|---|---|
| build-93 | boots | RX 9070 XT / Ryzen 7 7800X3D | Not provided | Open report |
Problems or notes: A commenter says video worked on build 93 with the same configuration, keys, firmware, and game files used for build 95.
Current: build-93 (1 record); previous: build-88 (0 records).
| Build | Status | GPU / CPU | FPS | Details |
|---|---|---|---|---|
| build-93 | runs with issues | RX 5700 XT 8GB / Ryzen 5 5600 | Not provided | Open report |
| build-93 | runs with issues | AMD Radeon 9070XT / Intel Core I5 | Not provided | Open report |
Problems or notes: User reports excessive bloom outside the Great Deku Tree, returning to normal after defeating Gohma, and invisible boxes and walls inside it. Windows 10.
Problems or notes: Shaders load slowly and significantly slow gameplay, rebuilding when entering the same area. In the Kokiri Sword area, Link and most surroundings turn solid black; white flickers also occur.
Current: build-93 (2 records); previous: build-88 (0 records).
| Build | Status | GPU / CPU | FPS | Details |
|---|---|---|---|---|
| build-93 | runs with issues | rx 6900xt / Not provided | Not provided | Open report |
Problems or notes: User reports the same vegetation disappearance issue on default settings.
Current: build-93 (1 record); previous: build-88 (0 records).
| Build | Status | GPU / CPU | FPS | Details |
|---|---|---|---|---|
| build-93 | runs with issues | AMD Radeon RX 570 4GB / Intel Core i5-8500 | 4 FPS | Open report |
Problems or notes: The game boots and compiles shaders, but remains at 4 FPS in-game. The reporter says reducing resolution to 1x and changing memory layout to 4GB did not resolve the low FPS; a VRAM management issue on Polaris GPUs is suspected.
Current: build-93 (1 record); previous: build-88 (0 records).
Showing 21–27 of 27 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.