Pokémon Pokopia
A user reports a constant black screen after booting and loading the game on Build 65.
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
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
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.
Star Fox Reported platform: Linux AppImage (PGO)
| Build | Status | GPU / CPU | FPS | Details |
|---|---|---|---|---|
| Lichii nx2 build 70 (`286117c`) | runs with issues | integrated RDNA2, RADV, reports as `GFX1013` / AMD BC-250 (Oberon APU), 7 cores / 14 threads, AVX2 + FMA | Not provided | Open report |
Lichii nx2 build 70 (`286117c`) report
Statusruns with issues
GPUintegrated RDNA2, RADV, reports as `GFX1013`
CPUAMD BC-250 (Oberon APU), 7 cores / 14 threads, AVX2 + FMA
DriverNot provided
Recorded FPSNot provided
Problems or notes: User reports heavily distorted speech, music, and effects (“robot voice”). Comments clarify that the approximately 0.7032 accepted/copied ratio reflects retries, not audio loss at that point; they discuss possible timebase or host-drain causes without confirming which applies. The user also says build 75 does not reach gameplay, instead hitting a guest Userspace PANIC (`debug_buffer_err_code=40299`) about 29 seconds in and presenting a static black frame at 59.9 FPS.
Related game issues
- [GBug] StarFox: nx2_sysmix accepts a constant 70.32% of mixer output, so audio plays as "robot voice" (open)
- [Crash] StarFox, Device loss occurred! (closed)
- [Crash] Starfox is crashing right before the training mission begins. I got it to pass one time havent been able to get it work again. (closed)
- Release note: On RTX 50-series GPUs, the GPU device can still be lost after a scene change.
- Release note: Gameplay is capped at about 30 fps, even though the game asks for 60.
- Release note: On RTX 50-series GPUs (5070 Ti, 5090), the GPU device can be lost shortly after a scene change.
- Release note: User reports heavily distorted speech, music, and effects (“robot voice”) on build 70. Comments clarify that the approximately 0.7032 accepted/copied ratio reflects retries rather than lost samples; possible causes discussed include emulated time running ahead of wall time or slow host audio draining, but the cause is not confirmed.
- Release note: 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.
- Release note: User reports crashes before the training mission begins; another user reports crashes during the campaign after skipping training.
Compared with Previous Build
Star Fox Reported platform: unknown
Also listed as: StarFox
| Build | Status | GPU / CPU | FPS | Details |
|---|---|---|---|---|
| build-75 | runs with issues | Not provided / Not provided | 60 FPS | Open report |
| build-70 | runs with issues | Not provided / Not provided | ?–30 FPS | Open report |
| 19.44 (11-4-2026) | runs with issues | NVIDIA RTX 50 series / Not provided | Not provided | Open report |
| Lichii nx2 build 75 (c9ebb5c) | runs with issues | NVIDIA RTX 40 series / Not provided | Not provided | Open report |
| Build - 75 | runs with issues | NVIDIA RTX 50 series / Not provided | Not provided | Open report |
build-75 report
Statusruns with issues
GPUNot provided
CPUNot provided
DriverNot provided
Recorded FPS60 FPS
Problems or notes: On RTX 50-series GPUs, the GPU device can be lost after a scene change.
build-70 report
Statusruns with issues
GPUNot provided
CPUNot provided
DriverNot provided
Recorded FPS?–30 FPS
Problems or notes: Gameplay is capped at about 30 fps despite the game asking for 60. On RTX 50-series GPUs (5070 Ti, 5090), the GPU device can be lost shortly after a scene change.
19.44 (11-4-2026) report
Statusruns with issues
GPUNVIDIA RTX 50 series
CPUNot provided
DriverNot provided
Recorded FPSNot provided
Problems or notes: User reports crashes before the training mission begins; it passed once. A separate user reports crashes during the campaign after skipping training.
Lichii nx2 build 75 (c9ebb5c) report
Statusruns with issues
GPUNVIDIA RTX 40 series
CPUNot provided
DriverNot provided
Recorded FPSNot provided
Problems or notes: User reports repeated Unmapped Write64 errors and a crash when closing the game; audio popping is suspected but not confirmed.
Build - 75 report
Statusruns with issues
GPUNVIDIA RTX 50 series
CPUNot provided
DriverNot provided
Recorded FPSNot provided
Problems or notes: User reports that the emulator closes about a minute after gameplay begins.
Related game issues
- [GBug] StarFox: nx2_sysmix accepts a constant 70.32% of mixer output, so audio plays as "robot voice" (open)
- [Crash] StarFox, Device loss occurred! (closed)
- [GBug] Starfox - Unmapped write64 error spam in console (closed)
- [Crash] Starfox is crashing right before the training mission begins. I got it to pass one time havent been able to get it work again. (closed)
- Release note: On RTX 50-series GPUs, the GPU device can still be lost after a scene change.
- Release note: Gameplay is capped at about 30 fps, even though the game asks for 60.
- Release note: On RTX 50-series GPUs (5070 Ti, 5090), the GPU device can be lost shortly after a scene change.
- Release note: User reports heavily distorted speech, music, and effects (“robot voice”) on build 70. Comments clarify that the approximately 0.7032 accepted/copied ratio reflects retries rather than lost samples; possible causes discussed include emulated time running ahead of wall time or slow host audio draining, but the cause is not confirmed.
- Release note: 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.
- Release note: Repeated Unmapped Write64 errors while the game is running, possible audio popping, and an emulation crash when closing the game, as reported by a user.
- Release note: User reports crashes before the training mission begins; another user reports crashes during the campaign after skipping training.
Compared with Previous Build
Current: build-75 (1 record); previous: build-70 (1 record).
Showing 1–6 of 6 reports
Known issues from Lichii sources
Known Game Issues
Donkey Kong Bananza
A black rectangle appears in what should be a mini-example guide; the reporter says it also occurs on build 70.
Kirby Riders
Freezes or aborts while menu preview videos play.
Splatoon Raiders
The reporter says they cannot swim in ink during the tutorial on MacOS.
Fire Emblem
Screen and camera shaking during play on build 65.
Mario Kart World
A user reported rapidly increasing VRAM usage after starting the game, followed by low framerate.
Mario Kart World
Crashes while loading before the main menu; user comments also report session or emulator crashes.
The Legend of Zelda: Ocarina of Time
User reports fluctuating performance of approximately 10–30 FPS, bushes disappearing when approached or changing shape, and intermittent lighting and shading glitches.
OOT
Black screens during the introductory cinematic, GDT sequence, or gameplay; reports include intermittent black flashes and audio playing ahead of video.
OOT
Docked mode may show a black screen except for captions or HUD, while handheld mode may appear excessively bright, low resolution, or vaseline-like.
Showing 251–260 of 287 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?
build-75 · Veröffentlicht am November 5, 2026
Star Fox
- runs with issues · GPU Nicht angegeben · CPU Nicht angegeben · Treiber Nicht angegeben
12 veröffentlichte Downloaddateien für diesen Build.
build-70 · Veröffentlicht am November 4, 2026
Star Fox
- runs with issues · GPU Nicht angegeben · CPU Nicht angegeben · Treiber Nicht angegeben
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
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.