
Azahar 2126.0 RC2 is shaping up to be one of the emulator’s most useful updates in a while. It adds multiplayer rooms to Android, improves GPU timing, fixes several Vulkan problems and helps a number of Nintendo 3DS games run more reliably. That’s a lot for one update. This is still a Release Candidate, though, so it isn’t the final stable version. The developers released RC2 after withdrawing the first candidate because of a serious Android stability issue. That quick replacement suggests the team wants testers to focus on the new features without getting stuck on a known crash. The result is a release that feels ambitious but practical. Most of the work targets problems users can actually see: broken graphics, crashes, awkward mobile controls and games that fail because the timing doesn’t match the original hardware closely enough.
Android multiplayer finally feels useful
The biggest addition is multiplayer room support on Android. Users can now browse rooms, create private sessions, join password-protected games and use an integrated chat system. Until now, the desktop build had the more complete multiplayer experience. RC2 closes much of that gap.
It doesn’t recreate every wireless feature of a real Nintendo 3DS. You can’t connect the emulator directly to a physical console, and nearby Android devices don’t communicate exactly like two handhelds using local wireless play. Instead, the devices need a working network connection. That could mean using the same Wi-Fi network or connecting through an Android hotspot.
For private multiplayer sessions, that setup should be manageable. Public rooms take more work. Azahar doesn’t currently provide its own official public room directory. Users who want to browse public sessions must enter the address of a compatible third-party web API. Some room features are also missing from this candidate, including public room creation, room descriptions and certain details about the game running inside a session. Those limits matter, but the feature still changes what’s possible on mobile. Android multiplayer no longer feels like a rough side project. It now looks like a proper part of the emulator.
Vulkan takes over on some Android devices
Azahar 2126.0 RC2 also changes how the emulator handles graphics on Android devices that use ANGLE. ANGLE translates OpenGL ES commands through other graphics systems, often Vulkan. When Azahar detects that ANGLE is managing OpenGL rendering, the emulator now forces the Vulkan backend. You won’t see this on every phone.
The change only affects devices where the combination of OpenGL and ANGLE causes serious visual problems. On those systems, the graphics option will appear disabled, and Azahar will explain why it selected Vulkan automatically. That may sound restrictive, but it’s a sensible fix. Letting users choose a renderer doesn’t help when one of the choices is likely to produce broken graphics.
The Vulkan backend also receives several direct corrections. Monster Hunter games should benefit from a fix involving an incomplete gas-related graphics function. The update also resolves a crash during colour-fill operations and corrects an edge case that could corrupt graphics when the emulator downloaded fill surfaces. These aren’t glamorous changes. They’re the sort that make the difference between a game looking normal and a screen full of visual errors.
More accurate GPU timing fixes difficult games
The most interesting technical change sits deeper inside the emulator. Azahar now includes a revised GPU interrupt queue and an experimental option called Simulate 3DS GPU timings. As the name suggests, it tries to reproduce the timing behaviour of the original Nintendo 3DS graphics hardware more closely. Why does that matter?
Emulation isn’t only about drawing the right image. The emulator also has to perform each task at the right moment. Some games depend heavily on the timing between the CPU, GPU and system services. When that timing drifts, the game may freeze, fail to load or behave in strange ways. Luigi’s Mansion 2 is one of the clearest examples.
The game can now run without the older delay render thread workaround that users previously needed to avoid timing problems. That’s a cleaner solution, and it may help other titles that rely on similarly precise hardware behaviour.
Super Mario 3D Land also gets an important fix. A bug could stop a completed save file from loading, which is about as frustrating as it sounds. RC2 corrects that problem. The new timing mode is disabled by default, and that’s probably the right choice. It changes a sensitive part of the emulator and could cause regressions in games that already work well. It also won’t magically improve performance.
A game that struggled to reach 60 frames per second on real hardware won’t suddenly run at a locked 60 just because this option is enabled. The goal is accuracy, not free speed. CPU timing has improved too. The update fixes a system lock in Lego City Undercover: The Chase Begins and may help with similar faults in other games. Changes to the emulated GSP graphics service also improve the handling of suspended applications, image posting and certain situations where the player returns to a running game.
Duplicate frames can now be skipped
Azahar now skips the presentation of duplicate frames by default. Many Nintendo 3DS games run internally at 30 frames per second but output a 60Hz signal by showing each frame twice. That works fine on the original system, but it can confuse external frame-generation tools. Those tools may treat repeated frames as new ones, which can lead to uneven motion or poor generated results.
By removing duplicate frames before they reach the display, Azahar gives frame-generation software cleaner material to work with. Most users won’t notice the setting directly, but people using motion interpolation or external frame-generation tools may see a real improvement. Shader handling has also become more efficient.
Azahar previously generated certain LG2 and EX2 subroutine functions for every shader, even when the shader didn’t need them. RC2 only creates those functions when required. That cuts memory use without changing how the game should look.
Screenshot capture gets a fix as well. On some platforms and graphics setups, screenshots could swap colour channels and produce obviously incorrect images. The emulator now handles those formats properly.
Several smaller graphics and compatibility bugs have also been addressed. These include disabled cubemap texture units in Brain Age: Concentration Training, black screens in older homebrew applications and a possible integer overflow linked to custom Luma3DS memory mapping.
Android controls become easier to customise
Touchscreen controls are rarely ideal for games designed around physical buttons. Azahar can’t remove that problem, but RC2 gives Android users a better tool for dealing with it. The new Combo Button lets one on-screen button trigger several inputs at the same time.
That’s useful for games that rely on awkward button combinations or repeated shortcuts. Instead of trying to press several virtual buttons with perfect timing, users can assign the full combination to one control.
The button stays hidden by default. Users can enable it in the overlay settings and choose which inputs it should activate. Azahar has also improved its secondary-screen controls. That matters because every Nintendo 3DS game uses two displays, while Android devices come in dozens of shapes and sizes.
Phones, tablets and foldables all need different layouts. RC2 adds more screen options and fixes several problems in the Adjust Scale menu, making it easier to resize and position the two displays around touch controls, camera cut-outs and unusual aspect ratios. The regular Android build now includes an optional update checker too. It runs when Azahar starts and can be switched off in the settings.
Desktop users get several practical upgrades
The desktop versions don’t receive a headline feature as large as Android multiplayer, but they do pick up a solid set of improvements. Azahar’s compression tools now support command-line options. Users can compress or extract compatible files through scripts and terminal commands, which should help anyone managing larger game libraries or automated workflows. Controller support inside the desktop interface has improved as well. That includes controller-based hotkeys and fixes for shortcuts used in separate-window layouts.
The emulator now refreshes the game list automatically after the user removes installed software, updates or downloadable content. It’s a small change, but it removes the need to refresh the library manually. The file menu has also been reorganised, with clearer access to the NAND and SDMC folders.
Windows users will see a new MXE build that replaces the older MSYS2 version. Existing MSYS2 users should be able to move across without losing their data, although the old build is expected to disappear during the 2127.0 development cycle.
Windows language detection now works more reliably, and a larger part of the Qt interface should follow the selected language. On macOS, the update improves the handling of Unicode characters in SDMC filenames and fixes minor issues involving MoltenVK and Metal. An ARM64 Docker image is now available too, which broadens support for container-based and automated setups.
A major update, but still a test release
Azahar 2126.0 RC2 does much more than fix a few isolated bugs. It brings proper multiplayer tools to Android, cleans up Vulkan rendering, improves hardware timing and solves compatibility problems in several well-known games. It also makes the emulator easier to use.
Mobile players get better controls and screen management. Desktop users get cleaner file access, improved controller support and more flexible command-line tools. Still, this is a Release Candidate. Anyone who values stability over new features may prefer to wait for the final Azahar 2126.0 release.
Users who install RC2 should back up their emulator data first, especially save files and configuration folders. Most of the changes look promising, but deep timing and graphics updates can sometimes create new problems in games that previously worked without trouble. For testers, though, RC2 offers plenty to explore. It’s a serious update, and it gives a clear picture of where Azahar is heading next.














