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.
Donkey Kong Bananza Reported platform: Windows
Also listed as: dkb
| Build | Status | GPU / CPU | FPS | Details |
|---|---|---|---|---|
| build-65 | playable | NVIDIA GeForce RTX 4060 Laptop, 8 GB / Intel Core i7-13650HX | 10–30 FPS | Open report |
build-65 report
Statusplayable
GPUNVIDIA GeForce RTX 4060 Laptop, 8 GB
CPUIntel Core i7-13650HX
Driver32.0.16.2101
Recorded FPS10–30 FPS
Problems or notes: Not provided
Related game issues
- [Crash] (open)
- [Crash] Bananza runs at ~57 fps then aborts silently, 0xC0000409 at +0x2ecd3bd (closed)
- Black DK when finding banana (closed)
- [Crash] rx 6800xt all emulators crash on loading screen (open)
- [VBug] Build 93 finaly has no major visual errors but has poor performance 9070xt (open)
- [UIBug] Bananza — build 93 (open)
- [Crash] donkey kong and ocarina crash on AMD 6800xt (open)
- Donkey Kong Bananza (040074A01BF12000): fatal 2111-3604 right after a VP9 video reaches end of stream (nx2:vdecsvc) (closed)
- [GBug] Donkey Kong Bananza locked at 20 fps (open)
- Donkey kong bananza Crash loading (closed)
- [VBug] Shadow artifacts (closed)
- [GBug] Donkey kong bananza, black rectangle (closed)
- Donkey Kong Bananza: terrain missing (white/black) on builds 70 and 75, renders correctly on build 65 (open)
- donkey kong bananza purple screen issue (closed)
- Release note: Crashes after the continue-game loading screen.
- Release note: On build 70 (286117c), the MSVC package reportedly aborted after about 133.8 seconds of gameplay with 0xC0000409; the MinGW PGO package reportedly aborted on the intro screen with the same offset.
- Release note: DK appears all black during the cutscene when finding or collecting a banana, then returns to normal.
- Release note: User reports the game crashes when the loading screen appears on Windows 10 with an AMD RX 6000 series or older graphics card.
- Release note: The issue says FPS is worse than on most other forks.
- Release note: On build 93, FPS fluctuates approximately between 20 and 60, with frequent periods around 30 and drops to 25–28 FPS in the Dragon Layer; GameSir G7 Pro rumble can be excessive, occur without an obvious trigger, or continue longer than expected.
- Release note: User reports a crash when loading a save on AMD RX 6000 series or older under Windows 11.
- Release note: A VP9 video reaching end of stream triggers error 2111-3604 and freezes emulation; the video panel appears as a solid yellow box in stable-1.0.0.
- Release note: User reports the game is locked at 20 FPS, including menus and title screen, on Windows 11.
- Release note: Crashes when loading after the main menu on build 31.
- Release note: User reports the picture is covered with artifacts, especially on shadows.
- Release note: A black rectangle appears in what should be a mini-example guide; the reporter says it also occurs on build 70.
- Release note: On Windows builds 70 and 75, terrain/world renders solid white while the HUD and characters still render. On build 75, EDEN_NX2_RESETFIX=0 changes the ground to black with no texture or lighting.
- Release note: Purple screen after starting the game and entering it.
Compared with Previous Build
Current: build-65 (1 record); previous: nx2-build-34 (0 records).
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-65 (1 record); previous: nx2-build-34 (0 records).
Kirby Riders Reported platform: Windows 11
| Build | Status | GPU / CPU | FPS | Details |
|---|---|---|---|---|
| build-65 | runs with issues | NVIDIA RTX 30 series or older / Not provided | Not provided | Open report |
build-65 report
Statusruns with issues
GPUNVIDIA RTX 30 series or older
CPUNot provided
DriverNot provided
Recorded FPSNot provided
Problems or notes: Freezes when menu preview videos play for the selected mode. A comment says the log records the game aborting (2162-0001) during menu videos; the report was closed as stale, and no resolution was confirmed.
Related game issues
Compared with Previous Build
Current: build-65 (1 record); previous: nx2-build-34 (0 records).
Pokémon Pokopia Reported platform: Windows 11
| Build | Status | GPU / CPU | FPS | Details |
|---|---|---|---|---|
| build-65 | not booting | NVIDIA GeForce RTX 3080 / AMD Ryzen 7 5800X 8-Core Processor | Not provided | Open report |
build-65 report
Statusnot booting
GPUNVIDIA GeForce RTX 3080
CPUAMD Ryzen 7 5800X 8-Core Processor
DriverNVIDIA 616.92.0.0
Recorded FPSNot provided
Problems or notes: The user reports a constant black screen after booting and loading the game; the title indicates GPU idle at 16%.
Related game issues
- [VBug] Pokopia - Furniture most of the time invisible in Homes its shadows only (open)
- [UIBug] Pokemon Pokepia Game cover/icon is not showing in recent releases (open)
- crash or infinite loading when use windows 10 (any game) (closed)
- Pokémon Pokopia: colors washed out with a purple haze at normal camera angle, correct when camera looks straight down (closed)
- [GBug] Unable to start Pokopia. Constant Black Screen and GPU Idle at 16% (closed)
- [GBug] Pokémon Pokopia: black screen (only character outlines and UI are visible) (open)
- Release note: Furniture is invisible in homes, with only its shadows visible.
- Release note: The game cover/icon is missing among the collection covers when the emulator is opened with the game in the ROM path.
- Release note: A user reports infinite loading while loading on Windows 10.
- Release note: Washed-out, low-saturation colors with a purple/lavender haze at the normal camera angle; colors become nearly normal when looking straight down. A user reported the haze remained on build-70.
- Release note: A user reports a constant black screen after booting and loading the game on Build 65.
- Release note: Only character outlines and UI are visible after launching the game.
Compared with Previous Build
Current: build-65 (1 record); previous: nx2-build-34 (0 records).
Showing 1–4 of 4 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.