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 Remake, OoT
| Build | Status | GPU / CPU | FPS | Details |
|---|---|---|---|---|
| nx2-9fa4a71fa0-nx2 | runs with issues | AMD Radeon RX 7600, 8 GB / AMD Ryzen 5 5500 | 15 FPS | Open report |
Problems or notes: Gameplay and movies run, but movie voices intermittently pause while video continues, causing late or absent audio. Gameplay was reported at about 15 fps in one test; another report recorded 15.4–19.4 average FPS over three sessions on build 9991f27, with hitches of 2–4 seconds and worst frames of several seconds. No driver crash or visual problems were noticed in the tested forest areas. Movie audio was not evaluated in the 9991f27 sessions.
| Build | Status | GPU / CPU | FPS | Details |
|---|---|---|---|---|
| nx2-build-88 | runs with issues | Intel Arc B580 (BMG G21) / Ryzen 5 5600X | 8 FPS | Open report |
Problems or notes: A user reports about 8 FPS in the intro after a multi-minute shader stall on first boot. The Kokiri intro cutscene picture froze while presents continued. These are user reports.
| Build | Status | GPU / CPU | FPS | Details |
|---|---|---|---|---|
| build-117 | unknown | Not provided / Not provided | Not provided | Open report |
| Lichii Build 95 | not booting | RTX 3050 6GB / i7-13620H | 0 FPS | Open report |
| Not provided | runs with issues | AMD RX 6000 series or older / Not provided | Not provided | Open report |
Problems or notes: A commenter says it runs much better for them on Linux than on Windows 11; no gameplay or FPS details are provided.
Problems or notes: User reports sound from the intro but no video. A comment says Build 116 was worse; another reports the game ran much better for them on Build 117.
Problems or notes: User reports random freezes after 5–15 minutes of play, I/O spikes up to 6GB/s, RAM use continuing to rise until out-of-memory forces the emulator to crash.
Current: build-117 (1 record); previous: build-116 (0 records).
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 |
|---|---|---|---|---|
| 62ba83427e | runs with issues | Radeon 8060S / Ryzen AI MAX+ 395 | 31–37 FPS | Open report |
Problems or notes: In Kokiri Forest, haze, blotches, and a translucent band appear in a fullscreen pass. Rejecting shader 3ddfb1d7a854c849 removed the haze and blotches in that test, while rejecting 780c0536b89fc89e removed fog but left blotches; these workarounds also remove game effects. Two starts stayed black from the beginning, one with music. A reported 31–37 FPS comparison against build-75 used views that were not identical.
| Build | Status | GPU / CPU | FPS | Details |
|---|---|---|---|---|
| build-83 | playable | RTX 4070 Ti / Ryzen 7 7700X | Not provided | Open report |
| 55532f2d814215aaf32a76c214cf129f2cb6282b | runs with issues | RTX 5060 Ti / Ryzen 7 7800X3D | 15–51 FPS | Open report |
Problems or notes: In a tested docked 2x gameplay run, haze was gone and Link and Kokiri Forest were clearly visible without shader rejections. FPS was described as low, with no value stated.
Problems or notes: Foliage, grass, shadows, and atmosphere were reported as substantially improved, and the Great Deku Tree exterior dialogue and interior corridor rendered visibly. Some eastern outdoor views remained severely white/yellow and washed out. Outdoor performance varied from 28–31 FPS in other views to about 15 FPS in problematic areas; the Deku Tree exterior dialogue showed 36 FPS and the interior showed 51 FPS. Texture-format and texture-index assertions were logged; one earlier Accurate attempt exited with code -1073740791, while a later session ran about 20m31s and exited normally. No causal link between assertions, lighting, or the earlier crash was established.
From build-75 to build-83: follow the gameplay changes described for these two builds.
Before: Missing vegetation and incorrect material data; affected lighting and colours; a glowing doorway; one-frame white flashes; and on AMD, shaders could produce a black 3D scene.
After: Additional shader pointers and storage-buffer bindings, corrected buffer tracking and mesh-shader register handling, fixed occlusion-query and nested-return handling, and added the Max Resolution add-on and frame-ahead presentation tuning.
build-75 → build-83
Also listed as: OoT
| Build | Status | GPU / CPU | FPS | Details |
|---|---|---|---|---|
| b4716fc | runs with issues | RX 6700 XT / Not provided | Not provided | Open report |
Problems or notes: The title screen, intro, and cinematics before the Deku Tree exterior cutscene render correctly. That cutscene is black except for a small circle around Navi where the world renders.
Showing 71–80 of 275 reports
Known issues from Lichii sources
A user reports a constant black screen after booting and loading the game on Build 65.
A black rectangle appears in what should be a mini-example guide; the reporter says it also occurs on build 70.
Freezes or aborts while menu preview videos play.
The reporter says they cannot swim in ink during the tutorial on MacOS.
Screen and camera shaking during play on build 65.
A user reported rapidly increasing VRAM usage after starting the game, followed by low framerate.
Crashes while loading before the main menu; user comments also report session or emulator crashes.
User reports fluctuating performance of approximately 10–30 FPS, bushes disappearing when approached or changing shape, and intermittent lighting and shading glitches.
Black screens during the introductory cinematic, GDT sequence, or gameplay; reports include intermittent black flashes and audio playing ahead of video.
Docked mode may show a black screen except for captions or HUD, while handheld mode may appear excessively bright, low resolution, or vaseline-like.
Showing 251–260 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.