⚠️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 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-rc3 Changelog
All
- Added a new "Limit frames ahead of GPU" setting to toggle a previously introduced optimization which improves latency, now disabled by default. | @DavidRGriswold #2793
- Since 2127.0-alpha4, this behaviour was always enabled, but some users reported that it caused a performance regression.
- Users with a sufficiently powerful device can now choose to enable it manually to reduce input latency in exchange for performance.
Android
- Fixed a bug where all setting values in Azahar's
config.inifile would be written directly, rather than leaving untouched values blank. | @DavidRGriswold #2784- Due to this issue, Azahar setups which have run on Azahar 2127.0-rc1 or 2127.0-rc2 will no longer properly reflect any future changes to Azahar's default settings.
- This can be resolved by resetting all settings in Azahar's settings menu after upgrading to a version with this fix.
- Due to this issue, Azahar setups which have run on Azahar 2127.0-rc1 or 2127.0-rc2 will no longer properly reflect any future changes to Azahar's default settings.
- Fixed an issue where devices running Android 17 or later would be unable to connect to a real 3DS device or other local devices. | @OpenSauce04 #2803
- Azahar will request a new Local Network Access/ Nearby Devices permission on these devices when run for the first time after updating.
Desktop
- Fixed multiple issues relating to default hotkey values. | @DavidRGriswold #2791
- Fixed some issues relating to keyboard navigation in the game list. | @DavidRGriswold #2783