⚠️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.
This follow-up release candidate addresses some issues that were discovered in the first release candidate, 2120-rc1, alongside introducing a fix for a long-standing graphical issue which has been present since Citra.
⚠️ This update should be considered mandatory for all MacOS users. This is due to a fix being included for a particularly significant bug relating to booting the HOME menu which specifically affected MacOS users.
This changelog builds off of the changelog of 2120-rc1. Please read the changes there for additional information.
Azahar 2120-rc1 Changelog
MacOS
- Fixed an issue which would consistently cause the system files installed in Azahar's virtual 3DS to become corrupted | @PabloMK7 #694
- Users affected by this issue in 2120-rc1 can fix it by updating to this release and re-running the setup process, as the old corrupted data will be deleted
All
- Implemented newly discovered framebuffer vertical flip flag | @PabloMK7 + an anonymous contributor #699
- This fixes a long-standing issue where Starfox 64 3D would appear upside-down
- Fixed an issue which made it impossible to set up New 3DS files using Old 3DS hardware | @PabloMK7 #679
- Fixed an issue which stopped Azahar from being able to use
movable.sedfiles from some non-XL Old 3DS models | @PabloMK7 #697 #701
Desktop
- Re-added the Report Compatibility button to the Help menu, which now directs to the Azahar compatibility submission guide. | @OpenSauce04 #678
- This button previously existed in Citra, but had different functionality
- Fixed the "Artic Traffic" label being difficult to read while using a light theme | @PabloMK7 #700
Technical
- Fixed compilation errors introduced with the release of the CMake 4.0 release candidates | @OpenSauce04 #688
- Fixed compilation errors on Linux introduced with the release of a recent Pipewire update | @mdartmann #691
Appended Information:
The MSYS2 version of 2120-rc2 has temporarily been removed to an unforseen issue.
The MSYS2 version will be reinstated when 2120-rc3 releases.
For now, please use the MSVC version on Windows platforms.
Thank-you for understanding. :SMILE: