Other / not listed
Frequent freezing is reported while running at about 30 FPS on Windows 10 with build 117.
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.
| Build | Status | GPU / CPU | FPS | Details |
|---|---|---|---|---|
| build-116 | runs with issues | NVIDIA RTX 30 series or older; 306012gb / 3600x | Not provided | Open report |
Problems or notes: The user reports broken frame generation, general lag and stuttering, a 10–12 FPS drop compared with build 93, and texture-cache data being overwritten. They say the game became unplayable for them.
Current: build-116 (1 record); previous: build-94 (0 records).
| Build | Status | GPU / CPU | FPS | Details |
|---|---|---|---|---|
| build-117 | runs with issues | 1080ti / i7 7700k | 30 FPS | Open report |
Problems or notes: Frequent freezing. A commenter attributes it to shaders and suggests rebuilding them, but another user reports that installing a 30k shader pack and deleting shaders did not help.
Current: build-117 (1 record); previous: build-116 (0 records).
Also listed as: green-hat kid adventure, green-hat kid game
| Build | Status | GPU / CPU | FPS | Details |
|---|---|---|---|---|
| build-93 | runs with issues | RX 6950 XT / Ryzen 7 5800X | Not provided | Open report |
| build-93 | runs with issues | Not provided / Not provided | Not provided | Open report |
| build-93 | runs with issues | AMD RX 9000 series (RX 9070 XT) / Not provided | Not provided | Open report |
| build-88 | runs with issues | RX 9070 XT / Not provided | Not provided | Open report |
| build-83 | unknown | RX 9070 XT / Not provided | Not provided | Open report |
| 557d694581 | runs with issues | RTX 50 series / Not provided | Not provided | Open report |
| 5a50f50 | runs with issues | AMD RX 7000 series / Not provided | Not provided | Open report |
| 55532f2 | runs with issues | AMD RX 7000 / Not provided | Not provided | Open report |
Problems or notes: A user report says bushes appear correctly at a distance but show the dead variant up close.
Problems or notes: A user reported an early GPU crash without EDEN_NX2_NO_MESH=1.
Problems or notes: Walls and objects are missing/not rendered inside the Deku tree.
Problems or notes: One user reported GPU/display blackout and VK_ERROR_DEVICE_LOST when entering gameplay without EDEN_NX2_NO_MESH=1; with that option, gameplay ran for at least five minutes. The report does not establish long-term stability or the precise failing shader or command.
Problems or notes: A user reported early crashes without EDEN_NX2_NO_MESH=1 and no early crashes with it across more than one game and emulator; this is a user testimonial, not a verified result.
Problems or notes: A merged report says plants in Hyrule Castle render as dead up close, from just past the gate through the garden near Zelda.
Problems or notes: The game crashed multiple times in Deku Tree; afterward it would not boot and reportedly became stuck during shader compilation. A commenter reports the problem only with RADV; testing with a second NVIDIA GPU made the game run, but too slowly to be playable.
Problems or notes: A user reported intermittent process SIGSEGV crashes after approximately 2–30 minutes, with and without EDEN_NX2_NO_MESH=1 and after suggested settings changes. No full-screen freeze was reported. The user later said the crash had not recurred since later commits.
Current: build-93 (3 records); previous: build-88 (1 record).
Showing 111–120 of 308 reports
Known issues from Lichii sources
Frequent freezing is reported while running at about 30 FPS on Windows 10 with build 117.
The user reports very low FPS and rendering artifacts when running on an Intel Arc GPU under Windows 11 with Vulkan.
On an AYN Thor with Adreno 740 and Turnip, large native compute shaders cause pipeline compilation to consume substantial memory and pin Vulkan pipeline-builder threads; reports include black output, GPU device loss, or out-of-memory termination.
On ARM hosts using NCE, the built-in Dynamic FPS by Dark and Max Resolution patches together were reported to trigger an early SIGILL on builds 88 and 94.
Recorded fix: Disable both Dynamic FPS by Dark (built-in) and Max Resolution (built-in) in the game's Add-Ons.
Long shader and pipeline hitches while exploring; the user also reports texture flashes or freezes when new pipelines compile.
A user reports constant CPU-side coil whine while playing on a laptop.
Missing textures were reported on build 95; stuttering and long loading times were reported on build 117.
On build-117, the user reports nonstop freezes or frame drops during gameplay. They report occasional hangs on older builds.
A system-wide GPU error and crash after playing for a few minutes, reported with AMD RX 6000 series or older on Linux in Build 117 PGO.
Crashes during boot at an unimplemented nx2:vi2 function 201; the report also mentions a later unimplemented IGeneralService function 101 assert.
Showing 81–90 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
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.