Repository navigation
Eglantine nx2 build 120 (b8d2c08)
Pre-releaseWhat's new in this build
This is build 120 of nx2 (b8d2c08). It is build 110 plus the .nup layout fix — a single commit on top of f6d03bc, the same change build 117 shipped. It does not contain the nx2-experimental batch: build 117 was published from a merge that pulled that line into nx2, nx2 no longer contains that merge, and this build is the .nup fix committed directly to the branch instead.
.nup containers written in the NUP v1 layout now open
The .nup loader added in build 110 described the container's records with their fields in the wrong order: the package record read meta_offset and meta_size four bytes early, and the file record kept a stray reserved word after the name and put the size, the two extent fields and the SHA-256 in the wrong slots. A container written in the aligned NUP v1 layout was therefore misread — the file table came back with wrong sizes and offsets, and the per-package metadata that supplies the title name, icon and display version was taken from the wrong bytes.
The record layouts now match NUP v1 exactly, and offsetof assertions pin every field, so a later change to the structs fails to compile instead of silently shifting the format again.
Everything else about .nup is as build 110 described it: base program with the newest update inside the container layered over it, name/icon/version read from the container, add-on content recognised but not mounted, and a malformed container rejected with a message instead of a crash.
Coming from build 117?
Then this build is a step back, and the download is small for a reason: the nx2-experimental work build 117 carried is not in it — task and mesh shaders (and EDEN_NX2_NO_MESH), the AMD VRAM margins, Mario Kart World's command-list snapshot, Splatoon Raiders' fog, and the nx2:camera log fix. If you want that batch, stay on 117 or take an nx2-experimental build (122), which has it plus the same .nup fix.
Coming from build 110, the .nup fix above is the only change.
How it works, for the technically curious
PackageRecordis 0x40 bytes inside#pragma pack(push, 1):title_id0x00,root_dir0x08,exefs_dir0x0C,romfs_dir0x10,version0x14,kind0x18,flags0x19,reserved0x1A,reserved20x1C,meta_offset0x20,meta_size0x28,reserved30x2C. The old struct putmeta_offsetat 0x1C andmeta_sizeat 0x24.FileRecordis 0x50 bytes packed: name 0x00/0x04,size0x08,extent_offset0x10,extent_size0x18,sha2560x20,codec0x40,codec_flags0x41,reserved20x42,reserved3(12 bytes) 0x44. The old struct had a strayreservedword at 0x08,sizeat 0x0C, the hash at 0x14 and the extents at 0x34/0x3C.- Both structs are packed, so the
static_assert(sizeof(...))checks that already existed could not catch the field reordering — the sizes came out the same. The newstatic_assert(offsetof(...))lines can.
Automatic build of nx2 at b8d2c08.
Windows: extract the zip and run eglantine.exe, or eden-cli.exe from a terminal.
Linux (AppImage): make it executable (chmod +x) and run it; it bundles its libraries and needs glibc 2.39 or newer (Ubuntu 24.04, Fedora 40, Debian 13, Arch).
Linux (tar.gz): extract it and run ./eglantine or ./eden-cli; it uses your system libraries, so Qt 6 and the usual libraries must be installed.
macOS: Apple Silicon and macOS 15 or newer. Unzip and move eglantine.app to Applications; eden-cli is inside it, in Contents/MacOS. The app is not notarized, so the first time right-click it and choose Open (or run xattr -dr com.apple.quarantine eglantine.app).
The -pgo builds are the same programs compiled with profile-guided optimization (clang plus Eden's profile); prefer them when your CPU supports it. The Windows PGO build is a MinGW build, so it carries its own DLLs and needs no Visual C++ redistributable.