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, Ocarina of Time
| Build | Status | GPU / CPU | FPS | Details |
|---|---|---|---|---|
| build-83 | unknown | Not provided / Not provided | Not provided | Open report |
Problems or notes: The release says the perf9 build was tested successfully in Ocarina of Time, but provides no gameplay duration or specific tested hardware.
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 |
|---|---|---|---|---|
| build-83 | runs with issues | RTX 3090 24 GB / Ryzen 9 5900X | Not provided | Open report |
Problems or notes: The user reported repeated GPU-thread graphics-pipeline builds during gameplay across boots, causing a visible hitch and about 943–998 ms of GPU-thread time in the first 10 seconds. A later user comment reported the issue fixed for them on build-88 (MSVC), which includes #194; that report is not maintainer-confirmed.
Current: build-83 (1 record); previous: build-75 (0 records).
Also listed as: OoT, Ocarina of Time
| Build | Status | GPU / CPU | FPS | Details |
|---|---|---|---|---|
| build-83 | runs with issues | RTX 5090 / Ryzen 7 9800X3D | Not provided | Open report |
Problems or notes: Opening rendered and controllable Kokiri Forest gameplay was reached. Some sessions hung at “Closing software…” during shutdown, while others exited successfully. The source does not establish a cause or fix.
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
Showing 11–13 of 13 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.