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: 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 |
| build-88 | runs with issues | 7800xt / Ryzen 7 5700X | Not provided | Open report |
| build-88 | not booting | AMD Radeon RX 9070 XT / AMD Ryzen 7 7800X3D | Not provided | Open report |
| build-88 | runs with issues | AMD Radeon RX 9070 XT 16GB / AMD Ryzen 7 7800X3D | Not provided | Open report |
| build-83 | runs with issues | AMD RX 9000 series / Not provided | Not provided | Open report |
| build-75 | runs with issues | AMD Radeon RX 9060 XT 16 GB (Navi 44) / AMD Ryzen 7 5700 | Not provided | Open report |
| Lichii nx2 build 75 (c9ebb5c) | runs with issues | NVIDIA GeForce RTX 4060 Laptop GPU / Intel Core i7-14650HX | Not provided | Open report |
| 286117c7e0-nx2 | not booting | NVIDIA RTX 50 series / 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.
Problems or notes: A commenter using CachyOS and Linux 7.2.9-2-cachyos reports severe audio/video delay during the initial cutscene, then black screens on both monitors and a GPU crash and reset when character control begins. They report the same issue with a fork.
Problems or notes: User reports the logo, text, and UI are visible but the 3D environment remains black; audio continues, and the AMD driver sometimes times out or crashes. The issue reportedly persists after updating or rolling back the driver and restarting.
Problems or notes: The game launches with logo, text, and UI visible, but the 3D environment remains black. Audio continues. AMD driver TDR errors or crashes are also reported.
Problems or notes: The issue reporter says the game reaches the end of the introductory cutscene, turns black while loading gameplay, then crashes with an AMD TDR. Comments report similar crashes on RX 9060 XT, RX 9070/9070 XT, and RX 7900 XTX. One user says EDEN_NX2_NO_MESH=1 stops the Windows driver crash but leaves the game black-screened or crashing while loading gameplay. Reports on Build 93 conflict: one user reports an early GPU crash without the variable, another reports playing through Kokiri Forest without crashes, and another says the issue remains and visual bugs occur during gameplay.
Problems or notes: User reports over-bright bloom/glow, dense fog, incorrect lighting on characters and terrain, and some textures decoded as garbage after entering an outdoor area. The game does not crash. Performance was reported as 33–34 ms/frame until about 80 seconds, then 89.5 ms/frame (about 11 fps) outdoors.
Problems or notes: Gameplay starts, but the 3D scene and character are black; menus and item preview can render, and HUD elements remain visible. Reported GPU shader errors include rejected native texture gather shaders and draws skipped for no pipeline.
Problems or notes: The user reported an infinite startup launch loop when booting the .NUP version. A comment corrected the GPU to RTX 3080.
Current: build-117 (2 records); previous: build-116 (0 records).
Showing 21–30 of 142 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-75 · Veröffentlicht am November 5, 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.