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.
Also listed as: OoT
| Build | Status | GPU / CPU | FPS | Details |
|---|---|---|---|---|
| nx2 5a50f50e0b; official PGO artifact of build-80 and local non-PGO nx2-latest | runs with issues | AMD RX 9070 XT (RDNA4, 16 GB) / Ryzen 7 5800X3D (8C/16T) | 28–35 FPS | Open report |
| local non-PGO nx2 @ 4c173bb792 with PR #345 merged (4647895acc) | playable | Radeon RX 9070 XT (RADV GFX1201) / Ryzen 7 5800X3D (8C/16T) | Not provided | Open report |
| Lichii nx2 build 93, Windows release | runs with issues | RX 9070 XT 16 GB / Ryzen 7 7800X3D (8C/16T) | 18 FPS | Open report |
| Lichii nx2-build-83 non-PGO AppImage | runs with issues | RX 9070 XT 16 GB (RADV GFX1201) / Ryzen 7 5700X (AM4, 8C/16T, non-X3D) | 20–35 FPS | Open report |
Problems or notes: On Bazzite (Fedora Atomic 45), gameplay was reported at 28-35 fps with 31-36 ms frame times despite no saturated thread. The PGO artifact crashed in dynarmic with Unhandled SIGSEGV after 2-10 minutes; the local non-PGO build was stable over several sessions.
Problems or notes: In a Deku Tree interior test, the reporter measured 16.8-18.6 ms frame times and reported the area was at the present cap. White flashes were confirmed gone there. Kokiri Village and Hyrule Field remained untested, and runtime pipeline builds caused isolated frame spikes.
Problems or notes: On Windows 11 Enterprise LTSC 2024, gameplay was reported at about 18 fps (about 56 ms per frame) with no saturated thread. New-content pipeline compilation caused first-visit hitches. A later follow-up on Frizti v3 reported about 20 fps in a busy view and about 60 fps looking at the floor; the reporter attributed the heavy-view limit to host GPU load, but that follow-up did not identify the build as build 93.
Problems or notes: On CachyOS, gameplay commonly ran at 20-35 FPS and in slow motion; menus were about 60 FPS and intro video/audio stuttered. The non-PGO AppImage rendered and reached gameplay. The PGO AppImage produced audio but no video output, and clearing the shader cache did not resolve it. The stated FPS range is the reporter's gameplay observation, not the table's median window FPS.
| Build | Status | GPU / CPU | FPS | Details |
|---|---|---|---|---|
| nx2-build-88 | runs with issues | Intel Arc B580 (BMG G21) / Ryzen 5 5600X | 8 FPS | Open report |
Problems or notes: A user reports about 8 FPS in the intro after a multi-minute shader stall on first boot. The Kokiri intro cutscene picture froze while presents continued. These are user reports.
Also listed as: OoT
| Build | Status | GPU / CPU | FPS | Details |
|---|---|---|---|---|
| b4716fc | runs with issues | RX 6700 XT / Not provided | Not provided | Open report |
| nx2 c9bdbaa | runs with issues | RX 6600 XT / Not provided | 24–48 FPS | Open report |
Problems or notes: The title screen, intro, and cinematics before the Deku Tree exterior cutscene render correctly. That cutscene is black except for a small circle around Navi where the world renders.
Problems or notes: A commenter reports 24–25 FPS at the Deku Tree web after watching the New Game intro, versus 44–46 FPS when loading the same save without the intro. With the reported storage-write extent branch, the intro-first sequence gave 44–47 FPS, gameplay about 35–48 FPS, and auto-exposure stayed correct. These are user-reported test results.
| Build | Status | GPU / CPU | FPS | Details |
|---|---|---|---|---|
| build-117 | unknown | Not provided / Not provided | Not provided | Open report |
| Lichii Build 95 | not booting | RTX 3050 6GB / i7-13620H | 0 FPS | Open report |
| Not provided | runs with issues | AMD RX 6000 series or older / Not provided | Not provided | Open report |
Problems or notes: A commenter says it runs much better for them on Linux than on Windows 11; no gameplay or FPS details are provided.
Problems or notes: User reports sound from the intro but no video. A comment says Build 116 was worse; another reports the game ran much better for them on Build 117.
Problems or notes: User reports random freezes after 5–15 minutes of play, I/O spikes up to 6GB/s, RAM use continuing to rise until out-of-memory forces the emulator to crash.
Current: build-117 (1 record); previous: build-116 (0 records).
Showing 71–80 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.