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 |
|---|---|---|---|---|
| release-binaries #80 | runs with issues | NVIDIA RTX 50 series / Not provided | Not provided | Open report |
Problems or notes: The emulator force-quit after remaining on the "Loading Shaders" screen for about 2 seconds.
| Build | Status | GPU / CPU | FPS | Details |
|---|---|---|---|---|
| build-70 | runs with issues | Not provided / Not provided | Not provided | Open report |
Problems or notes: Some races still stall while shaders build.
Current: build-70 (1 record); previous: build-65 (0 records).
| Build | Status | GPU / CPU | FPS | Details |
|---|---|---|---|---|
| build-65 | runs with issues | NVIDIA RTX 30 series or older / Not provided | Not provided | Open report |
Problems or notes: Freezes when menu preview videos play for the selected mode. A comment says the log records the game aborting (2162-0001) during menu videos; the report was closed as stale, and no resolution was confirmed.
Current: build-65 (1 record); previous: nx2-build-34 (0 records).
| Build | Status | GPU / CPU | FPS | Details |
|---|---|---|---|---|
| build-83 | runs with issues | AMD RX 9000 series / Not provided | Not provided | Open report |
Problems or notes: The emulator crashes after 5 to 10 minutes of gameplay.
Current: build-83 (1 record); previous: build-75 (0 records).
| Build | Status | GPU / CPU | FPS | Details |
|---|---|---|---|---|
| build-83 | not booting | Other / Not provided | Not provided | Open report |
Problems or notes: User reports that the game blacks out when booted. They identify this as a regression from build 75.
Current: build-83 (1 record); previous: build-75 (0 records).
| Build | Status | GPU / CPU | FPS | Details |
|---|---|---|---|---|
| build-83 | runs with issues | RTX 4070 SUPER 12 GB / i5-14600KF | 30–60 FPS | Open report |
| Not provided | playable | NVIDIA GeForce RTX 4070 SUPER / Intel Core i5-14600KF | 90–130 FPS | Open report |
Problems or notes: The commenter reports slow motion at about 30 fps and says GPU Mode: Fast reached 60 fps in most areas. They also report shader-build stutter on new content, fewer visual artifacts in a local build, and cache-warming stutter after updates.
Problems or notes: User-reported normal-speed play with the speed limit off. The approximately 90–130 FPS figures include built-in frame generation and are displayed FPS, not rendered FPS.
Current: build-83 (1 record); previous: build-75 (0 records).
| Build | Status | GPU / CPU | FPS | Details |
|---|---|---|---|---|
| build-83 | runs with issues | RTX 3060 12 GB / i5-11400 | Not provided | Open report |
| Not provided | runs with issues | NVIDIA GeForce GTX 1650 / Not provided | 7 FPS | Open report |
Problems or notes: The user reports audio/video desynchronization. The AV1 title and intro movies are reported below 60 FPS, and gameplay in Kokiri Forest is reported at about 15 FPS on build 83 versus about 24 FPS on build 80. The user notes that the build-80 movie ran at about 24 FPS and the build-83 movie at about 20–36 FPS.
Problems or notes: The user reports the game will not exceed 7 FPS and they cannot leave the character's bedroom, despite trying low settings.
Current: build-83 (1 record); previous: build-75 (0 records).
| Build | Status | GPU / CPU | FPS | Details |
|---|---|---|---|---|
| Lichii build 83 (MSVC) | runs with issues | NVIDIA GeForce GTX 1070 / Intel Core i7-7700 | 18 FPS | Open report |
Problems or notes: The user reports audio/video desynchronization and frequent hangs or stalls during play.
Showing 31–40 of 308 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
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.