Azahar 2126.1 Release Candidate 4

⚠️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.

---

This release candidate is an amendment to 2126.1-rc3. It introduces some final tweaks and fixes in preparation for the stable release. We hope that this will be the final release candidate, assuming no major issues are discovered.

For a more complete picture of what will be included in the final release, you can see the changelog for Release Candidate 1 here:
https://github.com/azahar-emu/azahar/releases/tag/2126.1-rc1

---

Azahar 2126.1-rc4 Changelog

All

• Implemented checks to ensure that Vulkan layers the system doesn't support are not enabled, avoiding crashes on certain setups. | @Wunkolo #2511

Desktop

• Fixed the setting for the newly introduced debug exception handler being erroneously enabled by default; it is now disabled by default. | @PabloMK7 #2505
  • Having this setting enabled can cause certain game mods which specifically target emulators to crash.

Android

• Invalid ROMs are now displayed with an "Invalid ROM" card in the game list instead of being blank. | @OpenSauce04 #2509
  • These blank cards unintentionally contained an error string in 2126.1-rc3 due to an oversight. By the nature of this change, that issue has also been fixed.