Azahar: baixar versions anteriors

This a minor release for the 2126 branch which primarily addresses a reported security advisory.
It also includes several newly backported improvements and fixes from the master branch.
Users are advised to update as soon as is convenient.
Azahar 2126.2 Changelog

All
- Addressed an oversight which allowed specially-crafted CIA files to execute arbitrary code in the host environment when locally installed by a user. | @PabloMK7 #2648
- Addresses the following GHSA report: GHSA-h74v-5mw8-qg8r
- Fixed an issue where the xBRZ texture filter would be applied incorrectly when using the Vulkan renderer, resulting in an incorrect appearance. | @OpenSauce04 #2647
- Handling of large HTTP downloads within emulated 3DS applications has been improved, improving memory efficiency and stability. | @PabloMK7 #2515
- Fixes downloading large games from the eShop.
- Added a new 3GX loader flag allow_homebrew_load, which allows loading 3GX plugins for homebrew apps if the plugin supports it. | @PabloMK7 #2649

Desktop
- Various improvements to GDB and RPC servers, fixing certain issues and improving functionality. | @PabloMK7 #2631, #2640, #2633
- For additional info, see individual PR descriptions.
- Script developers will need to update the RPC client as this is a breaking change.

Android
- Fixed a crash which could occur if the gpu_drivers directory contained a subdirectory. | @ygordreyer #2592

Technical
- Creating a copy of the kernel shared and config pages using svcMapProcessMemoryEx is now possible.
- This is a technical accuracy change. Little to no end-user impact.

This an unscheduled fix release which addresses a commonly experienced issue in Azahar's libretro cores.
For other versions of Azahar, this update is identical to 2126.1.1.
Azahar 2126.1.2 Changelog

libretro
- Fixed an issue which could cause RetroArch to entirely freeze or crash when exiting a game. | @Razor221 #2572

This an unscheduled fix release which addresses a few notable issues discovered post-launch in the 2126.1 update.
All users are encouraged to update as soon as is convenient.
Azahar 2126.1.1 Changelog

All
- Fixed an issue where Azahar could instantly crash when opened on certain systems with poor Vulkan support. | @Wunkolo #2528
- The "Skip Presenting Duplicate Frames" setting has now been disabled by default due to minor observed regressions compared to the old behaviour. | @PabloMK7 #2530, @OpenSauce04 #2536
- Fixed an issue which could cause Azahar's Vulkan renderer to crash when handling certain shadow textures. | @Wunkolo #2533
- Fixes a crash in Monster Hunter 4 Ultimate after opening the equipment menu.

Windows
- The About menu and Azahar's log file now indicate which build variant is currently being used (MXE, MSVC or MSYS2). | @OpenSauce04 #2538

This minor release contains many improvements and fixes which didn't make it into the base 2126.0 release.
Of particular focus in this release are stability improvements, eliminating potential crashes in many identified scenarios.
All users are encouraged to update as soon as is convenient.
Azahar 2126.1 Changelog

All
- Save states are now locked to the version of Azahar that they were created with. | @PabloMK7 #2394
- Attempting to load a save state from a different Azahar version will now display an error message explaining this restriction, and will also display the version of Azahar that the save state was originally created with, recommending temporarily downgrading to retrieve progress using the in-game save functionality if necessary.
- This does not limit save state usage compared to previous behaviour. Before this change, loading a save state from a previous version of Azahar would just crash the emulator. This change now gracefully shows a message instead.
- Fixed an issue where it was possible for texture surfaces to be deleted while in use, especially at larger internal resolution settings. | @Wunkolo #2407
- This change fixes Vulkan related crashes in many different games and situations. Most notably, when starting missions in Monster Hunter 4 Ultimate.
- The highest available internal resolution scaling setting has been increased from 10x (4000x2400) to 18x (7200x4320), allowing 8K displays to take full advantage of upscaling functionality. | @72374 #1906
- Implemented a fix for a crash in Teenage Mutant Ninja Turtles: Danger of the Ooze when using the Vulkan renderer due to inaccurate handling of the rasterizer cull mode being set to an unusual value. | @PabloMK7 #2396
- Fixed an issue which caused excessive lag in the character select screen for Super Smash Bros 4. | @PabloMK7 #2412
- Fixed an issue which caused excessive lag in Mini Mario & Friends: Amiibo Challenge when walking on diagonal surfaces. | @PabloMK7 #2412
- Fixed a regression which caused the 3DS friends menu to crash when opened. | @PabloMK7 #2412
- Fixed a crash which could sometimes occur during multiplayer sessions due to thread-unsafe logic. | @PabloMK7 #2405
- Implemented optimizations to GPU command list processing which save 0.5-1ms of processing time per frame on average. | @PabloMK7 #2318
- Implement geometry shader output register banking, which fixes a lot of SEGA 3D Classics games without the need of per-game patches. | @PabloMK7 #2338
- The mentioned games still present other rendering issues that need to be fixed in future versions of the emulator.
- Fix floating point denormal accuracy, which fixes various rendering issues in several games. | @Wunkolo #2350
- Fixed an issue where linear filtering was forcefully enabled with certain drivers, primarily on Android w/ Adreno. | @PabloMK7 #2445
- Fixed an issue where the 3DS Internet Browser would freeze due to incorrect core rescheduling behaviour. | @PabloMK7 #2370
- Implemented an improvement to emulated audio handling which fixes crackling sounds when an audio source's volume is changed. @Grayforz2468 #2409
- Most notable example is the Home Menu no longer having crackling music.
- Fixed an issue which caused HLE audio emulation to produce crackling in games that update looping PCM16 buffers while they are being played. | @Angelico2102 #2454
- This is known to address audio issues in "Inazuma Eleven 3".
- Fixed an issue in the Vulkan renderer related to the handling of disabled cubemap texture units. | @Wunkolo #2406
- This brings over a fix which was previously applied to the OpenGL renderer in a previous update.
- Fixed an invalid memory access issue related to uds beacons. May fix undiscovered issues in certain multiplayer games. | @PabloMK7 #2403
- Implemented checks to ensure that Vulkan layers the system doesn't support are not enabled, avoiding crashes on certain setups. | @Wunkolo #2511
- Fixed a crash which could happen during gameplay under certain circumstances while usi

Known Issue Notice
There is a minor known issue in the new MXE build for Windows where frame pacing may be slightly inconsistent. A potential fix for this issue has already been implemented, but requires additional testing. This fix will be included in the 2126.1 update.
Most users likely won't notice this issue, so use of the MXE build is still encouraged.
The MXE build will replace the MSYS2 build in 2127.0.
Thank you for your understanding.

Azahar 2126.0 Changelog

All
- Improved GPU interrupt queue & GPU timing emulation. This feature is highly experimental and is disabled by default, the toggle for it can be found in the graphics settings: "Simulate 3DS GPU timings". | @PabloMK7 #2095, #2145
- This change improves emulation accuracy by more closely mirroring the behaviour of real hardware.
- This PR is known to fix GPU timing issues in Luigi's Mansion 2: Dark Moon, which is now made playable without use of the "delay render thread" option, but likely impacts many other games as well.
- This PR also introduces a fix for an issue in Super Mario 3D Land which would prevent users from loading a save file after completing the game.
- This is a big change behind the scenes, and may inadvertently introduce issues due to its large scope. Please report any issues which may have been introduced by the new behaviour.
- Games that use dynamic FPS and don't reach 60 FPS on real hardware will also not reach 60 FPS on Azahar with this feature enabled.
- The PR description contains an in-depth technical explanation of the changes.
- Completely revamped the implementation of GDB functionality, with numerous debugging improvements and new debugging features. | @PabloMK7 #2086
- The PR description for this change goes into extensive detail about the changes, so read there for more information if curious.
- Refactored how filesystem access is handled for special files (such as Z3DS files), in preparation for changes coming in Azahar 2127. | @PabloMK7 #2352
- Fixes compressed 3DSX files (.z3dsx) with an embedded RomFS failing to load properly.
- Users should not expect any visible changes as this is only an internal restructuring of the code. If that is not the case please consider filing a bug report.
- NOTE: Due to internal changes on how system files are stored, system files set up on Azahar 2126 or newer will become incompatible with older Azahar versions. On the other hand, system files set up on versions older than Azahar 2126 will remain backwards compatible for the foreseeable future.
- More details on why this change is neccessary can be found in the pull request.
- Fixed an issue where screenshots produced by Azahar could have their colour channels swapped on certain platforms and system configurations. | @mal-cap #2170
- Added a setting to skip presenting duplicate frames, which is enabled by default. | @KojoZero #1867
- This makes frame generation software work properly with Azahar.
- Added a new option which allows users to toggle whether the emulated 3DS system thinks headphones are plugged in. | @PabloMK7 #2099
- A very small number of games have altered behaviour when using wired headphones. For example, when headphones are plugged in while playing Super Mario 3D Land, the audio playback is slightly altered.
- In multiplayer rooms, users' usernames are now pulled directly from the username set in the System tab in Azahar's settings instead of being a separate option.
- Fixed a crash which could occur when an application submits a vertex array with an invalid base address. | @PabloMK7 #2299
- Known to fix a crash in the credits of Mario & Luigi: Superstar Saga. May fix other problems elsewhere.
- Adjusted rom loading error messages displayed to users to be more easily understandable and user-friendly. | @PabloMK7 #2097
- LG2/EX2 subroutine functions are now only emitted for shaders when necessary, instead of for every shader, reducing memory usage. | @Wunkolo #2046
- Fixed an issue where certain older homebrew software would g

This is an unscheduled release which almost exclusively addresses issues in the macOS version of Azahar.
Primarily, it fixes an issue experienced by many users where Azahar could potentially freeze when opened.
This issue didn't affect all users, and whether or not it appeared was dependent on multiple factors such as the macOS version being run and the macOS version Azahar was built with, and the current state of the user's Azahar directory. Because of this, it took some time to determine the root cause of the issue. Apologies for any inconvenience this may have caused for any affected users.
Azahar 2125.1.3 Changelog

macOS
- Fixed an issue where Azahar could instantly freeze on boot depending on certain factors such as OS version and Azahar user data content. | @OpenSauce04 #2244

Technical
- Backported a fix for linker warnings when building with Discord rich presence on macOS, first introduced in 2126.0 Alpha 2. | @OpenSauce04 #2216
- The CMake option name change introduced in that PR has not been backported.
- Introduced changes to dynarmic which fix a build issue introduced my MSYS2 package updates. | @PabloMK7 #2236

This is an unscheduled release to put into action new security policies we have enabled for Azahar after the recent TeamPCP supply chain attacks, which affected big open source projects like CEMU Emulator.
This release contains no user-facing changes when compared with 2125.1.1 outside of the security policy changes. We decided to publish this release now so that the new policies are applied as soon as possible. Users may choose to skip this release if they wish.
Please keep in mind that Azahar was NOT compromised by the attacks and our users are safe. We are just being proactive and adding security measures to our release distribution process as a preventative measure.
Azahar 2125.1.2 Changelog

All
- Enabled Attestation and Software Bill Of Materials for release assets to increase release security. | @PabloMK7 #2117
- From now on, Azahar releases are immutable. This means that once we publish a release, the assets linked to it cannot be changed in any way. This prevents token stealers from modifying release assets after they are published. You are able to know if a release is immutable if it shows a padlock icon with the word Immutable at the top left of the page.
- Starting from this release, Azahar release binaries are attested. This means that all of the official Azahar assets have now signed claims that specify where they were produced (CI jobs), the exact commit and timestamp, and other metadata.
- Users should be able to verify the validity of azahar binaries using the GitHub Cli. For example: gh attestation verify --owner azahar-emu --predicate-type "https://spdx.dev/Document/v2.3" <file-path>. This command will only succeed if the file was not tampered with, which is useful when downloading assets from secondary sources, such as our Internet Archive page.
- While plain sha256 hashes serve to verify integrity, attestations also allow to include the aforementioned metadata.
- You can view the attestations for all of our binaries in the Attestations page.
- Also starting from this release, Azahar binaries have a Sofware Bill Of Materials, which consists in a JSON that (in theory) contains all dependencies Azahar relies upon, which should help tracking vulnerabilities. In practice, this technology is rather new, so not all dependencies are fully detected. You can read more about this in #2117.
- A verify-release bash script is now provided in our source code that helps verifying the validity of Azahar releases. This allows users to better audit our releases as well as easily obtain the software bill of materials. Example usage is as follows: ./tools/verify-release.sh azahar-emu/azahar 2125.1.2. You can learn more about this tool in #2117.

Technical
- Added EXCLUDE_FROM_ALL to CMake targets where applicable, speeding up build times for certain non-standard build configurations. | @OpenSauce04 #2088
- All libretro core binaries are now stripped, greatly reducing filesize (primarily for the Android core) without affecting functionality in any way. | @OpenSauce04 #2111
- This is only relevant for the core binaries distributed by us; The cores used by the RetroArch core downloader were already doing this.

This is an unscheduled bugfix update which addresses previously undetected regressions in the 2125.0 and 2125.1 releases.
Users are advised to update when it is convenient to do so.
Azahar 2125.1.1 Changelog

Windows
- Fixed a regression introduced in 2125.1 where Azahar could appear to have rounded window corners while fullscreened. | @PabloMK7 #2049

All
- Fixed a regression introduced in 2125.0 where a small number of games could crash due to a shadow texture handling oversight. | @PabloMK7 #2047

Technical
- Changed a newly introduced use of the std::powf function in 2125.1 to use std::pow instead, restoring wider build environment compatibility. | @cobalt2727 #2045
- Miscellaneous OpenBSD build fixes. | @OpenSauce04 #2052

This is a minor release for the 2125 series which introduces bug fixes and some low-risk improvements + new features.
Azahar 2125.1 Changelog

All
- Added emulation of the 3DS's notification LED. | @PabloMK7 #2019
- Only the desktop frontend exposes this functionality as of now (see "Desktop" section).
- Fixed color blend modes behaving incorrectly on the OpenGL graphics backend. | @PabloMK7 #2038
- This notably fixes an issue where a black square could appear in the bottom-right corner of the screen in some games (e.g. Shin Megami Tensei IV)
- Implemented syscore CPU time limiting to match real hardware behaviour. | @PabloMK7 #1934
- Makes emulated applications properly use the syscore without starving LLE system applets, which fixes several subtle timing issues.
- Most notably, fixes stability issues caused by having the BOSS LLE module enabled.
- The BOSS LLE module is now enabled by the "Enable required LLE modules for online features" setting. | @PabloMK7 #1952
- Fixed emulated applications receiving incorrect error values from getaddrinfo/getnameinfo functions. | @GasInfinity #1956
- Optimize GeometryEmitter SETEMIT state, providing a minor performance improvement for games which use geometry shaders. | @Wunkolo #1996

Desktop
- Added a new UI element which displays the emulated 3DS's notification LED. | @PabloMK7 #2019
- Fixed Discord rich presence often not being set correctly due to a race condition. | @PabloMK7 #2035
- Removed Vulkan warnings which could appear at application launch on setups with missing Vulkan features. | @RedBlackAka #1938
- Removed Mesa OpenGL version override due to improved upstream support. | @RedBlackAka #1938

Android
- All builds of Azahar on Android, including the libretro core, now use the Vulkan renderer by default. | @OpenSauce04 #2003
- Note: On builds of Azahar other than the libretro core, this change doesn't apply retroactively to existing user configurations.
- Added a button to the about game dialog which allows deletion of disk shader cache on a per-game basis. | @PabloMK7 #2032
- Addressed an issue where orientation changes while a 3DS application is booting could cause the emulator to crash. | @PabloMK7 #2030
- Fixed an issue where hidden 3DS system titles could appear in the application list erroneously. | @PabloMK7 #1935
- Fixed an issue where, if a game was launched via an intent while another game was already open, the new game would be stuck infinitely loading. | @inssekt #2000
- Fixed an issue where resetting the values of the background color setting to the default would cause the app to crash. | @ptyfyre #1959
- Fixed application exits (e.g. with homebrew apps that close themselves) resulting in an "Invalid ROM Format" error dialog. | @SiniKraft #1991

libretro
- Fixed an issue where the libretro core could crash under certain circumstances when using the Vulkan renderer. | @warmenhoven #2004

Technical
- Added new ENABLE_BUILTIN_KEYBLOB CMake option, enabled by default. | @PabloMK7 #2024
- This is enabled by default for all of our builds, mimicking prior behaviour.
- Disabling it omits the built-in keys usually distributed with Azahar, which disables certain functionality.
- Added new USE_SYSTEM_OAKNUT CMake option. | @marcin-serwin #1947
- Improved logging for SVC failures. | @PabloMK7 #1948
- Our x86_64/Intel macOS binaries are now cross-compiled from an ARM64 macOS runner. | @OpenSauce04 #1953
- Fixed an issue where attempting to build Azahar's test suite alongside our libretro core while using GCC would result in a linker error. | @warmenhoven #2012
- Fixed several issues related to building and using Azahar on NetBSD. | @OpenSauce04 #1998
- Unit tests are now able to be discovered by IDEs via catch_discover_tests. | @Wunkolo #1997
- Correct the response of SendToOther in soc:U. | @GasInfinity #1929
- This is a correctness fix, and has no effect on the end-user.

Note
Pre-existing users of the Android vanilla variant should uninstall their current Azahar app before installing this new version, as the application ID has changed. No user data will be lost, and the same user directory just needs to be selected during setup.
The new application ID for vanilla is org.azahar_emu.azahar. Third-party emulator launchers may need to account for this change. The application ID for the Google Play Store variant remains unchanged.
This is to differentiate the Vanilla build from the Google Play version, preventing the Google Play Store from attempting to update it.
Azahar 2125.0 Changelog
libretro
- Azahar is now available as libretro/RetroArch cores for various OS platforms. | @warmenhoven #1215 + other PRs
- Below is a list of platforms with available cores in this initial release:
- Linux (x86_64)
- Windows (x86_64)
- macOS (arm64)
- macOS (x86_64)
- Android (arm64)
- iOS
- tvOS
- Other platforms and architectures may be added in subsequent releases.
- It's important to note that, due to restrictions around the use of JIT compilation on the App Store, the iOS and tvOS have JIT forcefully disabled by default* on those platforms. Disabling JIT has a big impact on performance, so emulation speed may be below 100% on devices other than those which have been released relatively recently.
- * For more information, read here: https://docs.libretro.com/guides/install-ios/#jit
All
- Implemented a disk shader cache for the Vulkan renderer in the form of .vkch files. | @PabloMK7 #1725 #1748
- These files keep track of compiled shaders so that there is no need to recompile them on subsequent application launches, which removes all stutter caused by shader compilation after the first playthrough of the application.
- Cache files can also be copied between your own devices to benefit from the reduced stutter.
- Implemented NWM_SOC::GetMACAddress, allowing applications which utilize it to function properly. | @PabloMK7 #1840
- This change allows using the NetPass homebrew application on Azahar.
- Greatly reduced CPU usage of Azahar while using Artic Base. | @keynote #1789
- Shader and pipeline compilation tasks are now handled by separate workers, improving parallelism and slightly reducing shader compilation stutter. | @PabloMK7 #1802
- Re-added texture filtering functionality while using the Vulkan renderer. | @jbm11208 #1675
- This feature was previously added in version 2124, but was subsequently removed in 2124.2 due to stability issues.
- This iteration should address the issues present in the previous implementation.
- Fixed an issue where, if a game with no cheats had its cheat list viewed or the game was launched, the cheats list for the previously loaded game would be erroneously used. | @Fs00 #1640
- Minor fixes to local play for Luigi's Mansion 1 and Download Play applications. | @lannoene #1690
- Minor optimization applied to the Vulkan renderer which slightly reduces its memory usage. | @PabloMK7 #1710
- Very minor optimization for log message filtering, effective when a large number of LOG_DEBUG messages are produced in a short time-frame. | @PabloMK7 #1773
- Implemented new "Integer Scaling" option. @DavidRGriswold #1400
- Added a new "Layouts to Cycle" setting, which allows users to select which layouts are cycled by the Cycle Layout/Toggle Layout hotkey. | @DavidRGriswold #1430
- Apply the selected texture filter to color surfaces, not just texture surfaces. | @PabloMK7 #1784
- Major refactor of configuration backend for all platforms, improving maintainability | @OpenSauce04 #1762
- This change is primarily a developer-facing one, but does somewhat affect end-users on Android by having the default config.ini file be dynamically generated and validated, meaning that keys which were missing in the default config file are now present. | @OpenSauce04 #1762
- CECD LLE module is now enabled by the "Enable required LLE modules for online features" setting. | @PabloMK7 #1842
- Download Play sessions 

This update re-enables support for the .3ds extension, which was previously removed in Azahar's initial release.
We previously made this change as a clear motion to distance ourselves from the mass piracy that lead to the closure of Yuzu and Citra, however, we have now determined that this change is causing more harm than good.
We've noticed that the removal of the .3ds extension has caused unnecessary fragmentation in the 3DS emulation community. This led to the creation of dubiously safe forks, to which a portion of the Azahar userbase migrated. These forks used unsafe deployment practices, presented licensing concerns, and confused users as to whether the forks were part of the upstream Azahar project. These circumstances created an unhealthy open-source development environment, and we don't believe that this is in the best interest of the 3DS emulation scene.
Given that the removal of the .3ds extension was originally an act of project philosophy rather than a technical change, we don't want this decision to overshadow the very real leaps which have been made in Azahar over the last year. Because of this, we have decided that it's for the best of everyone that we revert the change.
It is important to note that support for encrypted ROMs is still disabled; This will not change for the foreseeable future. Unlike the .3ds extension, which is a matter of project philosophy, encrypted ROMs still present actual legal challenges that we do not want to take on.
We have decided to publish this change in its own Azahar release to avoid the change overshadowing additions made in the future 2125 update.
We hope that this change will help to bring the 3DS emulation community closer together.
Azahar 2124.3 Changelog
All
- Re-added support for the .3ds file extension. | @PabloMK7 #1701