⚠️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 prerelease is an amendment to 2127.0-rc3. It addresses an issue first introduced in 2127.0-rc3 where updating from an existing Google Play build of Azahar on an Android 17+ device would result in a crash on launch. It is otherwise mostly identical to 2127.0-rc3.
Note
This release invalidates any existing generated shader cache.
Because of this, performance may temporarily be impared after updating from 2126.2 or earlier.
Performance will improve again after playing for a while.
Azahar 2127.0-rc4 Changelog
Android
- Fixed a regression where launching the Google Play build with Azahar already set up but no Nearby Devices permission granted would result in an immediate crash on Android 17+ devices due to a stray assert. | @OpenSauce04 #2830