The Legend of Zelda: Ocarina of Time
A commenter reports that 3D rendering remains black on AMD, while the start menu and 2D UI render.
Spielekompatibilität
Spielekompatibilität des Lichii Emulators
Du hast ein bestimmtes Spiel im Sinn? Erfahre, wie es mit Lichii läuft, welche Probleme bekannt sind und welchen Build du ausprobieren kannst.
Latest recorded build
build-117
Published November 7, 2026
Ein Spiel finden
Nach kompatiblen Lichii-Spielen suchen
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
Game Compatibility Results
Recorded performance
Performance by Build and Hardware
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.
Fire Emblem Reported platform: unknown
| Build | Status | GPU / CPU | FPS | Details |
|---|---|---|---|---|
| build-65 | runs with issues | RTX 4060 (8gb) / AMD Ryzen 5 5600 6-Core Processor (3.50 GHz) | 30 FPS | Open report |
build-65 report
Statusruns with issues
GPURTX 4060 (8gb)
CPUAMD Ryzen 5 5600 6-Core Processor (3.50 GHz)
DriverNot provided
Recorded FPS30 FPS
Problems or notes: The user reported that the screen and camera began shaking during play.
Related game issues
- DLSS does not work in FE Fortune's Weave - no Game DLSS Network detection (open)
- [Crash] VK_ERROR_DEVICE_LOST, FEFW (Linux + AMD) (open)
- [GBug] Fire Emblem Fortunes Weave - FMVs Skipped/Do not play. (closed)
- Screen Shaking (Fire Emblem Fortune's Weave) (closed)
- Release note: A user reports that DLSS replacement does not detect the game's DLSS evaluation in Fire Emblem: Fortune's Weave: no Game DLSS network or NVIDIA DLSS (Streamline) line appears, while guest tensor operations run on cooperative matrices and GPU usage is high.
- Release note: On Linux with AMD graphics, Fire Emblem: Fortune's Weave can crash after a black screen with VK_ERROR_DEVICE_LOST and a GPU reset.
- Release note: A user reported that Fortunes Weave skips pre-rendered videos, including the opening cut-scene.
- Release note: Screen and camera shaking during play on build 65.
Compared with Previous Build
Current: build-70 (1 record); previous: build-65 (1 record).
Fire Emblem Reported platform: macOS
| Build | Status | GPU / CPU | FPS | Details |
|---|---|---|---|---|
| Eglantine nx2 build 34 (3140648) | runs with issues | M5 PRO 20 core gpu / M5 PRO 18 core | Not provided | Open report |
Eglantine nx2 build 34 (3140648) report
Statusruns with issues
GPUM5 PRO 20 core gpu
CPUM5 PRO 18 core
DriverNot provided
Recorded FPSNot provided
Problems or notes: The user reported that audio played and the game was interactive, but the render was completely black. A later user comment said rendering seemed fixed in Eglantine nx2 build 129 (a407703).
Related game issues
- DLSS does not work in FE Fortune's Weave - no Game DLSS Network detection (open)
- [Crash] VK_ERROR_DEVICE_LOST, FEFW (Linux + AMD) (open)
- [GBug] Fire Emblem Fortunes Weave - FMVs Skipped/Do not play. (closed)
- Screen Shaking (Fire Emblem Fortune's Weave) (closed)
- Release note: A user reports that DLSS replacement does not detect the game's DLSS evaluation in Fire Emblem: Fortune's Weave: no Game DLSS network or NVIDIA DLSS (Streamline) line appears, while guest tensor operations run on cooperative matrices and GPU usage is high.
- Release note: On Linux with AMD graphics, Fire Emblem: Fortune's Weave can crash after a black screen with VK_ERROR_DEVICE_LOST and a GPU reset.
- Release note: A user reported that Fortunes Weave skips pre-rendered videos, including the opening cut-scene.
- Release note: Screen and camera shaking during play on build 65.
Compared with Previous Build
Fire Emblem Reported platform: Windows
| Build | Status | GPU / CPU | FPS | Details |
|---|---|---|---|---|
| nx2-build-117 | runs with issues | NVIDIA GeForce RTX 4090 / AMD Ryzen 7 9800X3D | Not provided | Open report |
nx2-build-117 report
Statusruns with issues
GPUNVIDIA GeForce RTX 4090
CPUAMD Ryzen 7 9800X3D
Driver617.14
Recorded FPSNot provided
Problems or notes: A user reports entering gameplay but no Game DLSS network detection or NVIDIA DLSS evaluation; the game's tensor operations instead run on cooperative matrices, with higher GPU usage. They report this on a copy of Fire Emblem: Fortune's Weave, update version 1.0.
Related game issues
- DLSS does not work in FE Fortune's Weave - no Game DLSS Network detection (open)
- [Crash] VK_ERROR_DEVICE_LOST, FEFW (Linux + AMD) (open)
- [GBug] Fire Emblem Fortunes Weave - FMVs Skipped/Do not play. (closed)
- Screen Shaking (Fire Emblem Fortune's Weave) (closed)
- Release note: A user reports that DLSS replacement does not detect the game's DLSS evaluation in Fire Emblem: Fortune's Weave: no Game DLSS network or NVIDIA DLSS (Streamline) line appears, while guest tensor operations run on cooperative matrices and GPU usage is high.
- Release note: On Linux with AMD graphics, Fire Emblem: Fortune's Weave can crash after a black screen with VK_ERROR_DEVICE_LOST and a GPU reset.
- Release note: A user reported that Fortunes Weave skips pre-rendered videos, including the opening cut-scene.
- Release note: Screen and camera shaking during play on build 65.
Compared with Previous Build
Fire Emblem Reported platform: Linux
| Build | Status | GPU / CPU | FPS | Details |
|---|---|---|---|---|
| build 93 (09b78bd) | not booting | AMD RX 9000 series; RX9070XT / R5 3600 | Not provided | Open report |
build 93 (09b78bd) report
Statusnot booting
GPUAMD RX 9000 series; RX9070XT
CPUR5 3600
DriverNot provided
Recorded FPSNot provided
Problems or notes: Fire Emblem: Fortune's Weave shows a black screen and then crashes with VK_ERROR_DEVICE_LOST. The issue reporter says it does not happen on Windows on the same system. A commenter reports the crash persists in Lichii build 95.
Related game issues
- DLSS does not work in FE Fortune's Weave - no Game DLSS Network detection (open)
- [Crash] VK_ERROR_DEVICE_LOST, FEFW (Linux + AMD) (open)
- [GBug] Fire Emblem Fortunes Weave - FMVs Skipped/Do not play. (closed)
- Screen Shaking (Fire Emblem Fortune's Weave) (closed)
- Release note: A user reports that DLSS replacement does not detect the game's DLSS evaluation in Fire Emblem: Fortune's Weave: no Game DLSS network or NVIDIA DLSS (Streamline) line appears, while guest tensor operations run on cooperative matrices and GPU usage is high.
- Release note: On Linux with AMD graphics, Fire Emblem: Fortune's Weave can crash after a black screen with VK_ERROR_DEVICE_LOST and a GPU reset.
- Release note: A user reported that Fortunes Weave skips pre-rendered videos, including the opening cut-scene.
- Release note: Screen and camera shaking during play on build 65.
Compared with Previous Build
green-hat game Reported platform: Windows 10
| Build | Status | GPU / CPU | FPS | Details |
|---|---|---|---|---|
| build-93 | runs with issues | AMD RX 6000 series or older / Not provided | Not provided | Open report |
build-93 report
Statusruns with issues
GPUAMD RX 6000 series or older
CPUNot provided
DriverNot provided
Recorded FPSNot provided
Problems or notes: ZL input is not detected during the shield tutorial, leaving it stuck in a loop. Rebinding ZL to L or using the keyboard does not resolve the issue.
Related game issues
Compared with Previous Build
Current: build-93 (1 record); previous: build-88 (0 records).
green-hat kid adventure Reported platform: Linux (Debian)
| Build | Status | GPU / CPU | FPS | Details |
|---|---|---|---|---|
| c0a03141a4-nx2 | runs with issues | NVIDIA GeForce RTX 4060 Ti / Intel(R) Core(TM) i5-4690K CPU @ 3.50GHz | 20 FPS | Open report |
c0a03141a4-nx2 report
Statusruns with issues
GPUNVIDIA GeForce RTX 4060 Ti
CPUIntel(R) Core(TM) i5-4690K CPU @ 3.50GHz
DriverNot provided
Recorded FPS20 FPS
Problems or notes: The user reports black 3D content in docked mode while the GUI overlay and main menu render. Handheld mode renders the game. The user reports approximately 20 FPS after reboot, the same as the last build, and says this is lower than build 88.
Related game issues
Compared with Previous Build
Hyrule Warriors Reported platform: Windows 11
| Build | Status | GPU / CPU | FPS | Details |
|---|---|---|---|---|
| build-88 | runs with issues | nvidia rtx 40 series / Not provided | Not provided | Open report |
| build 75 (c9ebb5c) | runs with issues | AMD RX 9000 series; RX 9060 XT 16GB / Not provided | Not provided | Open report |
| 80 | runs with issues | NVIDIA RTX 40 series / Not provided | Not provided | Open report |
| Lichii Development Build | nx2-build-95 | runs with issues | AMD Radeon RX 6600 / AMD Ryzen 5 5600X | Not provided | Open report |
build-88 report
Statusruns with issues
GPUnvidia rtx 40 series
CPUNot provided
DriverNot provided
Recorded FPSNot provided
Problems or notes: A commenter reports the same bug at the start.
build 75 (c9ebb5c) report
Statusruns with issues
GPUAMD RX 9000 series; RX 9060 XT 16GB
CPUNot provided
DriverNot provided
Recorded FPSNot provided
Problems or notes: An on-screen error appears after the cinematic and remains visible, blocking the view.
80 report
Statusruns with issues
GPUNVIDIA RTX 40 series
CPUNot provided
DriverNot provided
Recorded FPSNot provided
Problems or notes: In stages past the first one, the screen is black while the UI remains visible; when paused, the world renders in the background. The reporter says it worked on older builds of eglantine.
Lichii Development Build | nx2-build-95 report
Statusruns with issues
GPUAMD Radeon RX 6600
CPUAMD Ryzen 5 5600X
DriverAMD proprietary driver 2.0.353, Vulkan 1.4.315
Recorded FPSNot provided
Problems or notes: User reports a crash after a few minutes when moving between areas or into a large open field. The log shows images exceeding the VRAM memory budget, use of an unbacked sparse image, and an assertion at texture_cache.h:2710: assert false && "Unimplemented!".
Related game issues
- [Crash] Memory exhaustion, then an unimplemented path (closed)
- [VBug] (closed)
- [VBug] (closed)
- Release note: On the reported Windows 11 setup with an AMD Radeon RX 6600, Vulkan logs VRAM memory-budget warnings and an unimplemented-path assertion before a crash after a few minutes of gameplay.
- Release note: Black screen with visible UI during gameplay in stages past the first one, while the world renders in the background when paused.
- Release note: An on-screen error appears after the cinematic and remains visible, blocking the view.
Compared with Previous Build
Current: build-88 (1 record); previous: build-83 (0 records).
Showing 21–30 of 308 reports
Known issues from Lichii sources
Known Game Issues
Ocarina of Time
A user reported that local ClangCL and MSVC builds stalled with no frames, while the compared build-75 release presented frames. The cause was not determined; a maintainer noted the report came from an old commit and may no longer happen.
The Legend of Zelda: Ocarina of Time
On the reported Windows 11 system with a Radeon RX 9070, the world rendered almost entirely black after entering gameplay, with only lit areas and some white shapes visible; multi-second stalls were also reported during pipeline building and ASTC decodes.
Zelda Ocarine of time
Black screen or missing video during the intro or gameplay, sometimes with audio or UI still visible; user reports also mention low FPS and graphics artifacts.
Recorded fix: A user reports shared MSVC-build settings resolved the black screen for them; another reports switching from handheld to docked mode resolved it on their setup. These are user-reported steps, not maintainer-confirmed fixes.
Zelda Ocarine of time
The intro video fails with a black screen; a user log reports that FFmpeg has no decoder for video/av1.
Star Fox
A user reports the emulator closes about a minute after gameplay begins on Build 75 with an NVIDIA RTX 50 series GPU and Windows 11.
The Legend of Zelda: Ocarina of Time
On nx2-build-75, AV1 video streams fail to decode and the game remains on a black screen despite booting and presenting frames.
The Legend of Zelda: Ocarina of Time
On AMD/RADV under Linux, AV1 intro-cutscene video renders as a solid green area while audio and subtitles work.
The Legend of Zelda: Ocarina of Time
On Windows with AMD hardware, the emulator hangs indefinitely when the AV1 intro cutscene starts; the video layer is black while audio and subtitles work.
Other / not listed
A user reports that the linux-aarch64 PGO AppImage fails ZBIC NSO decompression for a game whose NSOs use ZBIC, leaving it stuck without presenting a frame; the same-commit non-PGO AppImage does not show the decompression assertions.
Showing 231–240 of 361 issues
Aktuelle Release-Hinweise
Kompatibilitätsänderungen in den neuesten Builds
Build build-117 · Ocarina of Time
Fixed a crash during shader building on Windows drivers for RX 6000 (RDNA2), RX 5000 (RDNA1), Vega, and Polaris cards. The faster matrix path now runs only on RDNA3 and newer.
Build build-116 · Zelda: Ocarina of Time
Ocarina of Time is described as very stable; foliage and Hyrule Field grass rendering are fixed, and many users get 60+ fps.
Build build-116 · Zelda: Ocarina of Time
NVIDIA DLSS Super Resolution can replace the game's own upscaler on RTX cards; the setting is experimental.
Build build-116 · Zelda: Ocarina of Time
A new option turns off the game's sharpening anti-aliasing; the default Game setting behaves as before, and DLSS takes priority if both are enabled.
Build build-116 · Mario Tennis Fever
The game runs fully at 60 fps, and texture glitches are fixed.
Den passenden Build finden
Welchen Build soll ich verwenden?
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
Häufige Fragen zur Spielekompatibilität
Wie teile ich ein Spiel mit diesen Filtern?
Setze die Filter für Spiel, Status, GPU und Build und kopiere anschließend die Seitenadresse. Ein direkter Link zum Spiel öffnet dessen Berichtskarte.
Was kann ich bei einem schwarzen Bildschirm versuchen?
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.
Warum kann dieselbe GPU unterschiedliche Ergebnisse liefern?
Treiberversion, Grafikeinstellungen, CPU-Auslastung und die getestete Spielszene können das Ergebnis beeinflussen. Vergleiche diese Details, bevor du deine Konfiguration änderst.
Wo kann ich ein fehlendes Testergebnis melden?
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.