Für build-83 sind keine allgemeinen Build-Änderungen aufgeführt.
Weitere Details findest du in den vollständigen Release-Hinweisen auf GitHub.
Build-Auswahl
Zwei Builds vergleichen
Wähle zwei Releases aus und vergleiche Änderungen an Spielen, Pakethinweise und offizielle Downloadmöglichkeiten.
Ausgewählt · build-83
Lichii nx2 build 83 (5a50f50)
November 6, 2026
Zusammenfassung
build-83 includes Ocarina of Time graphics and rendering fixes, performance and stability improvements, and updated setup guidance for Linux, Windows, and macOS.
Linux packages include standard and PGO builds for x86_64 and aarch64. The PGO builds are recommended; they use profile-guided optimization.
The Linux AppImage is self-contained and requires glibc 2.39 or newer. The Linux tar.gz uses system libraries, including Qt 6 and the usual libraries.
The Windows standard MSVC zip is suggested if graphical issues occur on other builds. The PGO zip is built with MinGW clang, bundles its own DLLs, and does not require the Visual C++ redistributable.
build-75 adds game fixes, an in-app updater that selects downloads for the user's platform, and expanded optional frame-dump diagnostics.
Änderungen (bis zu 5)
Zelda: Ocarina of Time: Now boots, completes the intro, and enters gameplay. A white screen was resolved after about 80 shaders became translatable; a 64-bit wait-on-address abort was also addressed.
Star Fox: Gameplay performance increased from 30 fps to 60 fps.
The in-app updater checks Lichii's GitHub releases and selects the download for the user's platform.
Build-Hinweise (bis zu 3)
Linux packages are available as AppImage and tar.gz for x86_64 and aarch64. AppImage requires glibc 2.39 or newer; tar.gz uses system libraries, including Qt 6 and the usual libraries.
Windows offers an MSVC zip and a PGO zip. The MSVC build is the only Windows build with NVIDIA DLSS and is also recommended if graphical issues occur on other builds. The MinGW clang PGO zip bundles its own DLLs and does not require the Visual C++ redistributable; it does not include NVIDIA DLSS.
The macOS arm64 package requires macOS 15 or newer and is not notarized.
Vergleiche die Pakethinweise direkt nebeneinander. Unten findest du Vorher-nachher-Hinweise zu den Änderungen zwischen build-83 und build-75.
Konkrete Änderungen für build-83 ↔ build-75
Ocarina of Time · build-75 → build-83
Vorher / nachher: Missing vegetation and incorrect material data; affected lighting and colours; a glowing doorway; one-frame white flashes; and on AMD, shaders could produce a black 3D scene. → Additional shader pointers and storage-buffer bindings, corrected buffer tracking and mesh-shader register handling, fixed occlusion-query and nested-return handling, and added the Max Resolution add-on and frame-ahead presentation tuning.
Quelle: build-83
All releases
Lichii Release History
build-10
November 1, 2026 · Commit d8a9528ba227e3618f8c050706dcf79cabd303f6 · 5 assets
Fixed missing vegetation, incorrect materials and lighting, a glowing doorway, one-frame white flashes, and an AMD black 3D scene. Added Max Resolution (built-in), enabled by default for the supported game build, and Ocarina-specific frame-ahead presentation tuning.
A user reports missing textures and buggy visuals after booting, occasional startup crashes, and crashes when playing the Grand Prix race on build-83 with Intel integrated graphics on Windows 11.
On Windows build-83, shutdown can hang at “Closing software…” after gameplay. Some sessions completed shutdown successfully; the cause is undetermined.
Wähle beide Tags aus, klicke auf „Builds vergleichen“ und kopiere die Adresse aus dem Browser. Der Link speichert beide Auswahlen.
Muss ich alle Builds dazwischen installieren?
Im Downloadverlauf kannst du einen bestimmten Release direkt auswählen. In den Pakethinweisen stehen die Installationsschritte für diese Version.
Was sollte ich vor einem Update sichern?
Behalte den Installer oder das Archiv deines funktionierenden Builds und sichere deine Spielstände und Einstellungen. So kannst du zurückwechseln, falls dein Spiel danach schlechter läuft.
Wo finde ich den zugehörigen Quellcode-Commit?
Öffne den offiziellen GitHub-Release des Builds. Dort findest du den Tag und den zugehörigen Quellcode-Commit.
