⚠️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.
Despite being a minor release, Azahar 2123.2 is receiving a release candidate. This is due to it containing notable internal changes to how the emulator is built, specifically on MacOS and Windows.
To help us catch issues before a full release, users are advised to test this release candidate if they can tolerate potentially uncaught minor issues.
2123.2 will also address some minor stability issues on Android.
Azahar 2123.2-rc2 addresses a regression in the Vulkan renderer which could cause persistent emulator crashes after a specific user action. More details below.
This issue affected versions 2123, 2123.1, and 2123.2-rc1.
For a list of the other changes which will be introduced in 2123.2, see the prior 2123.2-rc1 changelog.
Azahar 2123.2-rc1 Changelog
All
- Fixed an issue where, if the
shaders/vulkan/directory was manually deleted, the emulator would fail to recreate it properly, resulting in the emulator crashing due to failure to write cache data. | @OpenSauce04 #1373- Users who encountered this issue will stop experiencing crashes after updating.