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, Ocarina of Time
| Build | Status | GPU / CPU | FPS | Details |
|---|---|---|---|---|
| Not provided | not booting | 6700 xt / Not provided | Not provided | Open report |
| Not provided | runs with issues | AMD Radeon RX 6900 XT 16GB / Intel Xeon E5-2697v3 | Not provided | Open report |
| nx2-build-88 | runs with issues | RX 7800 XT / Not provided | Not provided | Open report |
| Not provided | not booting | RX 9060 XT 16gb / Not provided | Not provided | Open report |
| build-95 (the release tagged `build-94`) | runs with issues | RX 5700 / Not provided | 14–24 FPS | Open report |
| build-117 (PGO) | playable | RX 9070 XT / Ryzen 7 9800X3D | Not provided | Open report |
Problems or notes: A commenter reports an instant crash after trying the EDEN_NX2_NO_MESH=1 workaround.
Problems or notes: On nx2-build-117, the user reports that EDEN_NX2_NO_MESH=1 avoided device loss for a session of about 176 seconds. The variable skipped 27 draws; the user noticed no obvious visual issues but could not rule out missing visuals.
Problems or notes: Disabling mesh draws with EDEN_NX2_NO_MESH=1 did not prevent the device-loss crash on this configuration; it occurred after the intro cutscene.
Problems or notes: Commenters report crashes when attempting the EDEN_NX2_NO_MESH=1 workaround; one says the screen goes black after the intro and the emulator closes. Game version 1.1.1 is stated by another commenter with a separate instant-crash report.
Problems or notes: Short session in Kokiri Forest and the Deku Tree rendered correctly, with no crash, fence timeout, device loss, or compute rejections. Reported 14 FPS in Kokiri Forest and 22–24 FPS indoors; the commenter says outdoor performance was identical to build 93.
Problems or notes: Commenter reports about 70 minutes of play through the Deku Tree and Gohma with zero blackouts and no Native compute shader rejected (per-tap gather) error, using game version 2.0.0 loaded from a .nup. The same user says blackouts and the log error occurred with extracted base-game version 1.0.0.
Current: build-93 (4 records); previous: build-88 (1 record).
| Build | Status | GPU / CPU | FPS | Details |
|---|---|---|---|---|
| build-93 | runs with issues | RX 9060 XT 16 GB / i7-9700K | 19–36 FPS | Open report |
Problems or notes: A user reports that frame_gen and game_dlss_network enabled caused a near-white presented frame; setting both to false produced a correct image. White flashes were associated with async_presentation=true; async_presentation=false reduced white pixels in a 40-frame capture to 0.2% but lowered performance to about 19-25 FPS in a heavy Kokiri scene. The approximately 36 FPS result required async presentation, which flashed.
Current: build-93 (1 record); previous: build-88 (0 records).
| Build | Status | GPU / CPU | FPS | Details |
|---|---|---|---|---|
| nx2-build-75 [PGO] | not booting | AMD Radeon RX 6650 XT (RDNA2) / Intel Core i5-10400F | Not provided | Open report |
| nx2-build-83 | runs with issues | Radeon RX 6800 / Not provided | 43–47 FPS | Open report |
Problems or notes: The render area stays black after boot in both handheld and docked modes. The reporter also tried build 75 and pre-release #80; the black screen persisted. The associated comment describes the game ID as 0400486024DEC000.
Problems or notes: The reporter says the game renders correctly in a screen capture, including the title screen, logo, and menu, but the presented display is solid green. They report about 43 fps from presents and a 47 fps OSD in the capture.
| Build | Status | GPU / CPU | FPS | Details |
|---|---|---|---|---|
| build-83 | runs with issues | RX 9060 XT 16 GB / Not provided | Not provided | Open report |
Problems or notes: The reporter says the black-screen issue is gone and the game reaches gameplay, but the device is lost at gameplay start with VK_ERROR_DEVICE_LOST, followed by a crash.
Current: build-83 (1 record); previous: build-75 (1 record).
Showing 161–170 of 194 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-117 · Veröffentlicht am November 7, 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.