History view: these notes belong to nx2-build31-20261101, not the latest release. Return to build-88.
Inside nx2-build31-20261101
1 general build change and 0 game-specific updates. Explore the highlights below or jump to the side-by-side comparison.
Build change
Includes build 30's readback/rendering fixes plus indexed JIT invalidation, contiguous-page bookkeeping, corrected mixed-process protection ownership, parallel native driver compilation, and a cached indirect-reset-program lookup.
Before / after: Build 30's readback/rendering fixes. → Adds indexed JIT invalidation, contiguous-page bookkeeping, corrected mixed-process protection ownership, parallel native driver compilation, and a cached indirect-reset-program lookup.
30 → nx2-build31-20261101
Build selectors
Compare Two Builds
Choose two releases to read their game changes, package notes, and official download options side by side.
Selected · nx2-build31-20261101
Eglantine nx2 build 31
November 1, 2026
Summary
Windows x86_64 GUI build 31 is the exact Clang Release executable tested by the owner, who reported it works well. The other listed platform packages are CI-built and have not received the owner's gameplay testing.
Changes (up to 5)
Includes build 30's readback/rendering fixes plus indexed JIT invalidation, contiguous-page bookkeeping, corrected mixed-process protection ownership, parallel native driver compilation, and a cached indirect-reset-program lookup.
Build notes (up to 3)
Experimental software; compilation and native range/bitmap and mixed-ASID probes passed, but the expanded core test selection failed and baseline comparison and remaining dynarmic checks were incomplete.
Additional Linux x86_64, Linux PGO, macOS ARM64, and Windows PGO packages are CI-built and have not received the owner's gameplay testing. The new local video/AES fixes are not included in those packages.
PGO uses Eden's published profile; no FPS improvement is claimed.
Choose both tags and press Compare builds, then copy the address bar. The link preserves both selections.
Do I need to install every build in between?
The download history lets you choose a specific release directly. Read its package notes for any version-specific installation steps.
What should I keep before trying an update?
Keep the installer or archive for your working build, and back up saves and configuration. That gives you a practical route back if your game regresses.
Where can I check the source commit?
Follow a build's official GitHub release link to inspect its tag and associated source commit.
