Azahar 2126.0 Release Candidate 5

⚠️Important Release Candidate Information⚠️

This is a release candidate. Please expand this drop-down to read more about what this means before installing.

As a release candidate, this build is not yet considered a stable release, but is instead a build which could be promoted to a stable release if it is sufficiently tested with no major issues being discovered. Ideally, the release candidate period will last for 7 days, however if major issues are discovered, this will be extended to allow for additional testing with a corrected release candidate.

Despite its status as a pre-release build, users are encouraged to test this version to help us catch any newly introduced issues before the build is promoted to a full release. If you do observe such issues, please report them to us on GitHub so we can evaluate them.

If you are unwilling to tolerate potential minor issues, you may be better off waiting until a release candidate is promoted to a full release.

Users are advised to back up their Azahar user data directory before using a pre-release build.

---

Note

This changelog is relative to 2126.0-rc4. You can find the previous changelog here.

---

Azahar 2126.0-rc5 Changelog

All

• Refactored how filesystem access is handled for special files (such as Z3DS files), in preparation for changes coming in Azahar 2127. | @PabloMK7 #2352
  • Fixes compressed 3DSX files (.z3dsx) with an embedded RomFS failing to load properly.
  • Users should not expect any visible changes as this is only an internal restructuring of the code. If that is not the case please consider filing a bug report.
  • NOTE: Due to internal changes on how system files are stored, system files set up on Azahar 2126 or newer will become incompatible with older Azahar versions. On the other hand, system files set up on versions older than Azahar 2126 will remain backwards compatible for the foreseeable future.
  • More details on why this change is neccessary can be found in the pull request.

Desktop

• Fixed an issue where the "Old 3DS setup" and "New 3DS setup" labels were erroneously swapped in the Set Up System Files menu. | @OpenSauce04 #2351