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-93 | runs with issues | 6950XT / 5800x | Not provided | Open report |
Problems or notes: Bushes render correctly at a distance but appear dead up close.
Current: build-93 (1 record); previous: build-88 (0 records).
Also listed as: green-hat kid adventure, green-hat kid game
| Build | Status | GPU / CPU | FPS | Details |
|---|---|---|---|---|
| build-93 | runs with issues | RX 6950 XT / Ryzen 7 5800X | Not provided | Open report |
| build-93 | runs with issues | Not provided / Not provided | Not provided | Open report |
| build-93 | runs with issues | AMD RX 9000 series (RX 9070 XT) / Not provided | Not provided | Open report |
Problems or notes: A user report says bushes appear correctly at a distance but show the dead variant up close.
Problems or notes: A user reported an early GPU crash without EDEN_NX2_NO_MESH=1.
Problems or notes: Walls and objects are missing/not rendered inside the Deku tree.
Current: build-93 (3 records); previous: build-88 (1 record).
Also listed as: Ocarina of Time, Zelda: Ocarina of Time, OoT, Zelda OoT, TLoZ: OoT
| Build | Status | GPU / CPU | FPS | Details |
|---|---|---|---|---|
| build-93 | runs with issues | AMD RX 9000 series / Not provided | Not provided | Open report |
| build-93 | runs with issues | RTX 3060 Ti / Intel Core i7-12700 | 19–31 FPS | Open report |
| build-93 | runs with issues | NVIDIA RTX 50 series; AMD RX 9060 XT 16gb graphics card / Not provided | Not provided | Open report |
Problems or notes: The emulator closes when loading Hyrule Market after the user exits Kokiri Forest and enters Hyrule Castle.
Problems or notes: About 31 FPS on average, down to about 19 FPS in crowded scenes, with short freezes when attacking.
Problems or notes: The user reports textures not working properly, slow frame rate, and a shield glitch. They also report that trying a '.dat' file did not work. The issue body gives conflicting GPU details.
Current: build-93 (3 records); previous: build-88 (3 records).
Also listed as: OoT
| Build | Status | GPU / CPU | FPS | Details |
|---|---|---|---|---|
| build-93 | runs with issues | AMD Radeon RX 6900 XT / AMD Ryzen 9 5900X | 24–30 FPS | Open report |
Problems or notes: Severe lighting flickering and overexposure or corrupted lighting effects; significant slowdowns in some sequences; audio desynchronization during cinematics; initial shader compilation takes considerable time. The user reports approximately 24 FPS in Kokiri Forest and approximately 30 FPS in menus and some cinematics.
Current: build-93 (1 record); previous: build-88 (0 records).
Also listed as: OoT, Ocarina of Time, OOT REMAKE
| Build | Status | GPU / CPU | FPS | Details |
|---|---|---|---|---|
| build-93 | playable | AMD Radeon RX 7900 XT / Not provided | Not provided | Open report |
| build-93 | runs with issues | AMD Radeon RX 7900 XT (Navi 31) / i9-13900K | 60 FPS | Open report |
Problems or notes: The same official build-93 AppImage ran for over five minutes in 3D without GPU resets; task/mesh pipelines and previously missing geometry rendered.
Problems or notes: The game boots and 3D runs at about 60 FPS, then the GPU hangs after roughly 55 to 100 seconds and the device is lost. EDEN_NX2_NO_MESH=1 avoids the hang but skips mesh-shader draws and leaves objects missing.
Current: build-93 (3 records); previous: build-88 (0 records).
Showing 11–20 of 35 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.