Ocarina of time
Black square lines appear across Hyrule Field and disappear when approached.
Spielekompatibilität
Spielekompatibilität des Lichii Emulators
Du hast ein bestimmtes Spiel im Sinn? Erfahre, wie es mit Lichii läuft, welche Probleme bekannt sind und welchen Build du ausprobieren kannst.
Latest recorded build
build-117
Published November 7, 2026
Ein Spiel finden
Nach kompatiblen Lichii-Spielen suchen
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
Game Compatibility Results
Recorded performance
Performance by Build and Hardware
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.
Mario Kart World Reported platform: Windows
| Build | Status | GPU / CPU | FPS | Details |
|---|---|---|---|---|
| Not provided | runs with issues | rtx 5050 / ryzen 5 8400f | Not provided | Open report |
Not provided report
Statusruns with issues
GPUrtx 5050
CPUryzen 5 8400f
DriverNot provided
Recorded FPSNot provided
Problems or notes: A commenter reports that the whole emulator crashes.
Related game issues
- [Crash] GPU crash on mesh shader building, fixed in other fork (open)
- [Crash] Linux RADV, Navi 33 (Steam Machine): GPU reset from mesh draws in OoT, "Illegal opcode in command stream", also MKW on stock build 88 (open)
- [Perf] Mario Kart World (0400C3F00006E000): severe 3D in-game performance drop from build 93 (40-54 FPS) to build 95 (17-23 FPS) (open)
- [VBug] Switch Pro Controller causes desktop input flood / mouse click freeze on Windows (open)
- [Crash] RX9070XT, SteamOS (closed)
- [VBug] MKW 1.8.0 no render no textures (intel uhd graphics) (open)
- [Crash] (open)
- crash or infinite loading when use windows 10 (any game) (closed)
- GPU crash (closed)
- [GBug] Mario Kart World – Severe Performance Regression in Build 75 (closed)
- [VBug] Build 93 finaly has no major visual errors but has poor performance 9070xt (open)
- graphics memory leak in MKW (closed)
- Mario kart Crash on SplashScreen (closed)
- [VBug] playing mario kart world but textures wont load. also crashes when playing the grand prix race (open)
- [Crash] macOS MKW Loading Splash animation shows, but crashes after. (closed)
- [MKW 1.8.0] Grand Prix crash during course selection, but excellent Free Roam performance on 16 GB RAM (Build 31) (closed)
- Release note: Building mesh shaders can cause a hard crash on AMD 7000 series and some other AMD cards; on Linux this may freeze the system, while on Windows it crashes the emulator.
- Release note: A user report says stock build 88 reset the GPU about 25 seconds after launch on Linux RADV.
- Release note: User reports 17–23.8 FPS in 3D races on build-95, compared with 40.0–54.1 FPS on build-93 under the same reported test conditions.
- Release note: On Windows 11, connecting an official Nintendo Switch Pro Controller while Lichii is open reportedly floods the host OS with phantom inputs, making desktop mouse clicks unresponsive and keyboard typing erratic. Unplugging the controller reportedly restores normal input.
- Release note: On Linux, the game froze near the title screen, followed by pixel artefacts and a system crash.
- Release note: On Intel UHD integrated graphics, the game reportedly boots with no rendering or textures; later, some textures appeared gray. The reporter also reports crashes when teleporting during free roam.
- Release note: Crash reported after joining the game with OpenGL.
- Release note: A user reports a crash after brief rendering while loading on Windows 10.
- Release note: A user reported GPU crashes when booting on Bazzite with Mesa 26.2.4; the report was later said to concern an older nx2 build.
- Release note: A user reports severe performance regression after updating from Build 70 to Build 75 on Linux, with around 10 FPS on the title screen, barely reaching 15 FPS, constant stuttering, and RAM usage increasing nonstop.
- Release note: A commenter reports darker, heavily shaded characters and a frame-rate drop of about 5 to 10 FPS in builds after 72, and associates the onset in their tests with commit 3aa89d1c.
- Release note: Poor frame rates; the issue says performance is worse than on most other forks.
- Release note: A user reported rapidly increasing VRAM usage after starting the game, followed by low framerate.
- Release note: Crashes while loading before the main menu; user comments also report session or emulator crashes.
- Release note: The user reports missing textures and buggy visuals, occasional startup crashes, and crashes during Grand Prix races on Intel integrated graphics.
- Release note: On macOS, crashes after the loading splash in tag/build-65.
- Release note: The emulator crashed/exited while selecting a course in Grand Prix mode. The user had not confirmed reproducibility or whether Process Lasso contributed.
Compared with Previous Build
Mario Kart World Reported platform: Windows 11 24H2
| Build | Status | GPU / CPU | FPS | Details |
|---|---|---|---|---|
| Not provided | runs with issues | RX 6650 XT / Not provided | Not provided | Open report |
Not provided report
Statusruns with issues
GPURX 6650 XT
CPUNot provided
DriverAMD proprietary driver 2.0.353
Recorded FPSNot provided
Problems or notes: A commenter reports that after Build 72, characters look too dark and heavily shaded, and frame rate drops by about 5 to 10 FPS. The commenter says the problem appears with commit 3aa89d1c in their tests.
Related game issues
- [Crash] GPU crash on mesh shader building, fixed in other fork (open)
- [Crash] Linux RADV, Navi 33 (Steam Machine): GPU reset from mesh draws in OoT, "Illegal opcode in command stream", also MKW on stock build 88 (open)
- [Perf] Mario Kart World (0400C3F00006E000): severe 3D in-game performance drop from build 93 (40-54 FPS) to build 95 (17-23 FPS) (open)
- [VBug] Switch Pro Controller causes desktop input flood / mouse click freeze on Windows (open)
- [Crash] RX9070XT, SteamOS (closed)
- [VBug] MKW 1.8.0 no render no textures (intel uhd graphics) (open)
- [Crash] (open)
- crash or infinite loading when use windows 10 (any game) (closed)
- GPU crash (closed)
- [GBug] Mario Kart World – Severe Performance Regression in Build 75 (closed)
- [VBug] Build 93 finaly has no major visual errors but has poor performance 9070xt (open)
- graphics memory leak in MKW (closed)
- Mario kart Crash on SplashScreen (closed)
- [VBug] playing mario kart world but textures wont load. also crashes when playing the grand prix race (open)
- [Crash] macOS MKW Loading Splash animation shows, but crashes after. (closed)
- [MKW 1.8.0] Grand Prix crash during course selection, but excellent Free Roam performance on 16 GB RAM (Build 31) (closed)
- Release note: Building mesh shaders can cause a hard crash on AMD 7000 series and some other AMD cards; on Linux this may freeze the system, while on Windows it crashes the emulator.
- Release note: A user report says stock build 88 reset the GPU about 25 seconds after launch on Linux RADV.
- Release note: User reports 17–23.8 FPS in 3D races on build-95, compared with 40.0–54.1 FPS on build-93 under the same reported test conditions.
- Release note: On Windows 11, connecting an official Nintendo Switch Pro Controller while Lichii is open reportedly floods the host OS with phantom inputs, making desktop mouse clicks unresponsive and keyboard typing erratic. Unplugging the controller reportedly restores normal input.
- Release note: On Linux, the game froze near the title screen, followed by pixel artefacts and a system crash.
- Release note: On Intel UHD integrated graphics, the game reportedly boots with no rendering or textures; later, some textures appeared gray. The reporter also reports crashes when teleporting during free roam.
- Release note: Crash reported after joining the game with OpenGL.
- Release note: A user reports a crash after brief rendering while loading on Windows 10.
- Release note: A user reported GPU crashes when booting on Bazzite with Mesa 26.2.4; the report was later said to concern an older nx2 build.
- Release note: A user reports severe performance regression after updating from Build 70 to Build 75 on Linux, with around 10 FPS on the title screen, barely reaching 15 FPS, constant stuttering, and RAM usage increasing nonstop.
- Release note: A commenter reports darker, heavily shaded characters and a frame-rate drop of about 5 to 10 FPS in builds after 72, and associates the onset in their tests with commit 3aa89d1c.
- Release note: Poor frame rates; the issue says performance is worse than on most other forks.
- Release note: A user reported rapidly increasing VRAM usage after starting the game, followed by low framerate.
- Release note: Crashes while loading before the main menu; user comments also report session or emulator crashes.
- Release note: The user reports missing textures and buggy visuals, occasional startup crashes, and crashes during Grand Prix races on Intel integrated graphics.
- Release note: On macOS, crashes after the loading splash in tag/build-65.
- Release note: The emulator crashed/exited while selecting a course in Grand Prix mode. The user had not confirmed reproducibility or whether Process Lasso contributed.
Compared with Previous Build
Mario Kart World Reported platform: Windows 11
| Build | Status | GPU / CPU | FPS | Details |
|---|---|---|---|---|
| build-83 | runs with issues | intel uhd graphics / intel core i5 gen 13th | Not provided | Open report |
| 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 |
build-83 report
Statusruns with issues
GPUintel uhd graphics
CPUintel core i5 gen 13th
DriverNot provided
Recorded FPSNot provided
Problems or notes: The user reports missing textures and buggy visuals after boot, occasional crashes during startup, and crashes during Grand Prix races. A comment says the issue is still present in build-88.
31 report
Statusruns with issues
GPURX 6600
CPUi5-12400
DriverNot provided
Recorded FPSNot provided
Problems or notes: Crashes while loading before the expected main menu.
Not provided report
Statusunknown
GPUNVIDIA RTX 50 series
CPUNot provided
DriverNot provided
Recorded FPSNot provided
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.
Related game issues
- [Crash] GPU crash on mesh shader building, fixed in other fork (open)
- [Crash] Linux RADV, Navi 33 (Steam Machine): GPU reset from mesh draws in OoT, "Illegal opcode in command stream", also MKW on stock build 88 (open)
- [Perf] Mario Kart World (0400C3F00006E000): severe 3D in-game performance drop from build 93 (40-54 FPS) to build 95 (17-23 FPS) (open)
- [VBug] Switch Pro Controller causes desktop input flood / mouse click freeze on Windows (open)
- [Crash] RX9070XT, SteamOS (closed)
- [VBug] MKW 1.8.0 no render no textures (intel uhd graphics) (open)
- [Crash] (open)
- crash or infinite loading when use windows 10 (any game) (closed)
- GPU crash (closed)
- [GBug] Mario Kart World – Severe Performance Regression in Build 75 (closed)
- [VBug] Build 93 finaly has no major visual errors but has poor performance 9070xt (open)
- graphics memory leak in MKW (closed)
- Mario kart Crash on SplashScreen (closed)
- [VBug] playing mario kart world but textures wont load. also crashes when playing the grand prix race (open)
- [Crash] macOS MKW Loading Splash animation shows, but crashes after. (closed)
- [MKW 1.8.0] Grand Prix crash during course selection, but excellent Free Roam performance on 16 GB RAM (Build 31) (closed)
- Release note: Building mesh shaders can cause a hard crash on AMD 7000 series and some other AMD cards; on Linux this may freeze the system, while on Windows it crashes the emulator.
- Release note: A user report says stock build 88 reset the GPU about 25 seconds after launch on Linux RADV.
- Release note: User reports 17–23.8 FPS in 3D races on build-95, compared with 40.0–54.1 FPS on build-93 under the same reported test conditions.
- Release note: On Windows 11, connecting an official Nintendo Switch Pro Controller while Lichii is open reportedly floods the host OS with phantom inputs, making desktop mouse clicks unresponsive and keyboard typing erratic. Unplugging the controller reportedly restores normal input.
- Release note: On Linux, the game froze near the title screen, followed by pixel artefacts and a system crash.
- Release note: On Intel UHD integrated graphics, the game reportedly boots with no rendering or textures; later, some textures appeared gray. The reporter also reports crashes when teleporting during free roam.
- Release note: Crash reported after joining the game with OpenGL.
- Release note: A user reports a crash after brief rendering while loading on Windows 10.
- Release note: A user reported GPU crashes when booting on Bazzite with Mesa 26.2.4; the report was later said to concern an older nx2 build.
- Release note: A user reports severe performance regression after updating from Build 70 to Build 75 on Linux, with around 10 FPS on the title screen, barely reaching 15 FPS, constant stuttering, and RAM usage increasing nonstop.
- Release note: A commenter reports darker, heavily shaded characters and a frame-rate drop of about 5 to 10 FPS in builds after 72, and associates the onset in their tests with commit 3aa89d1c.
- Release note: Poor frame rates; the issue says performance is worse than on most other forks.
- Release note: A user reported rapidly increasing VRAM usage after starting the game, followed by low framerate.
- Release note: Crashes while loading before the main menu; user comments also report session or emulator crashes.
- Release note: The user reports missing textures and buggy visuals, occasional startup crashes, and crashes during Grand Prix races on Intel integrated graphics.
- Release note: On macOS, crashes after the loading splash in tag/build-65.
- Release note: The emulator crashed/exited while selecting a course in Grand Prix mode. The user had not confirmed reproducibility or whether Process Lasso contributed.
Compared with Previous Build
Current: build-83 (1 record); previous: build-75 (0 records).
Showing 1–5 of 5 reports
Known issues from Lichii sources
Known Game Issues
Pokémon Pokopia
Furniture is invisible in homes, with only its shadows visible.
Legend of Zelda Ocarine of Time (remake)
Reports describe audio/video desynchronization, audio stutter, hangs or stalls, low frame rates, and an in-game freeze.
Ocarina of Time Remake
The sky is extremely bright and obscures visibility in open areas such as Hyrule Field.
Other / not listed
The stone tablet does not render in the Lost Woods to Zora River area, although grass particles render on it.
Other / not listed
Freezes while building shaders and does not start; the start menu theme sometimes starts and stops after about 10 seconds.
Other / not listed
The game loads and music plays, but the screen stays black.
Other / not listed
The fairy fountain grotto's walls and other parts are invisible in underground areas with red health fairies. A commenter reported that a damaged NUP game-data file was the cause.
Recorded fix: PR #267 workaround: when loading the NUP, serve a .zs member with no zstd header from its closest sound sibling. A user reported that the workaround restored the grotto.
Ocarina of Time
Skipping or batching Preflushable buffer downloads can cause the scene to be overexposed because guest reads may occur before downloaded GPU-written data is available. The issue also reports potentially stale exposure data with the no-preflush experiment.
Ocarina of Time
A commenter reports that Kokiri Forest and the Deku Tree can run much more slowly after watching the New Game intro than when loading a save directly; the commenter reports a storage-write extent branch improved the intro-first result.
Showing 141–150 of 361 issues
Aktuelle Release-Hinweise
Kompatibilitätsänderungen in den neuesten Builds
Build build-117 · Ocarina of Time
Fixed a crash during shader building on Windows drivers for RX 6000 (RDNA2), RX 5000 (RDNA1), Vega, and Polaris cards. The faster matrix path now runs only on RDNA3 and newer.
Build build-116 · Zelda: Ocarina of Time
Ocarina of Time is described as very stable; foliage and Hyrule Field grass rendering are fixed, and many users get 60+ fps.
Build build-116 · Zelda: Ocarina of Time
NVIDIA DLSS Super Resolution can replace the game's own upscaler on RTX cards; the setting is experimental.
Build build-116 · Zelda: Ocarina of Time
A new option turns off the game's sharpening anti-aliasing; the default Game setting behaves as before, and DLSS takes priority if both are enabled.
Build build-116 · Mario Tennis Fever
The game runs fully at 60 fps, and texture glitches are fixed.
Den passenden Build finden
Welchen Build soll ich verwenden?
Für Mario Kart World 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
Häufige Fragen zur Spielekompatibilität
Wie teile ich ein Spiel mit diesen Filtern?
Setze die Filter für Spiel, Status, GPU und Build und kopiere anschließend die Seitenadresse. Ein direkter Link zum Spiel öffnet dessen Berichtskarte.
Was kann ich bei einem schwarzen Bildschirm versuchen?
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.
Warum kann dieselbe GPU unterschiedliche Ergebnisse liefern?
Treiberversion, Grafikeinstellungen, CPU-Auslastung und die getestete Spielszene können das Ergebnis beeinflussen. Vergleiche diese Details, bevor du deine Konfiguration änderst.
Wo kann ich ein fehlendes Testergebnis melden?
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.