Multi Beta 5.4: Windows release, migration & save limits

What is available now?

Multi Beta 5.4 is now a published Windows x64 prerelease. hjqcan/LASRecomp is an enhanced fork of peiikai/LASRecomp, maintained as Multi on the multi branch. The repository and default main branch names are unchanged; main mirrors upstream. It is not SwitchWaker, nxnative or D2R Mobile, and is not a release of Joe’s general-purpose tool.

The multi-beta5.4 release was published on 18 October 2026 at 17:33:21 UTC, with a Windows ZIP and SHA-256 file. Its tag points to 6a1dd81, the source previously reviewed as unreleased. The 19:05 UTC review verified release metadata and pinned documentation. SwitchToAny has not downloaded, audited or run the package, or independently checked the ZIP’s bytes against the listed checksum.

The publisher says the package contains no game assets, keys or saves. That is the publisher’s statement, not a site audit. Your own exact-version game inputs and local compilation are still required; this is not a ready-to-play game download.

Already using Beta 5.3 or an older client? The old updater cannot discover multi-beta* tags. Use the fork’s release page for a one-time manual ZIP update. Exit the old program, update the program files from the ZIP’s Multi folder, and preserve game directories, saves, seeds, mods and settings. The executable remains lasrecomp.exe; the new client can check later Multi releases. Complete any requested native-library rebuild before playing.

Which games and PC requirements apply?

The published Beta 5.4 Windows route supports:

• Animal Crossing: New Horizons: 1.0.0 or 3.0.1 with its matching update. Other ACNH versions and DLC are unsupported; online play and amiibo are unavailable.
• The Legend of Zelda: Link’s Awakening: 1.0.0 and 1.1.0, with the matching update for 1.1.0. The 1.1.0 randomizer remains experimental; the separate local Link + BowWow co-op prototype is limited to vanilla 1.0.0.

The release requires Windows 10+ x64, an AVX2 CPU, a Vulkan 1.3 driver and at least 20 GiB of free space for initial preparation. Python and a compiler are bundled rather than separately installed. These are prerequisites, not a tested-hardware matrix.

The inherited upstream README describes other desktop platforms. This release’s assets and actual gameplay acceptance are Windows-only. Linux/macOS have CI build checks, which do not establish gameplay acceptance or an iPhone route.

Historical Beta 5.3 testing: what does it establish?

These earlier runs belong to enhanced-beta5.3, published on 17 October at 19:03:45 UTC. They are retained for context, not counted as new Beta 5.4 tests.

The Beta 5.3 validation names Windows 11 and Intel Arc Pro 140T, using independent save copies:

• 48.2 minutes: island travel, the 05:00 day rollover, rain, mail, buildings, dialogue and the airport. Saving and a later reopen succeeded, but this run exposed an incorrect presentation interval.
• After the timing fix: separate 9.5-minute and 4.3-minute runs checked indoor/outdoor movement, inventory, tent transitions, save and reopen, at approximately 29.7–29.8 fps. Do not combine these into a corrected 48-minute benchmark.
• Save checks: the tested ACNH files passed all 24 internal checksums. This validates those copies and operations, not every future save or power interruption.
• Link’s Awakening: both supported versions launched, loaded saves, changed between a house and the village, and saved at around 60 fps in those scenes.

Complete real-game import tests used NSZ files. The other advertised input formats, NSP/XCI/XCZ, and encryption paths have synthetic regression coverage, not equivalent full-game real-input acceptance. Full playthroughs, more hardware, all randomizer combinations and first-use shader stalls remain outside the acceptance claim. The gameplay acceptance revision is 1cc17a8; the release source changes labels/documentation and rebuilds helpers, as described in the validation record.

The author’s 18 October progress discussion mentions work on 3.0.1/60 fps and possible future LAN play. Beta 5.3’s verified published scope remains ACNH 1.0.0 at about 30 fps on Windows.

What do Beta 5.4’s 60 FPS and save options mean?

The pinned Beta 5.4 documentation adds ACNH 3.0.1 with optional experimental 60 FPS + SpeedFix. Standard 30 FPS remains the default. The author’s development record reports early island/interior/dialogue/save-reopen checks and limited 60 FPS movement/tent/save comparisons. It does not establish a full playthrough, all activities, sustained 60 fps or other-platform gameplay.

The correction targets a fixed 60 FPS. Below 60 fps, the corrected mode slows the game; it is not dynamic frame-rate compensation. Switch back to standard mode if performance is insufficient. Select the mode before loading the game; restart the program if a game library is already loaded. First use prepares a separate .acnh60 game copy and library; both 3.0.1 frame-rate modes share that version’s save slot.

Back up the original 1.0.0 save before converting a copy. Follow the versioned save instructions: copy the complete save mount, including headers and Villager0, to 3.0.1’s separate slot and let the game convert it. A converted save cannot be reopened in 1.0.0. Keep the original and an independent backup; do not move the converted files back.

The bundled tmouh SpeedFix patch has its own CC BY-NC 4.0 attribution and license, separate from the runtime’s MIT code. In particular, the patch’s noncommercial restriction does not disappear because the runtime uses MIT. The earlier 17:01 UTC no-release checkpoint remains in the dated archive.

Preparation and save precautions

Prepare your own legally obtained game files and any required local keys for encrypted inputs. Use the project’s own setup notes to match the exact game/module identity before importing. The launcher prepares a native game library and creates a desktop shortcut; games and versions have separate libraries, caches and saves. Successful compilation alone does not establish playability on your PC.

Experiment with a copy and retain an independent backup. The save implementation record describes per-file rename publication; it does not promise a power-loss-atomic transaction across multiple filesystems. Passing internal checksums and offering local snapshots do not remove that limitation. Preserve game data, saves, seeds and settings when upgrading, and allow incompatible native libraries to rebuild.

Where should I follow it?

Start with the fork’s Beta 5.4 release page, pinned current documentation and fork issue tracker. Keep the fork, release tag, game version and source revision distinct when comparing reports.

The reviewed Beta 5.4 runtime’s MIT license covers its own code only; dependencies retain their licenses. It grants no rights to Nintendo game content, and the project is unaffiliated with Nintendo. This page provides no game files, keys or download sources for them.

For the other routes, see nxnative on Apple platforms or SwitchWaker’s GameCube-to-Switch direction. Our evidence method separates published artifacts, author reports and independently observed results.