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 |
|---|---|---|---|---|
| build-70 | playable | Not provided / M4 Pro | 30–38 FPS | Open report |
| tag/build-65 | not booting | Other / Not provided | 10 FPS | Open report |
Problems or notes: The report says races measured 30–38 fps after macOS performance work.
Problems or notes: Crashes after the loading splash. The issue report says a workaround bypassed the crash but resulted in 10 fps.
Current: build-70 (1 record); previous: build-65 (0 records).
| Build | Status | GPU / CPU | FPS | Details |
|---|---|---|---|---|
| build-117 | runs with issues | NVIDIA RTX 30 series or older / Not provided | Not provided | Open report |
| build-116 | playable | Not provided / Not provided | 60 FPS | Open report |
Problems or notes: The user reports that characters have no shadows.
Problems or notes: Not provided
Current: build-117 (1 record); previous: build-116 (1 record).
| Build | Status | GPU / CPU | FPS | Details |
|---|---|---|---|---|
| build 88 (55532f2), also reproducible on build 75 | runs with issues | NVIDIA GeForce RTX 3050 Ti Laptop GPU / 12th Gen Intel(R) Core(TM) i7-12700H | Not provided | Open report |
Problems or notes: The game reaches a controller screen, but a two-player motion game cannot start: it remains on “Playing with 1 Joy-Con” and reports that the Joy-Con connection was lost. The issue reporter's log shows controller type 5 is unsupported and the emulator disconnects the controller; it also logs no response from a Joy-Con. The left Joy-Con's battery level is not reported. These are user reports, not maintainer-confirmed findings.
| Build | Status | GPU / CPU | FPS | Details |
|---|---|---|---|---|
| build-117 | runs with issues | Other / Apple M1 | 1 FPS | Open report |
Problems or notes: Boots and plays audio, but the image is completely black from startup; intermittent red/green block artifacts are reported. Approximately 1 FPS.
Current: build-117 (1 record); previous: build-116 (0 records).
| Build | Status | GPU / CPU | FPS | Details |
|---|---|---|---|---|
| build 115 | runs with issues | RTX 5070 / Ryzen 5700x | Not provided | Open report |
| build 116 (PGO) | runs with issues | RX 9070 XT / Not provided | 60 FPS | Open report |
Problems or notes: Grass vanishes when swinging the sword.
Problems or notes: User reports that after 9000-frame eviction of preloaded pipelines, runtime builds caused draws to be held for up to 8 seconds per 10-second window and a 19-second freeze. The user says disabling eviction locally kept the game smooth; this is a user workaround, not a confirmed fix.
| 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
Showing 51–60 of 308 reports
Known issues from Lichii sources
When fastmem could not be created, guest code ran about 1.4x slower; Kokiri Forest ran at 22.2–26.6 FPS rather than 28.5–33.8 FPS. The report attributes the slow boots to failure to allocate 14336 MiB of backing memory.
Recorded fix: Change #645 retries the section after a private commit that grows the page file; in eight back-to-back boots, all three initial failures recovered on the second attempt and none ran slowly.
Graphics fail to load in the Water Temple; a commenter describes the area as unplayable.
Recorded fix: A commenter reports resolving the issue by using a NUP containing the missing texture files, described as 23.8 GB rather than 23.3 GB.
Many Water Temple rooms are invisible, with transparent walls. A comment attributes this to a damaged texture file in the game dump; another user reports the issue was resolved by making a fresh dump with a NUP with a higher file size.
On AMD Windows proprietary drivers, older builds can lose the GPU device when gameplay or a save starts; build-83 and build-88 reports include this problem.
Recorded fix: A Windows RX 9060 XT report found the issue absent in build-93. A Windows RX 7900 XTX report also found it absent in the CI build at 18cfe85.
On AMD RADV Mesa 26.2.4, task/mesh shader use can hang the GPU and cause device loss during 3D gameplay.
Recorded fix: The reporter found that updating to Mesa RADV 26.2.6 avoided the hang on the same GPU with the same build. If using a distrobox in gamescope gaming mode, the reporter says to install the gamescope package in the container so its Vulkan WSI layer is present.
On build-95, the user reports draws held while unbuilt pipelines are being built, causing multi-second stalls, even with async shaders enabled.
The user reports that a fresh build-95 config starts with slow defaults, including High GPU accuracy, asynchronous shaders off, async presentation off, Handheld mode, 4 GB memory layout, and CPU NVDEC; the game ran at 10–15 fps with stalls up to 8.9 s and blurry/pixelated Handheld resolution.
Recorded fix: The user reports that writing the six listed settings before launch helped: gpu_accuracy=0, use_asynchronous_shaders=true, async_presentation=true, nvdec_emulation=2, memory_layout_mode=2, and use_docked_mode=1; set each key's \default= line to false as well.
User reports a black-screen stall after the first AV1 frame with async GPU emulation enabled on AMD Radeon RX 6800 XT; with async GPU emulation disabled, the game later froze during gameplay.
Users report failure to start, black screens with 0 FPS, or emulator crashes in builds 88–95, including a build-95 Linux report with an unhandled SIGSEGV and null-pointer dereference. The comments caution that the reports may have different causes.
The user reports performance remaining at 20 FPS with music glitches on macOS.
Showing 121–130 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.