OOT
A commenter says many crashes with AMD graphics cards are related to mesh shaders.
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
98 Einträge zu Spielen und Testumgebungen sowie 275 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 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.
Also listed as: OOT Remake, OoT
| Build | Status | GPU / CPU | FPS | Details |
|---|---|---|---|---|
| 3724db9a5c | playable | RTX 4070 / i9-12900F | 16 FPS | Open report |
| b8c812b18 | runs with issues | RX 5700 / Not provided | Not provided | Open report |
| build 95 | playable | RX 7900 XTX / Ryzen 7 9800X3D | 60 FPS | Open report |
| nx2 @ 27226d2 plus two measurement-only commits | runs with issues | RTX 5060 Laptop (8 GB) / Ryzen AI 9 365 | Not provided | Open report |
| Lichii nx2 build 88 | boots | Intel Arc / Not provided | 1 FPS | Open report |
| nx2 build 88 | not booting | NVIDIA RTX 3060 / Ryzen 7 5700X | Not provided | Open report |
| Not provided | runs with issues | AMD Radeon RX 9070 XT / Not provided | Not provided | Open report |
| Build-93 MSVC 19.44.352995.0 | runs with issues | RX 9060XT 16GB / Ryzen 7 5700X | 1–30 FPS | Open report |
Problems or notes: The tester reported visible grass and a clear view of the tree through grey fog in front of the Deku Tree. The in-game counter showed 16 FPS in that view; this was a single reading.
Problems or notes: A user reported a local ClangCL build stalled with no frames (maximum 8 presents); a local MSVC build also stalled and died within a minute. In comparison, the user's build-75 release run presented frames at 32 FPS. The maintainer said the report was from an old commit and may no longer apply.
Problems or notes: Not provided
Problems or notes: In the Kokiri Forest scene, disabling per-fence Preflushable downloads or batching them by 64 fences increased GPU back-thread draws per second but broke auto-exposure, leaving the scene overexposed. Default downloads preserved correct exposure. The issue reports measurements, not a gameplay FPS result.
Problems or notes: The issue title reports about 1 FPS in the main menu and first cutscene. A comment reports about 9 FPS in the opening cutscene on an Intel Arc B580 with driver 101.9150 and Lichii v2.
Problems or notes: The user's .NUP dump remains on the Launching screen and does not start. Keys and firmware 23.0.1 were installed, but the issue persisted. The earlier launch log showed an ARM exception after unmapped memory accesses, but may have come from a separate troubleshooting launch and needs confirmation.
Problems or notes: In docked mode, a dotted cyan/magenta line appeared along mountain and sky silhouettes in Hyrule Field. The issue author reports that the line disappeared after the fix was tested.
Problems or notes: User reports occasional audio loss, frame-rate drops from 30 to 1 that recover to 30, a missing sky replaced by bright light, and a missing map. The report also lists AMD RX 9000 series as the graphics card.
Showing 61–70 of 275 reports
Known issues from Lichii sources
A commenter says many crashes with AMD graphics cards are related to mesh shaders.
In build 75 on Windows x86_64, gameplay settles at 28–29 FPS while menus and loading screens run at 53–59 FPS; the reporter characterizes the gameplay performance as CPU-bound.
Handheld mode gives a black 3D screen; Docked mode renders. A user also reports flicker/line artifacts at 2X resolution.
Recorded fix: Switching to Docked mode resolved the black 3D screen in the user's report.
A user reports frequent hangs or stalls in build 83; the trigger and duration were not isolated.
A user reports new-area shader hitches in build88.
The user reports audio delays after scenes followed by a black screen and emulator crash on Windows 11 with AMD graphics. A commenter reports a similar crash on Linux with AMD graphics.
A user reports a crash when opening the game on Linux with an AMD Radeon AI PRO R9700 (9070XT).
On an AMD Radeon RX 9070 XT, the logo, text, and UI are visible while the 3D environment remains black; audio continues and AMD driver timeouts or crashes sometimes occur.
A commenter reports AMD graphics-card crashes related to mesh shaders.
Recorded fix: A commenter says starting the Linux AppImage with EDEN_NX2_NO_MESH=1 usually fixes the problem.
A commenter reports that the game looks too bright when using the Aubepine build, making it barely playable.
Showing 261–270 of 287 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.