Skip to content

Releases: azahar-emu/azahar

Azahar 2120

21 Mar 23:07
Compare
Choose a tag to compare

This changelog treats the merge of PabloMK7's fork and Lime3DS as a base upon which all of the changes listed here are applied. The changes added in Lime3DS and PabloMK7's fork during 2024, alongside the changes introduced in Azahar, will be discussed in more detail as part of our first progress report. Additionally, this changelog will not refer to any branding changes.

It is also worth keeping in mind that this first release doesn't primarily focus on adding new features, instead working to create a strong base we can build upon in subsequent releases.


Azahar 2120 Changelog

All:

  • Implemented newly discovered framebuffer vertical flip flag | @PabloMK7 + an anonymous contributor #699
  • The method of acquiring the 3DS system files has been completely overhauled, now requiring the use of a real 3DS and the new Artic Setup Tool. | @PabloMK7
  • If 3DS system files have been installed, games owned by your eShop account can now be downloaded directly from the 3DS eShop application | @PabloMK7
  • Fixed various issues relating to save states | @PabloMK7 #656
  • Added a new performance hack option named "Disable Right Eye Rendering" | @PabloMK7 758ded7
    • The 3DS renders for both the left and right eye, even when 3D is not being used. This hack disables rendering one of the eyes, which can result in performance improvements of up to 50% for some games
    • Certain games may experience graphical issues when using this hack. Try it everywhere and see what works!
    • You can use the stereoscopic side by side mode to check if the image for the right eye is being disabled, to verify the compatibility of the game
  • Added a new option which enables all LLE modules required for online functionality | @PabloMK7 d5745ca
  • Support for encrypted applications has been dropped. Applications must now be dumped in a decrypted format to be used. | @PabloMK7
  • For historical reasons related to the origin of the extension, support for the .3ds file extension has been dropped
    • Azahar now makes use of the .cci extension, which is the true name of the format used by .3ds files
    • You can still make use of ROMs with the .3ds file extension by simply renaming the file to use the .cci extension.
    • Read more about the reasons behind this change in our related blog post: https://azahar-emu.org/blog/game-loading-changes
  • The virtual 3DS now has a randomly generated MAC address | @PabloMK7
    • This can be set based on the MAC address of your real 3DS or regenerated at any time via the settings menu
  • microprofile is now disabled by default at compile time, saving a small amount of RAM | @PabloMK7 #651
  • Added Valencian and Swedish translations

Desktop:

  • If the system is set to dark mode and the default Azahar theme is being used, white icons will now be used instead of the previous hard-to-see black-on-grey icons | @kleidis #623, @rtiangha #668

Linux:

  • Fixed an issue where severe visual artefacts would appear on the parts of the window no occupied by a 3DS screen on Wayland | @OpenSauce04 #754

Windows:

  • Fixed an issue where the Windows build would occasionally be unable to generate file paths | @PabloMK7 #588
  • Minor adjustments to modernize the installer | @RedBlackAka #683

Android:

  • Fixed an issue where language translations may not apply properly | @PabloMK7 #735
  • Fixed a bug which could sometimes cause renaming files to fail | @PabloMK7 d5745ca
  • Fixed issues relating to configuration data not being saved correctly | @PabloMK7 d5745ca
  • Made AM title scanning asynchronous, resulting in significantly faster game boot times under most circumstances | @PabloMK7 d5745ca
  • Made certain AM functions asynchronous, which helps to prevent some unnecessary stuttering while games are running | @PabloMK7 d5745ca
  • Fixed an issue relating to the SOC service which could cause crashes | @PabloMK7 d5745ca

Technical:

  • The CMake option previously known as ENABLE_DEDICATED_ROOM has been renamed to ENABLE_ROOM | @OpenSauce04 56e96de
  • A new CMake option, ENABLE_NATIVE_OPTIMIZATION, has been added which enables -march=native for the C and C++ compilers if supported | @OpenSauce04 c024933
  • A new CMake option, ENABLE_MICROPROFILE, has been added which enables the now-disabled-by-default microprofile
  • The ENABLE_OPENGL option can now be manually enabled on Linux aarch64 rather than being hard-coded to be set to OFF | @OpenSauce04 #749
    • It is still disabled by default
  • Various external dependencies have been updated | @OpenSauce04 #615 #616
  • 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
  • Fixed a minor error which could cause compilation failures on some non-x86 architectures | @ouni666 @PabloMK7 #732

Azahar 2120 Release Candidate 3

17 Mar 23:26
Compare
Choose a tag to compare
Pre-release

⚠️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 update addresses a graphical regression experienced by some users in 2120-rc2.
Please update to the latest release candidate to avoid these potential issues.

This changelog builds off of the changelogs of 2120-rc2 and 2120-rc1. Please read the changes there for additional information.


Azahar 2120-rc3 Changelog

All

  • Fixed a graphical regression introduced in the 2120-rc2 release candidate | @PabloMK7 #704

Azahar 2120 Release Candidate 2

17 Mar 20:52
Compare
Choose a tag to compare
Pre-release

⚠️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
  • 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.sed files 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:

Azahar 2120 Release Candidate 1

15 Mar 19:20
Compare
Choose a tag to compare
Pre-release

⚠️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 changelog treats the merge of PabloMK7's fork and Lime3DS as a base upon which all of the changes listed here are applied. The changes added in Lime3DS and PabloMK7's fork during 2024, alongside the changes introduced in Azahar, will be discussed in more detail as part of our first progress report. Additionally, this changelog will not refer to any branding changes.

It is also worth keeping in mind that this first release doesn't primarily focus on adding new features, instead working to create a strong base we can build upon in subsequent releases.


Azahar 2120-rc1 Changelog

All:

  • The method of acquiring the 3DS system files has been completely overhauled, now requiring the use of a real 3DS and the new Artic Setup Tool. | @PabloMK7
  • If 3DS system files have been installed, games owned by your eShop account can now be downloaded directly from the 3DS eShop application | @PabloMK7
  • Fixed various issues relating to save states | @PabloMK7 #656
  • Added a new performance hack option named "Disable Right Eye Rendering" | @PabloMK7 758ded7
    • The 3DS renders for both the left and right eye, even when 3D is not being used. This hack disables rendering one of the eyes, which can result in performance improvements of up to 50% for some games
    • Certain games may experience graphical issues when using this hack. Try it everywhere and see what works!
    • You can use the stereoscopic side by side mode to check if the image for the right eye is being disabled, to verify the compatibility of the game
  • Added a new option which enables all LLE modules required for online functionality | @PabloMK7 d5745ca
  • Support for encrypted applications has been dropped. Applications must now be dumped in a decrypted format to be used. | @PabloMK7
  • For historical reasons related to the origin of the extension, support for the .3ds file extension has been dropped
    • Azahar now makes use of the .cci extension, which is the true name of the format used by .3ds files
    • You can still make use of ROMs with the .3ds file extension by simply renaming the file to use the .cci extension.
    • Read more about the reasons behind this change in our related blog post: https://azahar-emu.org/blog/game-loading-changes
  • The virtual 3DS now has a randomly generated MAC address | @PabloMK7
    • This can be set based on the MAC address of your real 3DS or regenerated at any time via the settings menu
  • microprofile is now disabled by default at compile time, saving a small amount of RAM | @PabloMK7 #651

Desktop:

  • If the system is set to dark mode and the default Azahar theme is being used, white icons will now be used instead of the previous hard-to-see black-on-grey icons | @kleidis #623, @rtiangha #668

Windows:

  • Fixed an issue where the Windows build would occasionally be unable to generate file paths | @PabloMK7 #588

Android:

  • Fixed a bug which could sometimes cause renaming files to fail | @PabloMK7 d5745ca
  • Fixed issues relating to configuration data not being saved correctly | @PabloMK7 d5745ca
  • Made AM title scanning asynchronous, resulting in significantly faster game boot times under most circumstances | @PabloMK7 d5745ca
  • Made certain AM functions asynchronous, which helps to prevent some unnecessary stuttering while games are running | @PabloMK7 d5745ca
  • Fixed an issue relating to the SOC service which could cause crashes | @PabloMK7 d5745ca

Technical: