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
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
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 |
|---|---|---|---|---|
| Lichii nx2 build 75 | runs with issues | NVIDIA GeForce RTX 5080 (16 GB) / Intel Core Ultra 7 270K Plus | 28–29 FPS | Open report |
| nx2-build-88 (55532f2) | runs with issues | NVIDIA RTX 5070 Ti 16 GB / Ryzen 7 9800X3D | Not provided | Open report |
| nx2-build-117 | runs with issues | Radeon RX 6600M / Xeon E5-2666 v3 | Not provided | Open report |
Problems or notes: Gameplay settles at 28–29 FPS, while menus and loading screens run at 53–59 FPS. The reporter says Docked mode is required to render; Handheld mode gives a black 3D screen. They report that 2X resolution has flicker/line artifacts. This is a user report.
Problems or notes: The user reports heavy stutter when re-entering areas after pipelines are evicted and rebuilt. They attribute this to eviction after 9000 frames and report bursts of pipeline rebuilding on the GPU thread.
Problems or notes: A user reports frequent shader-building notifications and stutter, including when revisiting areas. Their capture showed runtime pipeline creation but no eviction entries; they say they cannot yet determine how much persists on a second launch.
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).
Showing 1–4 of 4 reports
Known issues from Lichii sources
Day-only garbage graphics in the Bombchu Bowling Alley: stones and ovens flash pink, yellow, red, or black, and the sign displays garbage, noise, and fragments of another image. It looks correct at night after leaving and returning, and was still present in build-117.
After outdoor play, the sky becomes flat yellow-white and water shimmers green until reboot, due to NaNs spreading through bloom. The report says the NaNs probably originate from fog/foliage probe reads beyond the 64 MiB graphics table-pointer cap.
Recorded fix: Use NaN-safe min/max/clamp handling and fix table-pointer reads beyond the old 64 MiB cap; the reporter confirmed normal visuals after both fixes.
Foliage and vegetation near the player may turn into dead-looking variants or lose leaves up close, including hedges and plants in Hyrule Castle; reports also mention trees, Kokiri Forest bushes, Castle Town hedges, and Hyrule Field grass. One user describes the behavior as an inverted LOD.
On macOS/MoltenVK with an Apple M1, the Switch 2 NSO version boots and plays audio but presents a black image from startup, with approximately 1 FPS and occasional red/green block artifacts.
On AMD GPUs, Ocarina of Time's compute shaders can fail compilation with VK_ERROR_OUT_OF_HOST_MEMORY or cause the AMD driver to crash. The issue report describes missing intro video and an eventual process crash; a later user reports an access violation inside amdvlk64.dll.
OpenGL is reported not to work for this game because GLSL task and mesh programs are not implemented, resulting in repeated errors and an emulator hang.
Rejecting shader hashes before translation skips their dispatches and can result in missing output or a black screen; a user reports the environment switch did not affect the tested Vulkan compute-pipeline path.
Recorded fix: For testing shader rejection, keep the disk shader cache off or delete it before each run; the maintainer says cached shaders are loaded without checking the rejection list.
Performance slows in crowded or busy areas, with front/back GPU-thread synchronization drains and waits; short freezes while attacking are also reported.
Shader compilation can cause freezes of about 3 seconds with each step, according to a user report.
On integrated AMD graphics, device-memory thresholds can keep the texture cache collector in aggressive mode even though deleting all images cannot reduce total usage below the threshold. This causes extensive image churn and GPU waits during gameplay.
Showing 31–40 of 361 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
build-83 · Veröffentlicht am November 6, 2026
12 veröffentlichte Downloaddateien für diesen Build.
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.