Dolphin

Emulator 2503

Dolphin emulates the Nintendo GameCube and Wii consoles on macOS and other platforms, with the 2503 version developed by the Dolphin Team; a fork for iOS, DolphiniOS, is also available.

Dolphin is an open-source emulator designed to replicate the Nintendo GameCube and Wii consoles, offering extensive compatibility with original games. Developed by the Dolphin Team, it runs on macOS, including recent models with Apple Silicon processors, as well as other platforms.

A derived version, DolphiniOS, exists for iOS, but Dolphin focuses on an optimized user experience for PC and Mac environments. The tool leverages advanced features such as support for modern controllers and graphical enhancements, while respecting the technical specifics of both consoles.

Mario Kart Wii sur Dolphin
The Legend Of Zelda : Twilight Princess sur Dolphin
Okapi dans Dolphin
Beyond Good & Evil dans Dolphin

Last updated:

Platforms

Architecture

Mac OS X - macOS Mac OS X - macOS Intel x86 Intel x86 Apple Silicon Apple Silicon 64-bit 64-bit Metal Metal

Download and links

Version history

2609
  • NetPlay sur Android : Ajout d’un système de demande de permission réseau local pour NetPlay, avec une interface utilisateur simplifiée via Jetpack Compose.
  • Correction de crash : Fix d’un bug provoquant des plantages du menu de configuration sur Android 9.0 et versions antérieures.
  • Correction de crash : Résolution d’un problème où un contrôleur GameCube branché sur le port 1 d’un adaptateur de contrôleur GameCube ne fonctionnait pas en NetPlay.
  • Correction de crash : Bug corrigé sur macOS entraînant des plantages de jeux au démarrage.
  • Correction de sécurité : Limitation des risques de RAM excessive et d’écriture mémoire dans un fichier NAND Wii via NetPlay.
  • Correction de sécurité : Empêchement d’un débordement de buffer lors du chargement d’un état de sauvegarde malveillant.

Welcome to Dolphin 2609's accompanying Progress Report! Like everyone else, we've been doing our best to weather the Techpocalypse brought on by AI, but it's really come after us in the past few months. Our website has been up and down repeatedly lately, as our defenses are barely holding out under the endless bombardment. But now AI has started to come for the emulator directly, with people using AI to mass-scan open source projects for potential vulnerabilities and overwhelm our volunteer team with very verbose reports. Though draining, once these vulnerabilities are out there, we can't ignore them. A lot of effort has had to be diverted to deal with them, both in patching them and adjusting our workflows to better manage them. For more information, zip directly to that section with this link here.

But that's not all. A vulnerability in macOS allowed our macOS buildbot to be briefly compromised by a generic cryptominer attack. We'll skip the quick summary and just point you toward the full story below, which you can reach by clicking here. The important thing is that we have determined that no builds were compromised.

We really just want to keep making Dolphin better. Fortunately, despite these headaches and roadbumps, there are still quite a few notable changes to go through, so let's get to it.

Hotfix Release 2609a

We released Dolphin 2609a on 7 October 2026. You can find the full change log below.

  • Added a prompt on Android to request permission for local network access while using NetPlay.
    • This permission is not required if you only want to play with others over the internet.
  • Approved additional codes and patches in various games for use with RetroAchievements in hardcore mode.
  • Fixed an issue on Google Play where Dolphin was accidentally listed as compatible with 32-bit ARM devices.
  • Fixed a bug which caused the settings menu to crash on Android 9.0 (Pie) and older.
  • Fixed a bug where a GameCube controller plugged into port 1 of a GameCube Controller Adapter did not work in NetPlay.
  • Fixed a bug which could cause games to crash at boot on macOS.

Here are the security patches in this hotfix release.

  • Fixed a bug where attempting to assemble certain syntactically invalid source causes Dolphin to crash.
  • Fixed a bug where a malicious NetPlay host could cause clients in a room to reserve an excessive amount of RAM.
  • Fixed a bug where a malicious NetPlay host could cause clients in a room to write part of their memory into a file on the Wii NAND.
  • Fixed a bug where a maliciously crafted save state could cause Dolphin to write outside of a buffer when loaded.

Notable Changes

All changes below are available in Release 2609.

2606-91 - Android NetPlay by tom-pratt

Under the hood, our mobile and desktop builds are almost identical. Dolphin is simply Dolphin; the only difference is the UI that lays on top. Despite this, our Android release doesn't have feature parity with our flagship desktop builds. A lot of features that are missing in the Android GUI that are present in the desktop GUI are mostly missing because they'd be difficult to implement or would have limited value on Android.

NetPlay once fell into both camps.

For those unaware, Dolphin has lockstep NetPlay available to allow for online play in games that only had local multiplayer. Lockstep NetPlay requires perfect synchronization between each instance, and thus Dolphin has to run in a deterministic mode. This means forcing Single Core (or using a slower and even hackier version of Dual Core), setting the same starting time/seed, and making sure the same inputs make it to every machine. Optionally, save data and cheats can also be synchronized for use on NetPlay. If done right, each instance of the emulator will stay synchronized with no further intervention, with Dolphin only passing inputs.

All of these complexities make NetPlay an enticing, but often cumbersome-to-use feature. And given that it would be annoying to create a good GUI for NetPlay on Android and it would make games run slower on already limited hardware, there was no rush to implement it on Android.

In the 2020s, the scales started to tilt in the other direction. Android devices have gotten stronger and stronger, and though CPU governors and GPU drivers still confound us, many flagship devices can run games in Single Core just fine. Additionally, Jetpack Compose for Android allows for easier and faster development of Android GUIs.

Wanting to share some of his favorite childhood experiences with his own kids, tom-pratt stepped up to the challenge. Using Compose, he built up the NetPlay Android GUI across several pull requests, with an initial bare bones implementation. This made it easier to review and eventually merge, and was quickly followed up with more features, such as controller port configuration for the host, that brings it closer to parity with the desktop implementation.

And now, as of Dolphin 2609, NetPlay is ready for Android users!

Currently, Android NetPlay requires users to be on a standard network (Wi-Fi, Ethernet, etc), but work has been started on adding support for Wi-Fi Direct, which would allow Android NetPlay to function between nearby devices with no network, similar to how the Nintendo DS's local Wi-Fi play worked.

Note: Using NetPlay over mobile data is not recommended. Even if you can get it to work, the packet loss and latency are not particularly suitable for lockstep multiplayer.

Cross Platform NetPlay

Can Android and desktop Dolphin play together with NetPlay? Yes, they can! Players can mix and match devices with whatever they have, so phones and laptops can play together just fine! However, there are some limitations that must be kept in mind.

Most full-size desktops use x86-64 processors, while most phones use ARM processors, and Dolphin uses different JITs depending on the host CPU. While our ARM64 and x86-64 JITs are very similar, they are not completely identical, and those JIT differences are likely to cause desyncs. Mixing and matching CPU architectures isn't a guaranteed failure though - whether these differences lead to a desync or not depends on what instructions games use and in what order.

Ignoring the JIT problem, there is one more major source of potential desyncs: the Framebuffer! Games that use EFB Access and/or Store EFB/XFB Copies to RAM can get different results from different graphics drivers. If these results mismatch at all, even if it doesn't directly affect game logic, a timebase desync will usually be reported. Often this won't outright break NetPlay (at least immediately), but if the difference becomes big enough, the instances will diverge. Given how special Adreno and Mali drivers are, there may even be problems when playing between different kinds of phones in those games!

In many games, none of these limitations will come into play. Even the differences in the JITs may not end up mattering. However, keep these factors in mind if everything is set up correctly and you're still experiencing desyncs.

2603-394 and 2606-121 - Add XFB Resolution OSD Display by elyashue and JosJuice

As we have covered a few times before, GameCube and Wii games were made with analog displays in mind, where overscanning the edges of the screen away was the norm and the pixels didn't even need to be square! Since the only requirement was "close enough", GameCube and Wii games usually render around 640x480, but the exact rendering resolution will vary from game to game and even scene to scene.

Given this vague resolution reality, some users wanted a tool to know the exact resolution that a game was running at, but Dolphin didn't really have a way to tell them. The best existing method was to take a screenshot at Raw Internal Resolution, but that doesn't tell you what a game is doing right now, only what the game was doing when you took that shot. Plus, you have to check the screenshot to see the dimensions.

This simple change allows users to know in real time what a game is doing with resolution. Go to Config > On Screen Display and turn on "Show XFB Resolution", and the game's current resolution will be shown in our on-screen overlay. Now as games change resolutions, you can see exactly what is happening, as it happens!

Here are some NTSC examples.

The GameCube and Wii use non-square pixels, so the aspect ratio is not defined by the rendering resolution. With this new feature, you can see that for yourself in games like F-Zero GX.

As expected, 640x480 is prevalent across the GameCube and Wii library.

640x456 is common on Nintendo-developed Wii games.

The NES and SNES had a vertical resolution of 224 lines. This legacy can be found on the GameCube and Wii in the many games that use the doubling of that vertical resolution: 448.

But ultimately, games can do whatever they want!

Games can even change resolution during play! Rogue Leader uses 640x450 for normal gameplay. But its cutscenes are anti-aliased, which increases the memory needed per pixel, so cutscenes use a smaller framebuffer size of 640x304. This also gives these scenes a cinematic aspect ratio of 2.1:1 - turning a technical detail into a visual flourish is exactly what we've come to expect from Factor 5.

As should be pretty clear from the thumbnails, the statistic shown is specifically the resolution the game is telling the emulated console to output (XFB resolution), not what Dolphin is actually presenting. Dolphin's aspect ratio compensation, internal resolution multipliers, and output presentation after resampling are not demonstrated by this feature.

2606-186 - Android: Route DolphinBar Balance Board to the Balance Board slot by tommywaaf

When Dolphin on Android was being prototyped back in 2012, Wii Remote support was easy - use Dolphin's Real Wii Remote feature to connect it through the device's on-board Bluetooth adapter. Simple. Unfortunately, the Google Graveyard beat us to the punch. Android 4.2.1 made changes to the Bluetooth stack to improve Bluetooth controller support, and in the process broke Wii Remote support entirely. Since Android 4.2.1, no Android device has been able to use Wii Remotes with their native Bluetooth connection. So when Dolphin on Android Beta became available to the public in 2013, there was no way to use Wii Remotes.

Fortunately, the Mayflash DolphinBar came to the rescue. By integrating its own Bluetooth radio and passing HID reports directly to Dolphin, the Mayflash DolphinBar could allow Wii Remotes to connect even on uncooperative operating systems and Bluetooth stacks. In 4.0-8877, Dolphin Android gained the ability to connect to the Mayflash DolphinBar, finally allowing this tentpole feature to work on Android.

But something was missing in that update. The Wii Balance Board didn't work!

After Nintendo's grand experiment to expand beyond the standard gamer audience proved tremendously successful, Nintendo noticed that many people were using its new console's revolutionary motion controls for regular exercise. Naturally, Nintendo responded with a peripheral made specifically for that: the Wii Balance Board. Effectively four pressure sensors inside a big flat Wii Remote that you stand on, the Balance Board itself is incredibly simple, but it opened the doors to fitness software so successful that the Balance Board was genuinely used in hospitals for physical therapy! It was less successful outside of fitness, with Balance Board support in games like Super Monkey Ball: Step & Roll and Skate It mostly receiving a "meh" response from players, though it did establish a strong niche in party games.

Since the Wii Balance Board is basically just a Wii Remote, it was pretty trivial for Dolphin to support. Once Dolphin added the Balance Board device ID to its Real Wii Remote code, it connected just like a Wii Remote would. The same applies to the Mayflash DolphinBar. The Balance Board can connect to the Mayflash DolphinBar, and Dolphin can detect the Balance Board through it. Simple.

On Android though? The fun fitness-focused peripheral was able to connect to the Mayflash DolphinBar just fine, but Dolphin on Android simply didn't look for it, making the peripheral unusable and all of the games that required it unplayable! Where the code for the check should have been was simply // TODO. Oops.

A simple four line change makes Dolphin on Android aware that the Balance Board exists, allowing the peripheral and the 135 games that can use it to finally be playable in their balanced form for the first time ever on Dolphin Android.

At long last, you can use the Wii Balance Board with the device you take everywhere! It's very portable, as the Wii Balance Board only weighs as much as four laptops!

If you carry a Wii Balance Board in your backback, you can now play Wii Fit Plus's Bird's-Eye Bull's-Eye whenever the fancy takes you! At school, in the library, even at the park!

2606-215 - CMake: Replace the Visual Studio project by JoshuaVandaele

CMake is a core component of Dolphin's build infrastructure. It's what's known as a "meta build system" - rather than building anything itself, CMake writes out the project files that other tools then use to actually do the building. This heavily simplifies our build system and allows us to easily support many combinations of operating systems and build tools. We can generate Makefiles, Ninja build files, Xcode projects and more with just a single CMake script!

However, there has long been an outlier in our infrastructure: Windows. While CMake supports generating Visual Studio projects on Windows, Dolphin has always been built with our own custom Visual Studio project files. Even after CMake was introduced to Dolphin's repo in 2013, it was never used for our Windows builds. The decision to continue using our custom Visual Studio project has placed a long-term maintenance burden on the project. By having two separate build systems co-exist simultaneously, we're effectively doubling the work involved when someone adds or removes source code files, all for one operating system.

This has now changed! Dolphin now uses CMake on all platforms, with our Windows builds being built with a Visual Studio project file that is generated by CMake. By having CMake handle the Visual Studio stuff for us, we were able to remove over 12,000 lines of Visual Studio-specific build files, making our lives much easier. During this process, we also updated our Visual Studio version to the recently released Visual Studio 2026.

But how does all this impact users? Ideally, it shouldn't have any impact at all. The VS2026 update is the only thing that might affect anyone, as we are now using a newer version of the Visual C++ runtime. If you use our updater, it'll download the latest Visual C++ Redistributable for you automatically and all you'll need to do is press "Continue" on the installer. However, if you are updating your Dolphin instance manually, you may need to download and install the latest version of the Visual C++ Redistributable yourself. You can find a handy link right here (download the X64 version, or ARM64 if you are using Windows on ARM).

One thing of note: as part of this change, DSPTool is no longer being shipped with our Windows builds. You can compile this developer tool yourself if it is useful to you.

2606-321 - Android: Add global settings search by Simonx22

This change adds a search field to Dolphin's settings on Android. With our settings buried in submenu after submenu on Android, the ability to do a quick search for exactly the setting you are looking for is so nice. Just type part of the setting name, then tap a search result to jump directly to the right submenu.

2606-97, 2606-132, and 2606-328 - Android Rumble Fixes by JosJuice

JosJuice fixed three rumble issues in Android that combined make rumble substantially better on that OS.

On Android, all vibration has to go through an API called VibratorManager. However, Dolphin's handling of it was wrong ever since the 2023 input code rewrite. We would fetch the list of vibrator IDs correctly, but instead of passing a vibrator ID to the VibratorManager, we passed the index of the ID in the list. This happened to work on most devices because the only vibrator had both an ID and an index of 0. But users of Retroid devices weren't as lucky - the ID there is 1. Dolphin would try to request the vibrator that has ID 0, but since there was no vibrator with that ID, no vibrations would happen. 2606-97 correctly passes the ID as we should, and vibration should work on all devices that support rumble. (Your Nvidia Shield TV won't rumble even if you want it to, because it lacks the necessary hardware!)

As of 2606-132, Dolphin now uses the vibration attribute USAGE_MEDIA. This tells VibratorManager that our vibrations are for games and not touch feedback. With this change, users who disable touch feedback in their Android settings will no longer also be disabling all rumble in Dolphin. If you prefer to play your games without rumble, you can still unmap rumble in Dolphin's controller settings.

GameCube and Wii games use a variety of different rumble lengths, but Dolphin used to ignore this on Android and vibrate for exactly 100 ms for any and all vibrations. The reason comes down to a mismatch in how Android handles rumble. A GameCube controller or Wii Remote starts rumbling when an "on" command is sent, and stops when an "off" command is sent. Games can delay the off command to get a longer rumble, or even switch back and forth between on and off to get a weaker rumble, but no matter what, the game has to send an off command eventually to make the rumbling stop. Android, on the other hand, requires apps to say up front how long a vibration should last. Because Dolphin can't look into the future to know when the game will send its off command, we used to simply tell Android to vibrate for 100 milliseconds. With 2606-328 and newer, whenever a game asks for rumble, Dolphin tells Android to vibrate for 10 seconds, and when the game says to stop rumbling, Dolphin tells Android to cancel the vibration. With this, GameCube and Wii rumble feels much closer to the original intent.


This Release's Contributors...

Special thanks to all of the contributors that incremented Dolphin by 388 commits after Release 2606!


Brace for Impact! - The AI vulnerability reporting wave crashes into Dolphin

In 2024, we received one report about a security issue in Dolphin, and it was notable enough that it got its own Progress Report section. In 2025, we received zero reports. In 2026, we've received more than 10 reports, and that's only so far. Something has changed, and reading the reports makes it obvious: it's AI.

LLMs and the tooling built around them have become better and better at finding security issues in software. A person who's interested in finding vulnerabilities can spin up AI agents and leave them running to discover issues on their own, and because of the subsidized prices that AI companies are offering for now, it's relatively affordable. This capability is both a good and a bad thing. On one hand, attackers can now find vulnerabilities more easily. On the other hand, defenders can also find vulnerabilities more easily, helping them keep software secure... But the number of vulnerabilities being found means a lot of time has to be spent validating, triaging and fixing them. In Dolphin, that all falls on our volunteers.

As with most things AI nowdays, not only are LLMs leading to more reports, but also longer, worse and outright incorrect reports. For example, curl has gotten so many bad reports that they announced an end to paying out bug bounties, and later, a vacation for the maintainers. Google Chrome has vastly more resources and uses less confrontative wording in blog posts, but they too are announcing bug bounty changes, like "revising our program scope" and "shifting our program's focus to prioritize concrete proof that a bug exists". Due to the sheer volume of security issues being found, they're even going to make two security releases per week.

As for Dolphin, almost all the writeups we've received this year were clearly written by AI, containing an overkill amount of detail. But fortunately, nobody has sent us complete hallucinations (yet)! Every report contained some kind of valid bug, with some being more exploitable than others. Most of them were simple buffer overflows like the one reported back in 2024, and those are easy for us to understand and fix.

Still, this is an order of magnitude more security reports than we've ever had to deal with before, and security bugs come with extra coordination constraints. Publishing a security bug means attackers can start trying to exploit it, so we want to minimize the gap between making a bug public and making a release that includes the fix. Unfortunately, this is basically the opposite of how we're used to working. Uploading a patch that fixes a bug reveals what the bug is, but we normally fix bugs by uploading a patch as soon as we have one and then waiting days or weeks for someone else to review it, usually without taking into account when the next release will be. This year we've tried a few different ways of handling this, like reviewing patches in private, starting a normal review process once the next release is a few days away, and in some cases (mostly for less serious bugs), doing things more or less as usual. So far we haven't settled on any particular process, but it's something we'll continue thinking about.

Making changes right before a release means the new code doesn't get as much testing as it otherwise would have, and we did unfortunately have issues sneak in from some of the bigger changes we made in response to security issues. A rewrite of Wii NAND save stating that landed in Dolphin 2606 broke loading save states in certain Wii games like Donkey Kong Country Returns (fixed in Dolphin 2606-292 and 2606a) and broke loading save states while TASing any Wii game (fixed in Dolphin 2606-379 and 2609). Added validity checks for DOL files that landed in Dolphin 2606a broke loading Wii Menus that had been patched with Priiloader (fixed in Dolphin 2606-308/2606-325 and 2609).

Security issues will likely keep being found in the future, so to cap off, we have two important things to say:

If you've found a security problem in Dolphin: To handle reports in an orderly way, we recently opened up GitHub's vulnerability reporting flow. Please use it to report any security bugs you find! While dealing with security reports does use up some of the precious hours we're able to spend on Dolphin, we prefer fixing vulnerabilities over letting them linger. If you have a bug that isn't a security issue, please report it on the bug tracker instead.

If you're a Dolphin user: Please keep your Dolphin install up to date! We had several security fixes in Dolphin 2606, many additional ones in Dolphin 2606a, and a few more in Dolphin 2609. If you're running a version of Dolphin other than the latest release or a recent development build, you'll have to assume it contains known security bugs, so don't open any untrusted files with it or use it to play NetPlay with untrusted people. Fortunately, so far we haven't seen anyone trying to maliciously exploit Dolphin, but we suggest not taking any unnecessary risks.

The macOS Cryptominer Incident

Dolphin has supported macOS for almost as long as Dolphin has been open source. As part of this support, we create official macOS builds for each development and release version and post them on our website. Because a Mac is generally required to create apps for macOS, we have a partnership with MacStadium, a hosting provider that specializes in cloud-based Mac infrastructure. MacStadium provides us with access to a Mac mini through their Free and Open-Source Software sponsorship program, and we use it to produce builds of Dolphin, run ARM64 unit tests, and to perform automated graphics testing through FifoCI.

When using a Mac as a server, the Screen Sharing feature is very helpful for system administrators. Screen Sharing allows one to remotely connect to a Mac and control it as if it was actually in front of them. While servers running Unix-like OSes like Linux are often solely managed through a command line, it is more difficult to manage a Mac with a command line exclusively. Screen Sharing provides full access to the macOS GUI, making many administration tasks easier. Because Macs provided through MacStadium are physically located in a data center, Screen Sharing is enabled by default on their machines.

The Attack

On August 6, Apple released macOS Tahoe 26.6.1. The user-facing patch notes were rather vague, with the only listed change being "security fixes". More detailed patch notes were posted a day later, revealing that a bug was fixed where Screen Sharing could be manipulated into allowing someone to connect to the machine without valid credentials. On affected macOS versions, someone could use this vulnerability to log in as an administrator on any machine that had Screen Sharing enabled, and wreak as much havoc as they wanted. This was a critical vulnerability for Macs being used as servers, as these machines often have Screen Sharing enabled for management purposes and may be directly exposed to the internet.

Not long after the update was released, an attacker reverse engineered the patch and figured out how the vulnerability worked. They quickly took advantage of it and started compromising any vulnerable machine that they could find on the Internet. First, they would use Screen Sharing to add their own SSH key as an authorized key for the root user, allowing them to administrate the computer via the SSH protocol. Next, they would block the Screen Sharing port with a firewall rule to prevent others from re-compromising the machine. Finally, using their new SSH entry point, the attacker would deploy a cryptominer to mine Monero. Even though the vulnerability was already patched in an update, this attacker was able to quickly leverage it to spread a cryptominer to tons of unpatched Macs all over the internet.

Compromised

Unfortunately, due to our macOS system administrator being busy with personal matters, this important security update went unnoticed initially and our build machine was not patched in time. MacStadium blocked Screen Sharing in their networks after the attacks ramped up, but this was too late for us. On August 8, the attacker compromised our macOS build machine through the Screen Sharing vulnerability. The observed payload was the same Monero cryptominer found on other affected machines. We believe that this attack was not targeted specifically towards Dolphin, as all indicators of compromise matched other machines infected with the cryptominer, and we did not observe any indications of data exfiltration or other payloads on the machine.

We eventually noticed that the machine was compromised on August 15 and shut it down. Because we were unaware that there was malware on the machine from August 8 to 15, we were using it during that period of time to produce new builds of Dolphin. This includes development versions between 2606-294 and 2606-302, as well as the 2606a hotfix release. Since the attacker had full control over the machine when these builds were produced, we became very concerned over the possibility that they could have been infected with malware.

Thankfully, after manually analyzing the contents of each build, we can report that none of the builds appear to be compromised with any malware. We also ran each build through VirusTotal and found no evidence of anything suspicious. However, if you are running any of these macOS builds, we recommend that users should update to the latest development or release version, out of an abundance of caution. We would also like to reiterate that only our macOS build machine was compromised during this incident, so users on Windows, Android, and Linux are unaffected.

Remediation

On August 16, we requested that MacStadium support delete all data on the Mac and re-install macOS from scratch. Our macOS build machine was eventually restored on August 18. In total, it took 4 days to fully recover from the incident. After getting access to the fresh installation of macOS on the 16th, we decided to take the time to improve our security measures. For example, we no longer expose Screen Sharing directly to the Internet and now require an additional layer of security before it can be accessed.

We have learned many lessons from this incident, and it has also motivated us to thoroughly audit our infrastructure. We will be making further improvements in the future to reduce the risk of anything like this happening again.

2606a
  • Support officiel du Game Boy Player : Ajout de l'émulation du périphérique Game Boy Player pour la GameCube, permettant de jouer à des jeux Game Boy via Dolphin avec jusqu'à cinq instances simultanées pour le multi-joueur.
  • Correction de bugs critiques de sécurité : Correction de plusieurs vulnérabilités (overflows de mémoire, fuites d'informations, débordements de tampon) dans le traitement des fichiers GCZ, DOL, ELF et LZO, ainsi que dans le module DSP-HLE.
  • Correction des sauvegardes Wii : Résolution d'un problème empêchant le chargement des sauvegardes Wii lorsque des fichiers étaient ouverts dans le jeu.
  • Amélioration des effets de bloom : Correction d'un problème visuel majeur dans les effets de bloom pour les jeux GameCube/Wii à haute résolution, grâce à un nouveau module Graphics Mods nommé Bloom Blurred.
  • Prise en charge du mixeur audio Wiimote : Ajout d'un mixeur audio pour les haut-parleurs intégrés des Wiimotes, permettant de rediriger le son vers d'autres périphériques audio compatibles.
  • Activation de CCache pour les builds macOS : Ajout d'une option pour activer CCache dans les builds universels pour macOS, améliorant potentiellement les performances de compilation.

Welcome to the Progress Report for Dolphin Release 2606. We usually prefer to launch toward the beginning of the month, but a slew of important, large, and technically challenging changes had us working overtime. Strap in, because we have a lot to cover!

For April Fool's we teased that Dolphin now had support for the Game Boy Player, but the joke was that it was real! We'll detail exactly how it happened and the challenges that surrounded getting the emulated hardware and software working together. The last unplayable Triforce game, The Key of Avalon, no longer has that title! It is now functional in Dolphin, supporting up to five instances of the emulator together for 4 player (and a server) action. And Graphics Mods quietly fixed a major visual issue at high resolution that has plagued many flagship games for Dolphin's entire existence!

All of that and more in this Dolphin Progress Re-

✱ knock knock knock ✱

Huh, someone's at the door. Could you get that?

That's right! Since the last Dolphin Progress Report, RetroAchievements support has come to Wii games. You can now waggle your way up the leaderboard! We'll go over some statistics of the launch in a section down below, which you can reach with this handy link!

Without further ado, let's get to the Notable Changes for Dolphin 2606!


Hotfix Release 2606a

We released Dolphin 2606a on 11 August 2026 with some important security patches and a fix for Wii save states. You can find the full change log below.

  • Fixed several heap overflow bugs when reading a malformed GCZ file. (GHSA-7pvc-j9pm-c2rp)
  • Fixed a heap information disclosure bug when reading a malformed DOL file. (GHSA-27c8-xjgc-74mj)
  • Fixed several bugs where malformed ELF files can read and write outside of a buffer.
  • Fixed a buffer overflow when receiving a malformed LZO block during NetPlay save synchronization.
  • Fixed a bug in DSP-HLE where software using the AX μcode can write outside the bounds of a buffer in host memory. (GHSA-4q28-hhjv-hf3f)
  • Fixed several bugs in DSP-HLE where software using the Zelda μcode can read and write outside the bounds of buffers in host memory. (GHSA-983q-fjjx-96h3)
  • Fixed a bug where the /dev/net/ip/top IOS device can leak uninitialized host memory to the guest. (GHSA-5fqv-9qrg-gm4j)
  • Fixed an issue where loading save states for Wii software can fail when the software has open files.
  • Added a flag to enable CCache in the macOS universal binary build script.

Notable Changes

All changes below are available in Release 2606.

2603-175 - HW: Game Boy Player Support by Billiard and endrift

The Game Boy family of handhelds are legends of a bygone era. Under the crushing weight of incredibly primitive technology, Nintendo chose to focus on portability and great games rather than pushing the latest and greatest hardware. They were right. The Game Boy line outsold every single competitor they ever faced!

However, as great games accumulated on the platform, demand began to build for a way to play them on nicer, larger, lit screens. Nintendo eventually answered it with the Super Game Boy for the Super Famicom/Super Nintendo, and its Advance'd successor, the Game Boy Player for the Nintendo GameCube.

These devices were literally Game Boys without a screen that plugged into a home console, transmitting audio and video to the host console and receiving input from its controller. Software running on the host console would handle interfacing between the two systems and sometimes could add additional features if a game supported it.

We imagine that Nintendo chose to use actual Game Boy hardware because of the difficulty of making a general-purpose software emulator. The perfect demonstration of this is a third-party competitor to the Game Boy Player, the Advance Game Port, which attempted just that! By creating a Game Boy Advance emulator, Datel was able to ship a lower cost way to play GBA games on a GameCube. It was very ahead of its time, but also very flawed.

Nintendo showed that they could do emulation better on a per-game basis with titles like Pokémon Box, but they didn't see it as a plausible solution for the entire library. By shipping actual GBA hardware, the Game Boy Player was able to bypass all performance and compatibility concerns.


Being a peripheral for the GameCube, emulating the Game Boy Player has always been in the back of our minds. There was even an feature request for it for over 16 years! But it languished on the issue tracker and became the oldest open issue for one simple reason: emulating the Game Boy Player would essentially mean emulating a Game Boy Advance (which potentially involves making a new GBA emulator from scratch) and how it communicates to the GameCube. There was no way anyone would be willing to volunteer the gargantuan effort necessary just for an amusing curiosity.

Ultimately, the feature request was accepted, but there was really no path forward for it back then. We just recommended that users use one of the many available GB/GBC/GBA emulators already available, and figured that would be the end of it. They could even use the Advance Game Port in Dolphin if they really needed to run GBA games in Dolphin, as that peripheral has been partially supported since the 4.0 era.

For the longest time, the feature request was completely dormant, until around five years ago. Support for the Game Boy Player became a bit more realistic when mGBA was integrated into Dolphin. It was the ultimate solution to emulating the Game Boy Advance connectivity features found in some GameCube games, fixing all of the synchronization and communication issues that had plagued the feature for years in one fell swoop. With this, the tables had turned on Game Boy Player emulation. Couldn't we just use the integrated mGBA to emulate the Game Boy Player hardware?

The answer was yes, and endrift got to work on a Game Boy Player implementation in Dolphin! However, for various reasons, the project stalled out. And so it sat as years went by, forgotten by everyone... except the users who would occasionally ask us why we teased it as coming soon at the end of the integrated mGBA article. Oops.

Fast forward to 2026, and in the waning days of March, Billiard stumbled upon endrift's mostly-finished Game Boy Player project, and had an idea. A wonderful, awful idea: wouldn't it be funny to complete the work and add Game Boy Player support to Dolphin on April Fools' Day? With just days until the first of April, the plan rapidly unfurled and developers pounced on the code, rushing to polish things up for a quick pull request, review, test, and merge. Game Boy Player support ended up being merged a few hours into April Fools' Day.


Post by @dolphin@dolphin-emu.org
View on Mastodon

The final part of the gag was this image, which we posted without explanation on our social media and Discord on the first day of April. Watching the confusion and disbelief give way to excitement was delightful.


While we did a lot of testing to make sure Game Boy Player support was working, when legendary GameCube sage extrems started typing in our developer chat shortly after the pull request was merged, we knew we had !#@%ed up. Not only are they a living reference book for GameCube hardware, they are also the author of the definitive Game Boy Player homebrew software, Game Boy Interface (GBI). And Game Boy Interface exposed a lot of problems in Dolphin's Game Boy Player implementation.

How did we miss this? During the rush to polish and test the code, we primarily used the official Game Boy Player Start-Up Disc. That software heavily processes everything from the Game Boy Advance hardware, crushing its video contrast and applying filters to its audio. The processing was so heavy that the audio issues went unnoticed during our rushed testing - the audio sounded a little muddy rather than piercing.

In all honesty, Game Boy Player support really should have gone through a lengthy review process to allow people like endrift and extrems to test and comment heavily on the code and implementation. But if we did that, it probably would have just sat around in our open pull requests and ended up bitrotting again. By pushing things straight to production, we forced ourselves into the position of needing to fix the issues fast.

And after at least a few very minor fixes and improvements, the situation wasn't nearly as dire.

All of that work has paid off. As Game Boy Player support enters a Dolphin release and sees wider availability, we think it is ready.

To use the Game Boy Player in Dolphin, simply load a Game Boy game into the Game Boy Player via the "Game Boy Player ROM" setting in our GUI, then run the Game Boy Player Start-Up disc or Game Boy Interface. That's it!

You can find the Game Boy Player ROM setting within the GameCube settings.

And that's all there is to it. Dolphin will automatically attach the Game Boy Player hardware when necessary through INI settings. If desired, users can manually attach the emulated Game Boy Player by adding HSPDevice = 2 under [Core] in Dolphin.ini or a GameINI. This should do nothing to actual GameCube games though. ...Probably.

Note: For importing/exporting saves from other Game Boy emulators, the Game Boy Player technically counts as GBA slot 5 in Dolphin (after the 4 Integrated GBAs) and will load saves that have "-5" appended to them.


Now, we need to take a moment to go over the limitations of our Game Boy Player support.

Dolphin is not a Game Boy emulator; we emulate the GameCube, Wii, and Triforce. Our integrated GBA is only there to support things that a GameCube can do, such as connecting a Game Boy Advance to the controller port in supported games, or attaching a Game Boy hardware peripheral and funneling its audio and video to a large screen. As such, we are not trying to replicate every part of the Game Boy experience. We are only trying to recreate the Game Boy Player experience specifically, along with all of its quirks.

Game Boy Player support in Dolphin should be considered a curiosity rather than the premier way to run these handheld games in an emulator. Not only does Dolphin have much higher system requirements, but dedicated Game Boy emulators will provide a superior experience in almost every way, with better fitting UIs and support for many more Game Boy features. They also don't need additional software to use their Game Boy hardware. But if you have a Game Boy Player and Start-Up Disc lying around and desire some nostalgic fun, or want to explore the Game Boy Player experience with GBI in Dolphin, or if you just really need those sweet borders (we get it), Dolphin's Game Boy Player emulation is for you.

2603-37 and 2603-100 - Triforce: Implement Necessary Hardware for The Key of Avalon by Billiard and Crediar

The Key of Avalon games on the Triforce represent an incredible emulation challenge unlike anything else that Dolphin has encountered before. And it's not because the game itself is difficult to run; at its core, it's a relatively simple game to emulate. There's no crazy graphical effects, wacky CPU tricks, or any MMU manipulation. It's just a basic game.

The problem we encountered was that this game is so rare that we were never able to actually get our hands on the cabinets, only the GD-ROMs that the games came on. And this is a pretty big problem, because the unique hardware was the whole point of the game - four satellite Triforces with touchscreens and card readers that communicated with a central Triforce connected to a large screen to allow for multiplayer trading card monster battling in full 3D!

The biggest hurdle was the touchscreens inside the pedestals. They were completely foreign to anything we've ever seen, Triforce or GameCube! As it became increasingly clear that we may never get a chance to see the real hardware, we employed the tried and true strategy of "poke at it until you find something". It's not a particularly efficient way forward, but it was the only option available. Any signs of life moved us closer, and after a few weeks of throwing stuff at the wall, we eventually made a breakthrough. We had stumbled across the Elo SmartSet Data Protocol for touchscreens, which ended up being similar to the protocol the game actually uses. That lead didn't get us all the way there, but it was close enough that we could get to the finish line on our own.

Finally, we could push that "START" button on the touchscreen and go in-game... right?

After all of the work to get the touchscreen functional, this was a heartbreaking moment. However, it wasn't all bad. We could finally access the game's tutorial if we don't insert an IC Card. This allowed us to reach some delicious scripted gameplay and told us that we couldn't be that far away.

The problem was that we didn't know exactly what was causing the hang. There could be more oddities with the touchscreen, problems with the deck/card readers, and it also had to communicate with a server in order to proceed to gameplay. Given that the tutorial didn't use any networking, the client-server networking was the first target of our attention.

As detailed in our Rise of the Triforce article, this game uses a server-client architecture, where the touchscreen pedestals are the clients and the central Triforce is the server that actually controls the game state. We thought that perhaps there was some issue with the network, but as far as we could tell, the game wasn't even trying to communicate with the server yet. It initially synced up on power-on, but didn't spam any network commands during the hang. However, thanks to a patch that allowed us to see some debug output from the game, we were able to see some IC Card commands repeating indefinitely.

For a quick refresher, IC Cards are physical cards that can be used to save your progress in some Triforce games. We initially assumed that IC Cards would work fine in Avalon, as they already functioned properly in Virtua Striker 4 and Gekitou Pro Yakyuu. But the logs weren't lying - something was wrong, and some quick hacks to the IC Card handling code changed the behavior.

Undeterred by setback after setback, Billiard ended up rewriting a good chunk of the IC Card handling code in order to make it behave more logically. While we can't say for sure this is how real hardware would behave without having access to it, the responses make a lot more sense. But with the rewrite, we also broke both Virtua Striker 4 and Gekitou Pro Yakyuu. Great.

Thankfully, these regressions were more a consequence of rewriting a lot of code at once, and didn't end up being much more than bumps on the road. After fixing them and tightening up the code a little bit more, it was time to try The Key of Avalon once again.

Finally, it was in-game!

However, even though we could control the game, we still didn't implement enough of this game's weird hardware to make it truly playable. The game was giving us a deck of mostly starter cards and other garbage because the deck reader wasn't fully working. crediar had already started efforts on implementing the deck reader and did hardcode a list of cards to give the player. This worked for 27 of the 30 cards, and the game generously filled out the rest of the deck with starter cards. But to play a trading card game, you really need to be able to build your own deck.

An elegant solution would be to have a GUI deck editor where you can construct and load multiple decks for playing the game. However, that would be a lot of work, and we were still understanding the game at this point. Instead, Billiard added a quick and dirty method to load a deck of cards into the game using a JSON file.

{
  "cards": [
    {
      "index": 12
    },
    {
      "table": 1,
      "index": 13
    },
    {
      "index": 18,
      "quantity": 3
    }
  ]
}

This file demonstrates the different ways to set cards. Index defaults to 0, quantity defaults to 1.

With all of this, it is finally at least possible to play The Key of Avalon in Dolphin. Full matches against other players and the CPU both work, and players can save their progress to IC Cards. But this isn't to say it's a perfect experience quite yet.

Currently, entering the Segaboot menu will essentially softlock the game as it cannot reboot normally for unknown reasons. The game does not detect that prize cards have been dispensed, meaning there's a message at the top of the screen after rounds telling you to take your prize cards. This message can be reset in the Segaboot menu. We hope to fix these problems in the future.

2603-215 - Graphics Mods: Enhance Bloom by iwubcode

For a large set of GameCube and Wii games, including many flagship titles, a broken effect has significantly impaired their visual fidelity at high resolutions for Dolphin's entire existence. Yet under everyone's radar, iwubcode has slipped in a fix for this problem, quietly producing one of Dolphin's biggest graphical enhancements in years! But to explain this, we need to go over what the effect was trying to achieve in the first place.

Let's talk a bit about light.


Camera sensors and film have a limited dynamic range, so the photographer must adjust the incoming light with the aperature and shutter speed so the subject is within the dynamic range of the media (properly exposed). However, photography sensors and even film cannot capture the entire dynamic range of the world. This can result in an artifact. If a spot of light in the scene is much brighter than the dynamic range of the sensor/media, it will not only peak out the spot it falls on, but also bleed a little bit into dark areas around the light, softening and rounding highlights.

This phenomenon is the overexposure artifact halation in film and CCD saturation or "charge bleeding" in digital photography. There are differences between the two but we'll just refer to halation for convenience from here on.

Haze (atmospheric light scattering) is a visual phenomenon caused by light bouncing on particles suspended in the air or the air itself, resulting in a diffuse glow around intensely bright objects. ✱ Flare and other optical phenomenon can add glow as well.

All combined, these artifacts result in "bloom", the glow around bright objects as seen in photos.

We have all been exposed to a bazillion photos and videos from real life on a limited range display. Our brains have learned to pick up on the artifacts that brightness beyond the dynamic range creates in the camera, and given the correct context, they can interpret this as brighter than just white alone.

This illusion means that bloom is essential for making objects look bright on a standard dynamic range display.

Yet for a long time, games were not able to reproduce these artifacts. They were limited to "SDR rendering" - their engines were internally limited to the same tiny dynamic range as a typical CRT. The brightest white a game could comprehend was the same white as the screen, same with black. With this limitation, game engines could not understand dynamic range at all, let alone recreate the artifacts that result from it! This manifested in games having a flat, low-contrast, and "cartoon-background" look. Artists could still make games look amazing, of course, but due to the difficulty of manually lighting every single scene, SDR rendering's limitations still largely drove the look of lighting in the games industry.

This changed with the advent of High Dynamic Range Rendering (HDRR) in 2004. With HDR Rendering, game engines could now understand and render way beyond the limitations of SDR, and then tone map down to SDR for display. In effect, the game's camera now percieved light akin a camera looking at the real world. In-camera effects such as crushed blacks, halation, haze, flares, specular highlights, sparkles, aperture and exposure, bokeh, and more could be properly recreated in games!

The effect this had on the gaming industry was transformational. HDR Rendering has become ubiquitous, so much so that the term has largely disappeared - it's just rendering now!

So, what did all this mean for our favorite purple cube and waggle stick?

The GameCube and the Wii were built on top of ArtX graphics technology from the tailend of the 1990s. Their graphics hardware, while very capable and flexible, was fundamentally limited to SDR rendering. As HDR rendering was revolutionizing game lighting in the mid-2000s on PC and the "next generation" of consoles, GameCube and Wii games were starting to look... old fashioned. How could developers for the GameCube and Wii keep their games looking fresh?

If you don't have the tech, just art it instead!

The GameCube and Wii were not capable of understanding dynamic range, so the game engine cannot determine when a pixel is "brighter than bright" on its own. But what if we just let artists tell the game engine instead? If a texture mapped the light emission that goes beyond the standard dynamic range, an emission map if you will, then the game engine could use that information in the scene to create effects that look like HDR Rendering! Keep in mind that this isn't actually HDR Rendering, and it's limited in what it can do. For example, you can forget about dynamic lighting in a system like this, as it is by definition not dynamic. But if the game is baking all the lighting anyway, as most GameCube and Wii games did, they could use this trick to tremendous effect.

This "fake HDR bloom" showed up all over the place, including flagship games! Twilight Princess, Metroid Prime 3 and Trilogy, Xenoblade Chronicles, Super Mario Galaxy 1 and 2, Ōkami, Sonic Colors, The Last Story, Rogue Squadron III (of course), Donkey Kong Country Returns, Shadow the Hedgehog, and dozens more all use this effect, either in specific areas or throughout the whole game!

How the effect is built by the game engine is fairly straightforward - it's just smart artistry combined with the brute force blending power of the Flipper/Hollywood. To explain, let's walk through how Prime 3 does it.

  • After primary rendering is done, the game has a whole frame in memory, sans the bloom and HUD and a few other bits.
  • Then, it renders an quarter resolution EFB Copy of the screen, but samples the "emissions textures" ✱ instead of diffuse textures.
  • Prime 3 darkens the emissions EFB Copy, then it creates a slightly offset duplicate, which it dims and blurs. It does this six times, three offset copies to right and three to the left, while increasing dimming as the copies move away from center.
  • It additively merges all these EFB Copies together, dims it, then repeats the offset duplication step again but vertically.
  • Finally, Prime 3 additively blends the completed bloom image over the screen, and then renders the HUD and other remaining bits to finish.

Here are all of those steps as shown by our FIFO Player one after another, slowed down and enlarged for your viewing convenience.

...But there is trouble for Dolphin lurking in this bloom effect. Sharp-eyed readers may have noticed that the demonstration images above are all 1x Native. What happens when we increase the internal resolution in Dolphin?

We can see duplicate copies of the lights all over the place!

What is going wrong here? The blurring. These games blur the bloom EFB Copies by an arbitrary value, a number with no relation to the rendered screen that the developers hand-calibrated for a 480p image. Since it's just a number, one of the thousands of numbers spread throughout the game's code, Dolphin has no awareness of this arbitrary value and cannot change it. So when Dolphin raises the resolution of the EFB Copies with Scaled EFB Copies, the bloom is no longer blurred enough for the new higher resolution, exposing the layers that compose the bloom.

And Dolphin largely hasn't had a way to deal with this. For about a decade, the only options players had were to play a game with fake HDR bloom at 1x Native... or live with this.

Frustrated by this reality, savvy users began creating "No Bloom" Action Replay codes. Removing the bloom altogether certainly removes the broken effect, but it achieves that by outright removing a feature of the game's lighting. It could never look right.

It was quickly realized that a better solution was to keep the bloom EFB Copies at native resolution while the rest of the game could run at higher resolutions. "Native Bloom" experiments worked decently well, improving on the bloom separation while roughly maintaining the correct look of the game... until the player moved.

And... that's it. If you wanted to play one of these games in Dolphin 2603, those were your options. It wasn't great.

Enter iwubcode. They have been working on their Graphics Mods system for a while now, slowly building and expanding its capabilities over the past few years. Rather than hijacking the game's code with PowerPC assembly (game patches) or general memory editing (Action Replay codes), graphics mods work inside Dolphin's rendering pipeline, altering Dolphin's output exclusively. Graphics Mods work in two parts - the action, and the target. The action is how the graphics mod should affect Dolphin's rendering pipeline, i.e. "delete an EFB Copy", while the target is the only thing that is specific to a given game, such as "this is the hash for the EFB Copy I want to remove." This is a very simple example for demonstration purposes, but Graphics Mods are able to do a lot within Dolphin's rendering system, such as apply any shader to an EFB Copy.

Early on, iwubcode implemented No Bloom and Native Bloom as graphics mod actions. Since then, iwubcode and many other contributors have been adding targets for bloom (called "bloom definitions") in game after game, with over 50 games so far! However, No Bloom and Native Bloom still have the same compromises as before - they either seriously change the look of the game, or create flashing that may be worse than the problem it's trying to solve.

But now, finally, we have a true solution with iwubcode's new graphics mod, Bloom Blurred. This mod targets the source of the bloom problem directly by making Dolphin perform its own blur on the bloom effect, one that accounts for the current resolution. With this graphics mod, fake HDR bloom effects can be rendered at any internal resolution without any issues.

And thanks to all the bloom definitions that have been contributed over the past four years, Dolphin already knows the EFB Copies for the bloom effects of over fifty games. Every game that had a native bloom or no bloom graphics mod now also has blurred bloom!

At long last, the crown jewels of the GameCube and Wii can shine in high definition!

To use Bloom Blurred, all you need to do is have Graphics Mods enabled, then access the properties for a game (right click > properties on desktop, long press on Android) with the Graphics Mod, and enable Bloom Blurred.

If you run into a game with a fake HDR Bloom effect that doesn't have bloom Graphics Mods available, please record the scene in a FIFO log and send it to us!

2603-379 - AudioCommon: Add individual Wiimote audio mixer by TheShrubMaster

The Wii Remote had a lot going on. It was Nintendo's Hail Mary after the GameCube floundered, and they threw a lot of things at the wall to see what stuck. While it was the motion controls, infrared pointer, and attachments like the Nunchuk that really caught on, there were even more features in the legendary controller that didn't take the world by storm.

Case in point: the Wii Remote's speaker. Having a speaker built into the controller allowed games to do cool things like send an audio cue to a specific player, or have sound from your weapon come from near you to add immersion. It's a really cool feature, and while speakers didn't become a standard controller feature the way motion controls have, the idea has continued in various forms to this day, from the speaker in the DualSense to haptic audio in Nintendo Switch 1/2 controllers and the Steam Controllers.

However, this early implementation was... not very good. The Wii Remote's speaker is very low quality and it suffers from Bluetooth connection issues, so sound is choppy and unreliable. Because it was spotty on the best of days, most games didn't use the Wii Remote's speaker for essential audio, or if they did, they also had the ability to play it over the television speakers.

And that was how Dolphin handled speaker audio. If the player wasn't using a physical Wii Remote (via Real Wii Remote or Bluetooth Passthrough), all audio intended for the Wii Remote would be piped over the main speakers instead. But now we have another option! TheShrubMaster has added a mixer so Wii Remote speaker audio can be played over any additional speaker device, including controllers that expose an audio output!

The Wii Remote speaker mixer needs an additional audio output to do anything. USB audio devices, Bluetooth speakers/headphones, monitor speakers, or a controller with a speaker (if it exposes the audio output) can work. We haven't tested haptic audio, but if there is a way to expose haptics as an audio output, it should just work. Please let us know if you try that.

This feature is currently only available on our desktop Qt interface.

2603-388 - Expand and Enhance Dolphin's Cropping Capabilities by adamscott

Over ten years ago, Dolphin stopped assuming games were 4:3 or 16:9, and actually began to emulate the weird arbitrary analog aspect ratios of GameCube and Wii games. However, we then had to decide how to handle the small mismatch with your screen's aspect ratio. After some deliberation, we decided that by default, Dolphin will show everything the game renders and have tiny black bars if required. But if desired, the user could turn on "Crop" and zoom in a tiny bit to fill their entire screen, à la overscan.

While this was fine for most games, there were many edge cases that left users wanting more out of our Crop feature.

Now you can finally do something about it! adamscott has expanded Dolphin's crop feature with custom cropping support. With this, you can crop the screen however you want!

There is nothing limiting you to removing black bars. For instance, if using NetPlay, you can crop your screen so that only your screen is visible in split-screen multiplayer. Unlike viewport cheats that some NetPlay communities have used, cropping doesn't affect the game whatsoever and doesn't risk desyncing. The downside is that menus and other parts of the game get cropped too, so you may need to enable/disable the setting while playing the game.

You can find the custom crop options in Graphics -> Advanced, in both our Qt and Android GUIs. The previous crop feature remains, but has been renamed to "Crop to Aspect Ratio".


This Release's Contributors...

Special thanks to all of the contributors that incremented Dolphin by 443 commits after Release 2603!


Android minimum version bumped to Android 7

We've covered several minimum OS version bumps here on the blog, but Android has always stayed the same, locked to Android 5 Lollipop (API level 21) since 2015! But Android's time has finally come. As of 2603-57 and the latest release with 2606, Dolphin's minimum Android version is now Android 7 Nougat (API level 24). The reason for the increase is a familiar one - the old version was preventing Dolphin from adopting new features and forced us to maintain messy code for compatibility with older Android versions.

As we always do when we bump the minimum version of an operating system, here is a graph showing the percentage of affected users, according to our analytics.

Dolphin and the Revenge of the Aggressive AI Scraper Bots

In the Dolphin 2506 Progress Report, we talked about how aggressive AI training scraper bots were effectively DDoSing our websites. This problem was mitigated with Anubis, which uses proof of work checks, cookies, and other techniques in an attempt to verify that a request is coming from a real browser before allowing it to hit our servers.

While we have deployed Anubis to our websites that are heavy on dynamic user content, like our wiki and forums, we tried to avoid deploying it to our main website to avoid unnecessary user friction. The first time that a user visits a website protected by Anubis, it shows an interstitial page, forcing users to wait as their browser crunches numbers for an unspecified amount of time. Anubis also requires cookies and even JavaScript support in the more stricter bot check modes. While it has been very effective on the sites we have deployed it on, we wanted as many people to be able to access our main website as possible, and Anubis was a little too intrusive for our liking. So, we decided to leave our main website without Anubis and see how it would cope.

Unfortunately, the AI onslaught has only gotten worse over the past year. The amount of traffic hitting our main website has continued to grow and has now become unsustainable. At one point In March, our hosting provider recommended that we upgrade to a new plan that would better suit our traffic needs. Their suggested plan was over €1,000 per year more expensive than what we were currently paying. To avoid having to upgrade while we decided on a course of action, we temporarily added strict limits on the amount of CPU that our main website could consume. While this was effective, it also significantly reduced the number of requests that the website could handle, which caused slow loading and a number of full outages throughout the subsequent weeks. It was clear that something had to change.

Bunny

When this issue was brought up in one of our chats, a former Dolphin developer suggested that we should give Bunny a try.

Bunny is a platform that offers Content Delivery Network (CDN) services. A CDN is a network of servers located all over the world that act as intermediaries between a user and our server. When a device attempts to connect to a server behind a CDN, the request first reaches a CDN server. The CDN server then reaches out to us, forwards the response to the user, and then caches the response locally. If another request comes in for the exact same page, the CDN will simply serve what it has cached instead of reaching out to our server again. With this setup, most user interactions can be served by the CDN itself, spreading out the load through a highly optimized cache network, and most importantly, keeping that load off of our server.

Bunny also offers Web Application Firewall (WAF) services. A WAF allows us to inspect all traffic that is inbound for our server and only allow requests that we deem to be acceptable. Bunny's WAF product includes bot protection, which automatically detects requests from suspicious users and challenges the user to prove that they are human. We are also making these challenges appear for all users specifically on pages that cause high server load when being scraped, like our build list pages and download pages for individual builds. Using the WAF's log inspector, we were also able to find and remove a quirk of our website's localization system that some scrapers were (accidentally) abusing to increase the load on our server.

We never thought that we would ever get into a situation where our relatively small and simple website would need a CDN or a WAF. CDNs are more often used by websites that need to deliver a lot of data fast (like Netflix, for example), and our website hasn't been a target for any kind of abuse that necessitates a WAF until recently. But the Internet has changed significantly since we first launched our website in 2012. We are now being forced to adapt to a new reality where bots are generating more traffic on the Internet than humans.

Please note that we are still tweaking and optimizing our Bunny setup. If you find anything broken on our main website, do let us know.

A Note to the Nicer Kind of Scrapers

We have noticed that there are several well-meaning bots which scrape our website to find the latest version of Dolphin. While we are trying to keep some of these bots working by adding exceptions for them in Bunny's WAF, we can't guarantee that this type of scraping will continue to function in the future.

If you are operating one of these scrapers, we highly recommend that you switch to the API endpoints used by Dolphin's auto-updater. They allow you to query the latest Dolphin version and get direct links to the build artifacts. Most importantly though, the endpoints are exempt from Bunny's bot protection.

Use the endpoint GET /update/latest/(track name) to fetch the latest Dolphin version. The beta track is for releases, and the dev track is for development builds.

{
  "shortrev": "2603a",
  "date": "2026-03-17T23:16:19.910Z",
  "hash": "5e7cc91d8c9a43ca189b288937f65c9763af9c22",
  "changelog_html": "...",
  "artifacts": [
    {
      "system": "Windows x64",
      "url": "..."
    },
    {
      "system": "Android",
      "url": "..."
    },
    ...
  ]
}

This is a sample response from the endpoint.

For more information on our updater API, please check this GitHub wiki page.

A New Iteration of Redump

Dolphin's websites are far from the only ones facing an onslaught of AI scrapers. Redump.org, which is a catalog of metadata about video game discs, has been hit so hard it often becomes completely unavailable. Dolphin's Redump integration has worked pretty well for many years, but if you use it nowadays, you might get unlucky and find that no data was returned!

Unfortunately, the only person who has direct access to the Redump.org website has been inactive for years. Not only does the site lack any kind of protection against AI scrapers as a result, but there are many other problems that have gone unaddressed: no HTTPS support, registration emails not reaching common email providers like Gmail and Hotmail, and a lack of many things that could make the process of submitting and moderating discs smoother. So the staff (absent website administrator not included) banded together and moved Redump to a new and improved website! You'll find it at the new address Redump.info.

Of course, Dolphin has been updated to match! If you go to the Verify section of a game's properties, Dolphin will now fetch information from Redump.info. It works just like before, except the site is online more often and the connection is encrypted.

A Quarter of Wii RetroAchievements

Last but not least, the RetroAchievements team has shared with us a bunch of statistics for the first three months of Wii RetroAchievement support. You can find the full statistics on their forum but here are some highlights!

To return to the Notable Changes, click or tap here.

Top Ten Games by Player Count

Game Players
Super Mario Galaxy 5408
New Super Mario Bros. Wii 4052
Mario Kart Wii 3744
Super Smash Bros. Brawl 3445
Animal Crossing: City Folk 2132
Who Wants to Be a Millioniare: 1st Edition 2034
Super Mario Galaxy 2 1816
Learning with the PooYoos: Episode 1 1805
Rhythm Heaven Fever 1772
Kirby's Return to Dream Land 1769

Top Ten Most Beaten Games

Game Times Beaten
Super Mario Galaxy 2055
Who Wants to Be a Millionaire: 1st Edition 1960
Super Smash Bros. Brawl 1830
New Super Mario Bros. Wii 1824
Learning with the PooYoos: Episode 1 1794
Pinocchio's Puzzle 1547
Thomas & Friends: Hero of the Rails 1502
Golden Balls 1300
Grill-Off with Ultra Hand! 1213
Learning with the PooYoos: Episode 3 1129

Top Ten Most Mastered Games

Game Masteries
Who Wants to Be a Millioniare: 1st Edition 1831
Learning with the PooYoos: Episode 1 1783
Pinocchio's Puzzle 1547
Thomas & Friends: Hero of the Rails 1478
Grill-Off with Ultra Hand! 1189
Golden Balls 1176
Learning with the PooYoos: Episode 3 1114
Freddi Fish: Kelp Seed Mystery 1056
Pajama Sam: Don't Fear the Dark 1031
Xmas Puzzle 942

2606
  • Support du Game Boy Player : Ajout de l'émulation du périphérique Game Boy Player pour la GameCube, permettant de jouer à des jeux Game Boy/Color/Advance via Dolphin.
  • Correction majeure pour The Key of Avalon : Implémentation complète du matériel spécifique du Triforce, rendant le jeu The Key of Avalon jouable, y compris avec jusqu’à cinq instances simultanées pour le multi-joueur.
  • Correction de sécurité (Hotfix 2606a) : Résolution de vulnérabilités critiques (fuites mémoire, débordements de tampon) dans le traitement des fichiers GCZ, DOL, ELF et LZO, ainsi que dans le module DSP-HLE.
  • Amélioration graphique majeure : Correction définitive du problème de bloom à haute résolution pour plus de 50 jeux GameCube/Wii via le système de Graphics Mods, utilisant un flou dynamique adapté à la résolution.
  • Mélangeur audio individuel pour les Wiimotes : Ajout d’un mélangeur audio pour les haut-parleurs intégrés des Wiimotes, compatible avec les périphériques audio externes (USB, Bluetooth, etc.).
  • Amélioration des capacités de recadrage : Extension des options de recadrage pour un contrôle précis, incluant un recadrage personnalisé sans affecter le jeu (utile pour le NetPlay).

Welcome to the Progress Report for Dolphin Release 2606. We usually prefer to launch toward the beginning of the month, but a slew of important, large, and technically challenging changes had us working overtime. Strap in, because we have a lot to cover!

For April Fool's we teased that Dolphin now had support for the Game Boy Player, but the joke was that it was real! We'll detail exactly how it happened and the challenges that surrounded getting the emulated hardware and software working together. The last unplayable Triforce game, The Key of Avalon, no longer has that title! It is now functional in Dolphin, supporting up to five instances of the emulator together for 4 player (and a server) action. And Graphics Mods quietly fixed a major visual issue at high resolution that has plagued many flagship games for Dolphin's entire existence!

All of that and more in this Dolphin Progress Re-

✱ knock knock knock ✱

Huh, someone's at the door. Could you get that?

That's right! Since the last Dolphin Progress Report, RetroAchievements support has come to Wii games. You can now waggle your way up the leaderboard! We'll go over some statistics of the launch in a section down below, which you can reach with this handy link!

Without further ado, let's get to the Notable Changes for Dolphin 2606!


Hotfix Release 2606a

We released Dolphin 2606a on 11 August 2026 with some important security patches and a fix for Wii save states. You can find the full change log below.

  • Fixed several heap overflow bugs when reading a malformed GCZ file. (GHSA-7pvc-j9pm-c2rp)
  • Fixed a heap information disclosure bug when reading a malformed DOL file. (GHSA-27c8-xjgc-74mj)
  • Fixed several bugs where malformed ELF files can read and write outside of a buffer.
  • Fixed a buffer overflow when receiving a malformed LZO block during NetPlay save synchronization.
  • Fixed a bug in DSP-HLE where software using the AX μcode can write outside the bounds of a buffer in host memory. (GHSA-4q28-hhjv-hf3f)
  • Fixed several bugs in DSP-HLE where software using the Zelda μcode can read and write outside the bounds of buffers in host memory. (GHSA-983q-fjjx-96h3)
  • Fixed a bug where the /dev/net/ip/top IOS device can leak uninitialized host memory to the guest. (GHSA-5fqv-9qrg-gm4j)
  • Fixed an issue where loading save states for Wii software can fail when the software has open files.
  • Added a flag to enable CCache in the macOS universal binary build script.

Notable Changes

All changes below are available in Release 2606.

2603-175 - HW: Game Boy Player Support by Billiard and endrift

The Game Boy family of handhelds are legends of a bygone era. Under the crushing weight of incredibly primitive technology, Nintendo chose to focus on portability and great games rather than pushing the latest and greatest hardware. They were right. The Game Boy line outsold every single competitor they ever faced!

However, as great games accumulated on the platform, demand began to build for a way to play them on nicer, larger, lit screens. Nintendo eventually answered it with the Super Game Boy for the Super Famicom/Super Nintendo, and its Advance'd successor, the Game Boy Player for the Nintendo GameCube.

These devices were literally Game Boys without a screen that plugged into a home console, transmitting audio and video to the host console and receiving input from its controller. Software running on the host console would handle interfacing between the two systems and sometimes could add additional features if a game supported it.

We imagine that Nintendo chose to use actual Game Boy hardware because of the difficulty of making a general-purpose software emulator. The perfect demonstration of this is a third-party competitor to the Game Boy Player, the Advance Game Port, which attempted just that! By creating a Game Boy Advance emulator, Datel was able to ship a lower cost way to play GBA games on a GameCube. It was very ahead of its time, but also very flawed.

Nintendo showed that they could do emulation better on a per-game basis with titles like Pokémon Box, but they didn't see it as a plausible solution for the entire library. By shipping actual GBA hardware, the Game Boy Player was able to bypass all performance and compatibility concerns.


Being a peripheral for the GameCube, emulating the Game Boy Player has always been in the back of our minds. There was even an feature request for it for over 16 years! But it languished on the issue tracker and became the oldest open issue for one simple reason: emulating the Game Boy Player would essentially mean emulating a Game Boy Advance (which potentially involves making a new GBA emulator from scratch) and how it communicates to the GameCube. There was no way anyone would be willing to volunteer the gargantuan effort necessary just for an amusing curiosity.

Ultimately, the feature request was accepted, but there was really no path forward for it back then. We just recommended that users use one of the many available GB/GBC/GBA emulators already available, and figured that would be the end of it. They could even use the Advance Game Port in Dolphin if they really needed to run GBA games in Dolphin, as that peripheral has been partially supported since the 4.0 era.

For the longest time, the feature request was completely dormant, until around five years ago. Support for the Game Boy Player became a bit more realistic when mGBA was integrated into Dolphin. It was the ultimate solution to emulating the Game Boy Advance connectivity features found in some GameCube games, fixing all of the synchronization and communication issues that had plagued the feature for years in one fell swoop. With this, the tables had turned on Game Boy Player emulation. Couldn't we just use the integrated mGBA to emulate the Game Boy Player hardware?

The answer was yes, and endrift got to work on a Game Boy Player implementation in Dolphin! However, for various reasons, the project stalled out. And so it sat as years went by, forgotten by everyone... except the users who would occasionally ask us why we teased it as coming soon at the end of the integrated mGBA article. Oops.

Fast forward to 2026, and in the waning days of March, Billiard stumbled upon endrift's mostly-finished Game Boy Player project, and had an idea. A wonderful, awful idea: wouldn't it be funny to complete the work and add Game Boy Player support to Dolphin on April Fools' Day? With just days until the first of April, the plan rapidly unfurled and developers pounced on the code, rushing to polish things up for a quick pull request, review, test, and merge. Game Boy Player support ended up being merged a few hours into April Fools' Day.


Post by @dolphin@dolphin-emu.org
View on Mastodon

The final part of the gag was this image, which we posted without explanation on our social media and Discord on the first day of April. Watching the confusion and disbelief give way to excitement was delightful.


While we did a lot of testing to make sure Game Boy Player support was working, when legendary GameCube sage extrems started typing in our developer chat shortly after the pull request was merged, we knew we had !#@%ed up. Not only are they a living reference book for GameCube hardware, they are also the author of the definitive Game Boy Player homebrew software, Game Boy Interface (GBI). And Game Boy Interface exposed a lot of problems in Dolphin's Game Boy Player implementation.

How did we miss this? During the rush to polish and test the code, we primarily used the official Game Boy Player Start-Up Disc. That software heavily processes everything from the Game Boy Advance hardware, crushing its video contrast and applying filters to its audio. The processing was so heavy that the audio issues went unnoticed during our rushed testing - the audio sounded a little muddy rather than piercing.

In all honesty, Game Boy Player support really should have gone through a lengthy review process to allow people like endrift and extrems to test and comment heavily on the code and implementation. But if we did that, it probably would have just sat around in our open pull requests and ended up bitrotting again. By pushing things straight to production, we forced ourselves into the position of needing to fix the issues fast.

And after at least a few very minor fixes and improvements, the situation wasn't nearly as dire.

All of that work has paid off. As Game Boy Player support enters a Dolphin release and sees wider availability, we think it is ready.

To use the Game Boy Player in Dolphin, simply load a Game Boy game into the Game Boy Player via the "Game Boy Player ROM" setting in our GUI, then run the Game Boy Player Start-Up disc or Game Boy Interface. That's it!

You can find the Game Boy Player ROM setting within the GameCube settings.

And that's all there is to it. Dolphin will automatically attach the Game Boy Player hardware when necessary through INI settings. If desired, users can manually attach the emulated Game Boy Player by adding HSPDevice = 2 under [Core] in Dolphin.ini or a GameINI. This should do nothing to actual GameCube games though. ...Probably.

Note: For importing/exporting saves from other Game Boy emulators, the Game Boy Player technically counts as GBA slot 5 in Dolphin (after the 4 Integrated GBAs) and will load saves that have "-5" appended to them.


Now, we need to take a moment to go over the limitations of our Game Boy Player support.

Dolphin is not a Game Boy emulator; we emulate the GameCube, Wii, and Triforce. Our integrated GBA is only there to support things that a GameCube can do, such as connecting a Game Boy Advance to the controller port in supported games, or attaching a Game Boy hardware peripheral and funneling its audio and video to a large screen. As such, we are not trying to replicate every part of the Game Boy experience. We are only trying to recreate the Game Boy Player experience specifically, along with all of its quirks.

Game Boy Player support in Dolphin should be considered a curiosity rather than the premier way to run these handheld games in an emulator. Not only does Dolphin have much higher system requirements, but dedicated Game Boy emulators will provide a superior experience in almost every way, with better fitting UIs and support for many more Game Boy features. They also don't need additional software to use their Game Boy hardware. But if you have a Game Boy Player and Start-Up Disc lying around and desire some nostalgic fun, or want to explore the Game Boy Player experience with GBI in Dolphin, or if you just really need those sweet borders (we get it), Dolphin's Game Boy Player emulation is for you.

2603-37 and 2603-100 - Triforce: Implement Necessary Hardware for The Key of Avalon by Billiard and Crediar

The Key of Avalon games on the Triforce represent an incredible emulation challenge unlike anything else that Dolphin has encountered before. And it's not because the game itself is difficult to run; at its core, it's a relatively simple game to emulate. There's no crazy graphical effects, wacky CPU tricks, or any MMU manipulation. It's just a basic game.

The problem we encountered was that this game is so rare that we were never able to actually get our hands on the cabinets, only the GD-ROMs that the games came on. And this is a pretty big problem, because the unique hardware was the whole point of the game - four satellite Triforces with touchscreens and card readers that communicated with a central Triforce connected to a large screen to allow for multiplayer trading card monster battling in full 3D!

The biggest hurdle was the touchscreens inside the pedestals. They were completely foreign to anything we've ever seen, Triforce or GameCube! As it became increasingly clear that we may never get a chance to see the real hardware, we employed the tried and true strategy of "poke at it until you find something". It's not a particularly efficient way forward, but it was the only option available. Any signs of life moved us closer, and after a few weeks of throwing stuff at the wall, we eventually made a breakthrough. We had stumbled across the Elo SmartSet Data Protocol for touchscreens, which ended up being similar to the protocol the game actually uses. That lead didn't get us all the way there, but it was close enough that we could get to the finish line on our own.

Finally, we could push that "START" button on the touchscreen and go in-game... right?

After all of the work to get the touchscreen functional, this was a heartbreaking moment. However, it wasn't all bad. We could finally access the game's tutorial if we don't insert an IC Card. This allowed us to reach some delicious scripted gameplay and told us that we couldn't be that far away.

The problem was that we didn't know exactly what was causing the hang. There could be more oddities with the touchscreen, problems with the deck/card readers, and it also had to communicate with a server in order to proceed to gameplay. Given that the tutorial didn't use any networking, the client-server networking was the first target of our attention.

As detailed in our Rise of the Triforce article, this game uses a server-client architecture, where the touchscreen pedestals are the clients and the central Triforce is the server that actually controls the game state. We thought that perhaps there was some issue with the network, but as far as we could tell, the game wasn't even trying to communicate with the server yet. It initially synced up on power-on, but didn't spam any network commands during the hang. However, thanks to a patch that allowed us to see some debug output from the game, we were able to see some IC Card commands repeating indefinitely.

For a quick refresher, IC Cards are physical cards that can be used to save your progress in some Triforce games. We initially assumed that IC Cards would work fine in Avalon, as they already functioned properly in Virtua Striker 4 and Gekitou Pro Yakyuu. But the logs weren't lying - something was wrong, and some quick hacks to the IC Card handling code changed the behavior.

Undeterred by setback after setback, Billiard ended up rewriting a good chunk of the IC Card handling code in order to make it behave more logically. While we can't say for sure this is how real hardware would behave without having access to it, the responses make a lot more sense. But with the rewrite, we also broke both Virtua Striker 4 and Gekitou Pro Yakyuu. Great.

Thankfully, these regressions were more a consequence of rewriting a lot of code at once, and didn't end up being much more than bumps on the road. After fixing them and tightening up the code a little bit more, it was time to try The Key of Avalon once again.

Finally, it was in-game!

However, even though we could control the game, we still didn't implement enough of this game's weird hardware to make it truly playable. The game was giving us a deck of mostly starter cards and other garbage because the deck reader wasn't fully working. crediar had already started efforts on implementing the deck reader and did hardcode a list of cards to give the player. This worked for 27 of the 30 cards, and the game generously filled out the rest of the deck with starter cards. But to play a trading card game, you really need to be able to build your own deck.

An elegant solution would be to have a GUI deck editor where you can construct and load multiple decks for playing the game. However, that would be a lot of work, and we were still understanding the game at this point. Instead, Billiard added a quick and dirty method to load a deck of cards into the game using a JSON file.

{
  "cards": [
    {
      "index": 12
    },
    {
      "table": 1,
      "index": 13
    },
    {
      "index": 18,
      "quantity": 3
    }
  ]
}

This file demonstrates the different ways to set cards. Index defaults to 0, quantity defaults to 1.

With all of this, it is finally at least possible to play The Key of Avalon in Dolphin. Full matches against other players and the CPU both work, and players can save their progress to IC Cards. But this isn't to say it's a perfect experience quite yet.

Currently, entering the Segaboot menu will essentially softlock the game as it cannot reboot normally for unknown reasons. The game does not detect that prize cards have been dispensed, meaning there's a message at the top of the screen after rounds telling you to take your prize cards. This message can be reset in the Segaboot menu. We hope to fix these problems in the future.

2603-215 - Graphics Mods: Enhance Bloom by iwubcode

For a large set of GameCube and Wii games, including many flagship titles, a broken effect has significantly impaired their visual fidelity at high resolutions for Dolphin's entire existence. Yet under everyone's radar, iwubcode has slipped in a fix for this problem, quietly producing one of Dolphin's biggest graphical enhancements in years! But to explain this, we need to go over what the effect was trying to achieve in the first place.

Let's talk a bit about light.


Camera sensors and film have a limited dynamic range, so the photographer must adjust the incoming light with the aperature and shutter speed so the subject is within the dynamic range of the media (properly exposed). However, photography sensors and even film cannot capture the entire dynamic range of the world. This can result in an artifact. If a spot of light in the scene is much brighter than the dynamic range of the sensor/media, it will not only peak out the spot it falls on, but also bleed a little bit into dark areas around the light, softening and rounding highlights.

This phenomenon is the overexposure artifact halation in film and CCD saturation or "charge bleeding" in digital photography. There are differences between the two but we'll just refer to halation for convenience from here on.

Haze (atmospheric light scattering) is a visual phenomenon caused by light bouncing on particles suspended in the air or the air itself, resulting in a diffuse glow around intensely bright objects. ✱ Flare and other optical phenomenon can add glow as well.

All combined, these artifacts result in "bloom", the glow around bright objects as seen in photos.

We have all been exposed to a bazillion photos and videos from real life on a limited range display. Our brains have learned to pick up on the artifacts that brightness beyond the dynamic range creates in the camera, and given the correct context, they can interpret this as brighter than just white alone.

This illusion means that bloom is essential for making objects look bright on a standard dynamic range display.

Yet for a long time, games were not able to reproduce these artifacts. They were limited to "SDR rendering" - their engines were internally limited to the same tiny dynamic range as a typical CRT. The brightest white a game could comprehend was the same white as the screen, same with black. With this limitation, game engines could not understand dynamic range at all, let alone recreate the artifacts that result from it! This manifested in games having a flat, low-contrast, and "cartoon-background" look. Artists could still make games look amazing, of course, but due to the difficulty of manually lighting every single scene, SDR rendering's limitations still largely drove the look of lighting in the games industry.

This changed with the advent of High Dynamic Range Rendering (HDRR) in 2004. With HDR Rendering, game engines could now understand and render way beyond the limitations of SDR, and then tone map down to SDR for display. In effect, the game's camera now percieved light akin a camera looking at the real world. In-camera effects such as crushed blacks, halation, haze, flares, specular highlights, sparkles, aperture and exposure, bokeh, and more could be properly recreated in games!

The effect this had on the gaming industry was transformational. HDR Rendering has become ubiquitous, so much so that the term has largely disappeared - it's just rendering now!

So, what did all this mean for our favorite purple cube and waggle stick?

The GameCube and the Wii were built on top of ArtX graphics technology from the tailend of the 1990s. Their graphics hardware, while very capable and flexible, was fundamentally limited to SDR rendering. As HDR rendering was revolutionizing game lighting in the mid-2000s on PC and the "next generation" of consoles, GameCube and Wii games were starting to look... old fashioned. How could developers for the GameCube and Wii keep their games looking fresh?

If you don't have the tech, just art it instead!

The GameCube and Wii were not capable of understanding dynamic range, so the game engine cannot determine when a pixel is "brighter than bright" on its own. But what if we just let artists tell the game engine instead? If a texture mapped the light emission that goes beyond the standard dynamic range, an emission map if you will, then the game engine could use that information in the scene to create effects that look like HDR Rendering! Keep in mind that this isn't actually HDR Rendering, and it's limited in what it can do. For example, you can forget about dynamic lighting in a system like this, as it is by definition not dynamic. But if the game is baking all the lighting anyway, as most GameCube and Wii games did, they could use this trick to tremendous effect.

This "fake HDR bloom" showed up all over the place, including flagship games! Twilight Princess, Metroid Prime 3 and Trilogy, Xenoblade Chronicles, Super Mario Galaxy 1 and 2, Ōkami, Sonic Colors, The Last Story, Rogue Squadron III (of course), Donkey Kong Country Returns, Shadow the Hedgehog, and dozens more all use this effect, either in specific areas or throughout the whole game!

How the effect is built by the game engine is fairly straightforward - it's just smart artistry combined with the brute force blending power of the Flipper/Hollywood. To explain, let's walk through how Prime 3 does it.

  • After primary rendering is done, the game has a whole frame in memory, sans the bloom and HUD and a few other bits.
  • Then, it renders an quarter resolution EFB Copy of the screen, but samples the "emissions textures" ✱ instead of diffuse textures.
  • Prime 3 darkens the emissions EFB Copy, then it creates a slightly offset duplicate, which it dims and blurs. It does this six times, three offset copies to right and three to the left, while increasing dimming as the copies move away from center.
  • It additively merges all these EFB Copies together, dims it, then repeats the offset duplication step again but vertically.
  • Finally, Prime 3 additively blends the completed bloom image over the screen, and then renders the HUD and other remaining bits to finish.

Here are all of those steps as shown by our FIFO Player one after another, slowed down and enlarged for your viewing convenience.

...But there is trouble for Dolphin lurking in this bloom effect. Sharp-eyed readers may have noticed that the demonstration images above are all 1x Native. What happens when we increase the internal resolution in Dolphin?

We can see duplicate copies of the lights all over the place!

What is going wrong here? The blurring. These games blur the bloom EFB Copies by an arbitrary value, a number with no relation to the rendered screen that the developers hand-calibrated for a 480p image. Since it's just a number, one of the thousands of numbers spread throughout the game's code, Dolphin has no awareness of this arbitrary value and cannot change it. So when Dolphin raises the resolution of the EFB Copies with Scaled EFB Copies, the bloom is no longer blurred enough for the new higher resolution, exposing the layers that compose the bloom.

And Dolphin largely hasn't had a way to deal with this. For about a decade, the only options players had were to play a game with fake HDR bloom at 1x Native... or live with this.

Frustrated by this reality, savvy users began creating "No Bloom" Action Replay codes. Removing the bloom altogether certainly removes the broken effect, but it achieves that by outright removing a feature of the game's lighting. It could never look right.

It was quickly realized that a better solution was to keep the bloom EFB Copies at native resolution while the rest of the game could run at higher resolutions. "Native Bloom" experiments worked decently well, improving on the bloom separation while roughly maintaining the correct look of the game... until the player moved.

And... that's it. If you wanted to play one of these games in Dolphin 2603, those were your options. It wasn't great.

Enter iwubcode. They have been working on their Graphics Mods system for a while now, slowly building and expanding its capabilities over the past few years. Rather than hijacking the game's code with PowerPC assembly (game patches) or general memory editing (Action Replay codes), graphics mods work inside Dolphin's rendering pipeline, altering Dolphin's output exclusively. Graphics Mods work in two parts - the action, and the target. The action is how the graphics mod should affect Dolphin's rendering pipeline, i.e. "delete an EFB Copy", while the target is the only thing that is specific to a given game, such as "this is the hash for the EFB Copy I want to remove." This is a very simple example for demonstration purposes, but Graphics Mods are able to do a lot within Dolphin's rendering system, such as apply any shader to an EFB Copy.

Early on, iwubcode implemented No Bloom and Native Bloom as graphics mod actions. Since then, iwubcode and many other contributors have been adding targets for bloom (called "bloom definitions") in game after game, with over 50 games so far! However, No Bloom and Native Bloom still have the same compromises as before - they either seriously change the look of the game, or create flashing that may be worse than the problem it's trying to solve.

But now, finally, we have a true solution with iwubcode's new graphics mod, Bloom Blurred. This mod targets the source of the bloom problem directly by making Dolphin perform its own blur on the bloom effect, one that accounts for the current resolution. With this graphics mod, fake HDR bloom effects can be rendered at any internal resolution without any issues.

And thanks to all the bloom definitions that have been contributed over the past four years, Dolphin already knows the EFB Copies for the bloom effects of over fifty games. Every game that had a native bloom or no bloom graphics mod now also has blurred bloom!

At long last, the crown jewels of the GameCube and Wii can shine in high definition!

To use Bloom Blurred, all you need to do is have Graphics Mods enabled, then access the properties for a game (right click > properties on desktop, long press on Android) with the Graphics Mod, and enable Bloom Blurred.

If you run into a game with a fake HDR Bloom effect that doesn't have bloom Graphics Mods available, please record the scene in a FIFO log and send it to us!

2603-379 - AudioCommon: Add individual Wiimote audio mixer by TheShrubMaster

The Wii Remote had a lot going on. It was Nintendo's Hail Mary after the GameCube floundered, and they threw a lot of things at the wall to see what stuck. While it was the motion controls, infrared pointer, and attachments like the Nunchuk that really caught on, there were even more features in the legendary controller that didn't take the world by storm.

Case in point: the Wii Remote's speaker. Having a speaker built into the controller allowed games to do cool things like send an audio cue to a specific player, or have sound from your weapon come from near you to add immersion. It's a really cool feature, and while speakers didn't become a standard controller feature the way motion controls have, the idea has continued in various forms to this day, from the speaker in the DualSense to haptic audio in Nintendo Switch 1/2 controllers and the Steam Controllers.

However, this early implementation was... not very good. The Wii Remote's speaker is very low quality and it suffers from Bluetooth connection issues, so sound is choppy and unreliable. Because it was spotty on the best of days, most games didn't use the Wii Remote's speaker for essential audio, or if they did, they also had the ability to play it over the television speakers.

And that was how Dolphin handled speaker audio. If the player wasn't using a physical Wii Remote (via Real Wii Remote or Bluetooth Passthrough), all audio intended for the Wii Remote would be piped over the main speakers instead. But now we have another option! TheShrubMaster has added a mixer so Wii Remote speaker audio can be played over any additional speaker device, including controllers that expose an audio output!

The Wii Remote speaker mixer needs an additional audio output to do anything. USB audio devices, Bluetooth speakers/headphones, monitor speakers, or a controller with a speaker (if it exposes the audio output) can work. We haven't tested haptic audio, but if there is a way to expose haptics as an audio output, it should just work. Please let us know if you try that.

This feature is currently only available on our desktop Qt interface.

2603-388 - Expand and Enhance Dolphin's Cropping Capabilities by adamscott

Over ten years ago, Dolphin stopped assuming games were 4:3 or 16:9, and actually began to emulate the weird arbitrary analog aspect ratios of GameCube and Wii games. However, we then had to decide how to handle the small mismatch with your screen's aspect ratio. After some deliberation, we decided that by default, Dolphin will show everything the game renders and have tiny black bars if required. But if desired, the user could turn on "Crop" and zoom in a tiny bit to fill their entire screen, à la overscan.

While this was fine for most games, there were many edge cases that left users wanting more out of our Crop feature.

Now you can finally do something about it! adamscott has expanded Dolphin's crop feature with custom cropping support. With this, you can crop the screen however you want!

There is nothing limiting you to removing black bars. For instance, if using NetPlay, you can crop your screen so that only your screen is visible in split-screen multiplayer. Unlike viewport cheats that some NetPlay communities have used, cropping doesn't affect the game whatsoever and doesn't risk desyncing. The downside is that menus and other parts of the game get cropped too, so you may need to enable/disable the setting while playing the game.

You can find the custom crop options in Graphics -> Advanced, in both our Qt and Android GUIs. The previous crop feature remains, but has been renamed to "Crop to Aspect Ratio".


This Release's Contributors...

Special thanks to all of the contributors that incremented Dolphin by 443 commits after Release 2603!


Android minimum version bumped to Android 7

We've covered several minimum OS version bumps here on the blog, but Android has always stayed the same, locked to Android 5 Lollipop (API level 21) since 2015! But Android's time has finally come. As of 2603-57 and the latest release with 2606, Dolphin's minimum Android version is now Android 7 Nougat (API level 24). The reason for the increase is a familiar one - the old version was preventing Dolphin from adopting new features and forced us to maintain messy code for compatibility with older Android versions.

As we always do when we bump the minimum version of an operating system, here is a graph showing the percentage of affected users, according to our analytics.

Dolphin and the Revenge of the Aggressive AI Scraper Bots

In the Dolphin 2506 Progress Report, we talked about how aggressive AI training scraper bots were effectively DDoSing our websites. This problem was mitigated with Anubis, which uses proof of work checks, cookies, and other techniques in an attempt to verify that a request is coming from a real browser before allowing it to hit our servers.

While we have deployed Anubis to our websites that are heavy on dynamic user content, like our wiki and forums, we tried to avoid deploying it to our main website to avoid unnecessary user friction. The first time that a user visits a website protected by Anubis, it shows an interstitial page, forcing users to wait as their browser crunches numbers for an unspecified amount of time. Anubis also requires cookies and even JavaScript support in the more stricter bot check modes. While it has been very effective on the sites we have deployed it on, we wanted as many people to be able to access our main website as possible, and Anubis was a little too intrusive for our liking. So, we decided to leave our main website without Anubis and see how it would cope.

Unfortunately, the AI onslaught has only gotten worse over the past year. The amount of traffic hitting our main website has continued to grow and has now become unsustainable. At one point In March, our hosting provider recommended that we upgrade to a new plan that would better suit our traffic needs. Their suggested plan was over €1,000 per year more expensive than what we were currently paying. To avoid having to upgrade while we decided on a course of action, we temporarily added strict limits on the amount of CPU that our main website could consume. While this was effective, it also significantly reduced the number of requests that the website could handle, which caused slow loading and a number of full outages throughout the subsequent weeks. It was clear that something had to change.

Bunny

When this issue was brought up in one of our chats, a former Dolphin developer suggested that we should give Bunny a try.

Bunny is a platform that offers Content Delivery Network (CDN) services. A CDN is a network of servers located all over the world that act as intermediaries between a user and our server. When a device attempts to connect to a server behind a CDN, the request first reaches a CDN server. The CDN server then reaches out to us, forwards the response to the user, and then caches the response locally. If another request comes in for the exact same page, the CDN will simply serve what it has cached instead of reaching out to our server again. With this setup, most user interactions can be served by the CDN itself, spreading out the load through a highly optimized cache network, and most importantly, keeping that load off of our server.

Bunny also offers Web Application Firewall (WAF) services. A WAF allows us to inspect all traffic that is inbound for our server and only allow requests that we deem to be acceptable. Bunny's WAF product includes bot protection, which automatically detects requests from suspicious users and challenges the user to prove that they are human. We are also making these challenges appear for all users specifically on pages that cause high server load when being scraped, like our build list pages and download pages for individual builds. Using the WAF's log inspector, we were also able to find and remove a quirk of our website's localization system that some scrapers were (accidentally) abusing to increase the load on our server.

We never thought that we would ever get into a situation where our relatively small and simple website would need a CDN or a WAF. CDNs are more often used by websites that need to deliver a lot of data fast (like Netflix, for example), and our website hasn't been a target for any kind of abuse that necessitates a WAF until recently. But the Internet has changed significantly since we first launched our website in 2012. We are now being forced to adapt to a new reality where bots are generating more traffic on the Internet than humans.

Please note that we are still tweaking and optimizing our Bunny setup. If you find anything broken on our main website, do let us know.

A Note to the Nicer Kind of Scrapers

We have noticed that there are several well-meaning bots which scrape our website to find the latest version of Dolphin. While we are trying to keep some of these bots working by adding exceptions for them in Bunny's WAF, we can't guarantee that this type of scraping will continue to function in the future.

If you are operating one of these scrapers, we highly recommend that you switch to the API endpoints used by Dolphin's auto-updater. They allow you to query the latest Dolphin version and get direct links to the build artifacts. Most importantly though, the endpoints are exempt from Bunny's bot protection.

Use the endpoint GET /update/latest/(track name) to fetch the latest Dolphin version. The beta track is for releases, and the dev track is for development builds.

{
  "shortrev": "2603a",
  "date": "2026-03-17T23:16:19.910Z",
  "hash": "5e7cc91d8c9a43ca189b288937f65c9763af9c22",
  "changelog_html": "...",
  "artifacts": [
    {
      "system": "Windows x64",
      "url": "..."
    },
    {
      "system": "Android",
      "url": "..."
    },
    ...
  ]
}

This is a sample response from the endpoint.

For more information on our updater API, please check this GitHub wiki page.

A New Iteration of Redump

Dolphin's websites are far from the only ones facing an onslaught of AI scrapers. Redump.org, which is a catalog of metadata about video game discs, has been hit so hard it often becomes completely unavailable. Dolphin's Redump integration has worked pretty well for many years, but if you use it nowadays, you might get unlucky and find that no data was returned!

Unfortunately, the only person who has direct access to the Redump.org website has been inactive for years. Not only does the site lack any kind of protection against AI scrapers as a result, but there are many other problems that have gone unaddressed: no HTTPS support, registration emails not reaching common email providers like Gmail and Hotmail, and a lack of many things that could make the process of submitting and moderating discs smoother. So the staff (absent website administrator not included) banded together and moved Redump to a new and improved website! You'll find it at the new address Redump.info.

Of course, Dolphin has been updated to match! If you go to the Verify section of a game's properties, Dolphin will now fetch information from Redump.info. It works just like before, except the site is online more often and the connection is encrypted.

A Quarter of Wii RetroAchievements

Last but not least, the RetroAchievements team has shared with us a bunch of statistics for the first three months of Wii RetroAchievement support. You can find the full statistics on their forum but here are some highlights!

To return to the Notable Changes, click or tap here.

Top Ten Games by Player Count

Game Players
Super Mario Galaxy 5408
New Super Mario Bros. Wii 4052
Mario Kart Wii 3744
Super Smash Bros. Brawl 3445
Animal Crossing: City Folk 2132
Who Wants to Be a Millioniare: 1st Edition 2034
Super Mario Galaxy 2 1816
Learning with the PooYoos: Episode 1 1805
Rhythm Heaven Fever 1772
Kirby's Return to Dream Land 1769

Top Ten Most Beaten Games

Game Times Beaten
Super Mario Galaxy 2055
Who Wants to Be a Millionaire: 1st Edition 1960
Super Smash Bros. Brawl 1830
New Super Mario Bros. Wii 1824
Learning with the PooYoos: Episode 1 1794
Pinocchio's Puzzle 1547
Thomas & Friends: Hero of the Rails 1502
Golden Balls 1300
Grill-Off with Ultra Hand! 1213
Learning with the PooYoos: Episode 3 1129

Top Ten Most Mastered Games

Game Masteries
Who Wants to Be a Millioniare: 1st Edition 1831
Learning with the PooYoos: Episode 1 1783
Pinocchio's Puzzle 1547
Thomas & Friends: Hero of the Rails 1478
Grill-Off with Ultra Hand! 1189
Golden Balls 1176
Learning with the PooYoos: Episode 3 1114
Freddi Fish: Kelp Seed Mystery 1056
Pajama Sam: Don't Fear the Dark 1031
Xmas Puzzle 942

Bluetooth Passthrough does have some downsides, though. Because the emulated Wii has full control over the Bluetooth adapter, you can't connect other Bluetooth devices like headphones or controllers unless you have a second adapter. In addition, certain Dolphin features are not accessible when using Bluetooth Passthrough, such as save states. Windows users are also required to install a special driver to override the manufacturer's driver and prevent it from loading. Despite these problems, however, Bluetooth Passthrough remains a popular feature because of all the benefits it brings.

Unfortunately, we've recently observed that more and more modern Bluetooth adapters aren't compatible with Bluetooth Passthrough, and it wasn't immediately apparent why.

While helping users out in our Discord, Billiard noticed that many of the support requests seemed to be coming from users with Bluetooth adapters built off the Realtek RTL8761 chipset. Once he got his hands on one for himself, Billiard quickly found the problem. This particular chipset expects to have its firmware loaded by the operating system every time it is connected. When Dolphin has control over the adapter during Bluetooth Passthrough, the operating system doesn't get the chance to load that necessary firmware!

Billiard took action to rectify this issue. First, 2506-171 overhauled the Bluetooth Passthrough code to improve general performance through better timing of packets and other minor tweaks. These changes affect every adapter. Most importantly, it also separated Dolphin's emulation logic from the LibUSB logic as a step toward fixing the Realtek firmware problem.

2506-330 built upon the previous changes to add the ability to load Realtek firmware. When attempting to use a Realtek adapter with Bluetooth Passthrough for the first time, you will be prompted to allow Dolphin to download the appropriate firmware file from the internet. Once the firmware is downloaded, it is silently loaded on the device, just like the operating system would do.

This brings what was previously an entirely unsupported chipset to work with Bluetooth Passthrough.

While fixing a single chipset might not seem significant, given how common it is in modern Bluetooth adapters, this fix has greatly improved Bluetooth Passthrough's overall compatibility. Popular adapters like the TP-Link Bluetooth 5.3 Nano and Asus USB-BT500 can now work with Bluetooth Passthrough!

2506-121 - DolphinQt/InputCommon: Make the "Calibrate" button also map inputs by Billiard

You may have noticed our desktop settings UI has been changing over the past few months. This is part of a broader overhaul that we will detail further in the future.

In the meantime, a new feature in Dolphin's Qt GUI is the "Map and Calibrate" button.

The Map and Calibrate option lets you map and calibrate your joystick simultaneously—just click and rotate the stick clockwise a couple of times. For most joysticks, you'll achieve perfectly matched ranges to those of a GameCube Controller, Classic Controller, or Nunchuck with a single click and a spin. For users requiring specialized setups, manual mapping followed by calibration is still possible.

2506-62 - VideoCommon: Add Resource Manager by iwubcode

HD Texture Packs are one of the most impactful improvements you can apply to GameCube and Wii games. Constrained by storage and memory, developers at the time prioritized texture resolution for key assets like heroes and main locations, often leaving background elements with N64-level detail. These choices work fine at SD resolutions, but when upscaled to 4K, low-resolution textures become noticeably prominent.

As a result, it’s no surprise that Dolphin has supported HD textures since 2009, and the feature has continued to refine over the years.

We've added several texture formats (many that can run natively on the GPU itself without conversion, optional preloading, resource packs, and reduced duplication through smarter handling of mipmaps and more over the last fifteen years.

The biggest fundamental change to how custom textures were loaded was just two years ago, when we quietly added a new asset management system that allowed for loading textures without blocking emulation. This change didn’t really amount to much, except that now instead of performance stuttering while textures are loaded, any custom textures that weren’t loaded in time would pop-in. Depending on your computer, you might not have noticed this change at all!

The resource manager is a further evolution of this change. It further allows Dolphin to manage custom textures to ensure that HD Texture Packs can work on a wider variety of hardware. The resource manager tracks the requests per frame and orders them based on what was requested last. The newest requests get serviced first, leading to better perceived performance for loading textures. The resource manager also tracks memory usage and can purge textures that haven’t been used as much if the machine is low on RAM in order to prevent out-of-memory issues.

One more bonus is that custom texture loading is now multithreaded. This ensures that texture loading no longer needs to borrow resources from Dolphin’s main CPU emulation thread and can run on its own CPU core. This greatly improves the performance of loading many textures at once and reduces pop-in on modern multi-core CPUs.

Combined with the other improvements the resource manager brings, HD Texture Packs should no longer cause performance issues in most cases.

2506-33 - Add Option to Pursue Accurate Overall Runtime by Billiard

One of the reasons that various Mario Kart Wii online services struggle with Dolphin users isn't just the ease with which it enables cheating, but that even innocent users can also cause issues. While you might think that lagging during a race would be a disadvantage, due to the way Mario Kart Wii operates, it can actually put you ahead. During the race, you'll be in a lower position, collecting better items and avoiding blue shells. But when you finish, the game only uses your final time to determine your finish position. If you lagged for three seconds throughout the race and visually finished two seconds behind the leader, you will end up winning the race on the results screen. Yikes.

Modern Mario Kart Wii fan servers have protections against this, but it remains an annoying behavior and can definitely cause problems in other games that lack patches to address Dolphin's quirks.

For this situation and others like it, Billiard has introduced a new option to help mitigate small lag spikes. Correct Time Drift allows Dolphin to speed up after a lag spike to keep Dolphin aligned with real-time progression.

If something causes emulation to slow down or stutter for a short period, Dolphin will use the next opportunity to speed up and catch back up to real time. For temporary issues like network packet drops during NetPlay, shader compilation, and JIT cache flushing, this feature can keep Dolphin locked to the actual time. Outside of certain online games like Mario Kart Wii, this can also be useful for speedrunners to ensure that the emulated time is synchronized to the real time even during any minor bobbles in emulation.

Note that some actions will cause Dolphin to abandon time correction. If you disable the speed limiter (holding TAB by default) at any point, Dolphin will not try to slow down for the duration that you are bypassing the speed limit and will choose a new "par time" once the limit is restored.


This Release's Contributors...

Special thanks to all of the contributors who incremented Dolphin by 433 commits after Release 2506!



A Dual Core Correction

It has become established within the Dolphin project that Dual Core mode is a hack. It's well known that it is unstable, current developers have called it a hack, we've said it repeatedly here on the blog, and ector (one of Dolphin's founders) has said he regretted Dual Core. That really sounds like a hack! However, in the process of writing this article, we consulted with retired Dolphin developers about Dual Core, and had an enlightening conversation.

They told us that Dual Core mode is not a hack. In fact, Dual Core mode is more like the original hardware than Single Core mode. And yet, Single Core mode is more accurate.

To explain this, we need to go into detail on what Dual Core mode and Single Core mode actually do.

Processor Processing

The following are the processors on the GameCube, and how Dolphin emulates them.

The Wii does have some differences, but most of them are minor outside of the addition of the Starlet processor. For simplicity, we will be focusing on the GameCube throughout this section.

  • Central Processing Unit - A single PowerPC CPU core. The emulated software runs within this core, and Dolphin, for the most part, isn’t aware of what’s happening inside. To Dolphin, everything the emulated CPU does is just instructions. A lot of instructions that pass by very very fast. Dolphin translates the instructions (via recompilation or interpretation) into something the host CPU can understand, but for the most part it doesn’t know what they are doing.
    • NOTE: Dual Core mode does not split the emulated CPU across two host CPU cores. We can't do that.
  • Graphics Processing Unit
    • Command Processor - A simple integrated circuit that sits between the CPU and the GPU. The CPU creates lists of commands for the GPU and sends them to the command processor, then continues with its tasks. The command processor parses the command list and prepares the GPU to perform the work, such as configuring the TEV unit and setting up registers. Dolphin emulates the command processor, and assuming a hardware graphics backend is being used, it converts the GameCube GPU commands into commands for the selected graphics API (Vulkan, OpenGL, etc) and then passes the work to the host's graphics driver.
    • Rendering Components (TEV/XF/EFB/etc) - Continuing from above, once the host GPU driver has received commands, it converts them into the specific instructions and shaders that will actually run on the host GPU. This is still work for the host CPU, but it is done outside of Dolphin. The actual rendering, and thus most of the GPU emulation, occurs on the host GPU (when using a hardware graphics backend).
  • Digital Signal Processor - A Macronix DSP that handles various audio processing tasks.
DSP-HLE is quite lightweight as it technically emulates the results of the DSP rather than the processor itself. DSP-LLE, on the other hand, actually emulates this processor and is quite heavy.

All of the processors listed above work asynchronously - each processor performs its work independently of all the others. To coordinate and prevent race conditions, synchronization points must be used, communicating things like "VBlank just happened and we should start a new frame", or "there is work for you waiting in this memory region", or "the work I was assigned is now completed and I am waiting for more".

What is analogous to this in a modern PC? A multi-core processor. While cores may share some resources, they are more or less separate processors that operate asynchronously, and multithreaded applications need to synchronize across their threads. So of course, if a programmer wants to emulate a console with several processors running asynchronously, their very first thought would be to have separate threads for each emulated processor. This makes the host hardware behave like the original hardware, plus those threads can spread out across the many CPU cores of the host, better utilizing the host hardware and easing the emulator's CPU requirements. Makes perfect sense!

That's Dual Core mode. ﹡

Dual Core mode isn't a hack, because it closely mimics the original hardware!

Dual Core, Dual Problems

But then, why is Dual Core so unstable? There are two reasons for that.

Game Development is Hard

The GameCube does not have an operating system. While it does have SDKs and various Nintendo-provided assistance, ultimately, games run on the bare metal, and they have complete control over the system. They can do whatever they want.

And the software controls synchronization.

A game following best practices will set a synchronization point whenever there is potential for a race and will not ignore interrupts that the hardware sends back. If done correctly, the asynchronous processors cannot race at all.

Games made by Nintendo's development teams, such as Super Mario Galaxy, are rock solid ﹡ in Dual Core mode because they safely and thoroughly synchronize. But game development is hard, and "best practices" are an early casualty of crunch. All too often games run the hardware a little loose. For example, a common occurrence is that the game will have the CPU send work to the GPU before the game has completely scheduled all of the GPU's resources. If the CPU can return and fill out the rest of those resources before the command processor and GPU are finished with the work they were already assigned, this won't cause any problems. And since each GameCube should behave more or less identically to any other GameCube, if it is fine on the developer's GameCube, it should be fine on any GameCube. However, this is a race condition, and coding like this is asking for trouble. And unfortunately for us...
Your Computer Is Not A GameCube

In Dual Core mode, the emulated processors are spread across the host CPU cores, and Dolphin synchronizes at least as much as the original console. However, the time it takes for the host cores to do work could be literally anything. Modern CPUs adjust clock speeds on a per-core basis and change their frequency all the time based on heuristics entirely outside of our control, the operating system will constantly move our threads around the host CPU and can decide to put one of our threads to sleep without warning, the CPU could be heterogeneous and another program competing for resources could convince the OS to elevate one of its threads to the big cores and kick one of our threads to the little cores, and so on. Race conditions are inherently unsafe on modern hardware! Even Dolphin itself can unbalance the race.

Normal emulation scenarios, such as a large burst of shader compilation or emulation threads stalling due to saving state or capturing a screenshot, are more than enough to alter the outcome of racing threads.

So if a game relies on thread races, the predictable and consistent race they expected on the original hardware becomes an unpredictable and inconsistent race in Dolphin. And if the race's outcome differs from the original hardware, the game and/or Dolphin may crash!

And despite our many attempts, there isn't really anything we can do about it. Assuming we behave like the original hardware, that is.

The Solution: Don't Act Like A GameCube

In Single Core mode, Dolphin does not distribute the emulated processors across the host's processors. Instead, it consolidates all of those processors and emulates them in a single host CPU thread. This gives Dolphin full control over synchronization, allowing Dolphin to enforce work consumption at the same granularity as the original hardware. Even if a game runs a little too loosely, even if the host OS interferes, even if syncing with another instance of Dolphin on the other side of the world, Single Core can handle it.

This is not at all how the original hardware operates, but the result is higher accuracy and stability. The only downside, of course, is performance.

Lessons Learned

This experience has reminded us that the developers who founded Dolphin really knew their stuff. Splitting the GameCube's processors across host CPU cores is inherently risky. The fact that Dual Core was stable enough to be Dolphin's default for over fifteen years is a testament to the capabilities of Dolphin's early developers. Dual Core mode is more or less as good as this implementation can get—as our repeated failures to improve it can attest.

And Dual Core mode was extremely influential. After Dolphin went open source, it could run some games at full speed. It was extremely buggy, it required top-tier hardware of the time, and it was only a few games, but Dolphin could be used for play. That was a possibility given to us by Dual Core mode, as Single Core wouldn't reach playable speeds on high-end systems for another ten years or so. This was incredibly important in Dolphin's early days, as the ability to play attracted users, which attracted more developers, which attracted more users, giving Dolphin momentum to take off after it went open source. Dolphin would not be where it is now without Dual Core mode.

That being said, times have changed.

Our predecessors had to deal with Dual Core mode's instability to achieve playable performance, but, as we covered earlier, we don’t have to. Dual Core is no longer necessary for most of our desktop users and should no longer be the default on desktop.

So, what has changed now that we know all this? We will never refer to Dual Core mode as a hack again.

Aside: Why Not Just Synchronize More?

That is what SyncGPU does. Specifically, in addition to all the synchronization points already present in Dual Core, SyncGPU will only allow the processors to race for a certain amount of emulated time before forcing its own synchronization.

In practice, SyncGPU was neither as fast as Dual Core nor as stable as Single Core, leaving it in a position where it simply didn’t matter. But you already saw the charts.

2506a
  • Nouveau système audio Granule Synthesis : suppression des silences et des pops lors des ralentissements, sans latence ni étirement audio, avec une option pour désactiver le remplissage des trous.
  • Améliorations de la synchronisation des frames : réduction des variations de timing (variance ±0.40 ms pour V-Blank, ±0.24 ms pour Frame), améliorant la fluidité visuelle dans presque tous les jeux.
  • Prise en charge de la version minimale macOS 11 Big Sur : abandon du support de macOS 10.15 Catalina en raison de l'absence de C++20 et mise à jour de Qt vers la version 6.5 LTS.
  • Correction des builds macOS incompatibles avec NetPlay : version incorrecte attachée dans la release précédente, entraînant des problèmes de compatibilité multiplateforme.
  • Compatibilité étendue des périphériques USB : détection des contrôleurs Rock Band PlayStation 3 comme équivalents Wii, via l'option DisguisePlayStationAsWii dans Dolphin.ini.
  • Émulation Wii Speak : utilisation d’un micro standard pour les jeux compatibles, accessible via Tools > Emulated USB devices (desktop) ou Settings > Config > Wii > Emulated USB Devices (Android).

Welcome to the Dolphin Progress Report for Release 2506! As we've alluded to a few times, we've had major changes in the pipeline that we've been very excited to show off. Some of those changes are finally here! Headlining this report are major adjustments to how Dolphin handled audio lag under slowdown by default. No longer will users have to choose between high-latency audio stretching or popping when dealing with small hitches in performance thanks to the new Granule Synthesis Audio System.

If the game is already running full speed, we still have some improvements for you. Dolphin has seen a suite of frame pacing improvements that will give you a smoother experience across almost every game. And, if your system is very powerful, there are a select group of games that can now push past the 60 FPS barrier for high frame rate gaming. Before you get too excited, this feature does not work with most Nintendo developed titles and has incredibly low compatibility in general. For a list of what games support this, we'll get into it later in the report.

If you care about preserving oddball Wii add-ons, we've got you covered here too. Wii Speak emulation is finally here after an incredibly long journey. In addition, long time incompatible game The Daring Game For Girls is finally compatible with Dolphin. We'll get into that game's story and more, but first, we need to get through quite a bit of housekeeping.

The Release Hotfix Fiasco

We finally had some big enough problems in a release that we had to create a hotfix using our new versioning system. First, the macOS build for 2503 had the wrong version number attached, causing it to be incompatible with cross-platform NetPlay. We also found that GBA connectivity in compatible GameCube games was broken, and that there was a crashing bug when running Dolphin on older macOS versions. To rectify these problems, we created hotfix 2503a. However, in doing so, we inadvertently caused all development builds from that point on to take the "a" suffix. Some of our systems temporarily broke in the immediate aftermath while support for the suffix was hastily added. We technically could have removed the suffix, but we decided not to in the end because removing it would have caused even more disruption.

In future releases, if a hotfix is needed it will not apply a suffix to the development builds. This should make things easier on us and anyone else that is maintaining Dolphin builds of their own. We apologize for any inconvenience that this error has caused.

For reader convenience and future consistency, the hotfix suffix has been removed from all changes in this article.

Windows 10 minimum version bumped to 1903

Although Windows 10 will reach End of Support later this year, it continued to receive major updates up until two and a half years ago. Thanks to that, we should be able to continue supporting the decade-old operating system for many more years. However, as new APIs, standards, and compiler features appear, our minimum Windows 10 version will slowly climb. As of 2503-152, we are now taking advantage of time zone APIs that require Windows 10 version 1903, meaning that any older versions of Windows 10 are no longer supported.

The last Dolphin release to support Windows 10 versions 1703 to 1809 is 2503a, and the last development build is 2503-148.

macOS minimum version bumped to macOS 11 Big Sur

We have also increased our minimum macOS version from macOS 10.15 Catalina to macOS 11 Big Sur. Unfortunately, Catalina lacks support for some C++20 APIs that we'd like to take advantage of, so we decided to go ahead and bump our minimum macOS version to accommodate those changes. This bump will also allow us to (finally) update the Qt in our macOS builds to 6.5 LTS, which we will aim to do before the next release.

The last Dolphin release to support macOS 10.15 Catalina is 2503a, and the last development build is 2503-270.

Notable Changes

2503-51 - Granule Synthesis Audio System by samb

When reporting performance issues, sometimes users don't even realize that the game is slowing down. They instead report audio hitching or stuttering as the main issue that's bothering them. In order to provide low latency audio, Dolphin employs a ring buffer. And, as long as the game is running full speed, this buffer remains full and you'll get a constant stream of audio.

When the emulator is not running at the target frame rate, the buffer won't be filled up. And when Dolphin runs out of audio in the buffer, there will be a small gap in audio that sounds rather unpleasant.

To combat this, Dolphin has given users the ability to enable audio stretching. At the cost of higher audio latency, Dolphin can stretch the existing data in the buffer to keep audio running smoothly. For many users, the increase in audio latency is large enough that this feature isn't worth the trouble.

samb wondered if there was a better way to handle things. While stuttering was annoying, he wanted a solution that improved the situation without the downsides of audio stretching. Enter the Granule Synthesis Audio System.

The actual idea of the system is rather simple. By breaking down audio granularly, piece by piece, we can get the opportunity to adjust samples just as they are being presented rather than having to hold them. If there is a gap in audio, Dolphin can see it in real time and stop the stutter from happening by repeating the last sample. For minor hitches and slowdowns, this almost completely hides audio oddities without increasing audio latency!

Obviously no solution will be perfect, but we believe that "Fill Gaps" provides a fairly high quality solution without the downsides provided by audio stretching. If for some reason you prefer the old behavior, you can disable the "Fill Gaps" option in the Options -> Configuration -> Audio tab in Dolphin.

Note that audio stretching is currently not implemented within the Granule Synthesis Audio System. For users that are experiencing consistent and heavy lag and used audio stretching, this may result in less than ideal audio in the short-term. However, samb plans to add a full-fledged audio stretching system on top of Granule Synthesis to improve these edge cases in the future. Considering that most players are going to be attempting to play games at or near full speed, we decided that rather than delaying the feature, we'd rather merge it and add on to it later.

Frame Pacing Improvements - 2503-54, 2503-56, and 2503-186, by Billiard

"Frame pacing" is a term used to describe the consistency at which frames are presented to your screen. This is an extreme example, but if you have a screen that refreshes every 16.6ms (60 Hz) and half of your frames present in 11.1 ms (90 FPS) and the other half present in 22.2 ms (45 FPS), you are in for an extremely bad time despite having an average frame rate of 60 FPS. It's not enough to simply run at 60 frames per second! The rendering and presentation of those frames needs to be consistent frame to frame and synchronize with your display for best results. We call that frame pacing.

Historically, Dolphin's frame pacing has been pretty good... when it was not bogged down by Windows 7's terrible borderless window mode, or getting screwed over by terrible graphics drivers, or if you were trying to run a 30 FPS title before we implemented skip duplicate frames... But those issues were solved, and Dolphin's frame pacing is now good! ...Right?

We thought we were doing a pretty good job, but after the merge of samb's FrameTime/VBlank Analyzer + Graph, it was made apparent that there was still a lot of room for improvement.

The graph you see above shows two lines. "Frame", the orange line, is the time sampled immediately after the video backend pushes a frame. Ideally, this would perfectly match the amount of time the game has to render a frame. For NTSC, it should be 1001/60 ms (~16.67 ms) for a 60 FPS title and 1001/30 ms (~33.33 ms) for a 30 FPS title. The blue line is "V-Blank", which is measured at the end of each emulated video field - when the console would be pushing a frame to the screen. Ideally, this number should always be at the output rate of the emulated console. However, V-Blank is not necessarily tied directly to presentation because Dolphin has various hacks to display at different times.

All of the wiggles you see in the lines are variance, where either the Frame or V-Blank are missing their timing windows. The numerical statistics below the graph lists ±0.40 ms of variance for V-Blank and ±0.24 ms of variance for Frame. This results in uneven frame delivery to your screen, which appears as judder to the user.

With long obfuscated issues now in plain sight, work quickly began on improving Dolphin's frame pacing.

One of the initial things that samb did after seeing these results was to throttle Dolphin more often. Throttling is essentially just a fancy way to keep the core running at the desired speed. By having Dolphin throttle 1200 times a second instead of 100, Dolphin would incidentally be more likely to throttle at a time useful for presenting frames.

Billiard took this concept and improved it with 2503-54. Instead of adding more throttling and potentially affecting performance, he removed almost all of the superfluous throttling and instead had Dolphin throttle for player input and frame presentation.

Despite these efforts, some games still had a consistent juddering. One such game was Super Mario Sunshine. After looking at it for a while, Billiard realized that something strange was going on. For some reason, there were games that established different analog video timing parameters between the odd and even fields. In Super Mario Sunshine specifically, it gives the even field a slightly longer pre-blanking time and an equivalently shorter post blanking time. This is fine on console where output is drawn line by line. But because Dolphin was centering frame presentation based on pre-blanking time without taking into account post-blanking time, we were improperly pacing output in these titles. 2503-56 addresses this issue by accounting for both pre-blanking and post-blanking timings into frame presentation timings.

Finally, we have 2503-186. This change added a high resolution timer to Dolphin on Windows, and made some other adjustments to sleeps on other OSes. The reason for the high resolution timer on Windows is because it was being problematic regardless of technique used and giving worse frame pacing than Linux. The timer change appears to bring it up to code with what we're expecting. The other OSes did not need this, but we were able to further improve frame pacing by adding ~1 ms of "busy waiting" to make sure we get control to present exactly when we want to instead of when the OS ends our sleep.

What was the result of all this work?

If you're sensitive to frame pacing issues, you'll notice the improvements immediately. Most of our testers reported immediate results across a variety of different titles. However, we can't guarantee every game will be perfect just yet. There's always the possibility that some titles have imperfect frame pacing even on console, or that they are doing something weird. For instance, Alien Hominid runs at thousands of frames per second on console!

As a final note, Immediately Present XFB copies will always try to present the frame as soon as it is done to reduce input latency, which reduces the impact of these frame pacing improvements.

2503-122 - Use Game Requested Anisotropic Filtering by Pokechu22 and Billiard

Anisotropic filtering is a texture filtering technique that improves the quality of textures at oblique angles. It is very memory bandwidth intensive, making high levels of anisotropic filtering still uncommon even on consoles today. When gaming on a PC, it's common to just crank it to the max and forget about it. Naturally, Dolphin has offered anisotropic filtering as an enhancement from nearly the beginning.

You may not know this, but the GameCube and Wii actually support anisotropic filtering. It is fairly uncommon across the library due to it being exceedingly expensive performance-wise, but it is still a feature that these consoles support. However, rather than applying it to every texture, developers would instead apply anisotropic filtering to specific textures as needed - usually repeated textures on large floors or walls.

However, Dolphin's anisotropic filtering enhancement is not emulation of the consoles' anisotropic filtering. In fact, Dolphin completely ignored all anisotropic filtering requests from the game entirely! Dolphin's enhancement was everything or nothing, and there was no way to only enable anisotropic filtering just for the textures that would have used it on console. As such, it was impossible to get console-matching texture output - without the enhancement some textures would be too soft, and with the enhancement some textures would be too sharp. It was never quite right.

This has now changed! If Dolphin's texture filtering is set to Default and a game requests anisotropic filtering, Dolphin will now listen to the game's request and apply the specific anisotropic filtering it asked for.

Existing texture filtering configurations are not affected by this change. If you had 16x set previously, Dolphin will still use 16x anisotropic filtering on all textures.

2503-270 - Disguise Rock Band PlayStation USB devices as Wii equivalents by JosJuice

The 7th generation of video game consoles was a wild time for official USB controllers. Before or since, we have never had more a varied selection of official shaped plastic input devices! Amusingly, PlayStation 3 and Wii-branded devices were usually cross-compatible between the consoles. However, Xbox 360 devices tended to work differently and were usually not compatible. But, if you were someone who played Skylanders on the PlayStation 3 and had a Portal of Power from a PlayStation 3 bundle, you could use that on a Wii without any issues.

Sadly, this wasn't always the case. The Rock Band PlayStation 3 and Wii controllers identify themselves with different device IDs, despite being nearly the same internally. And that's unfortunate, because the different IDs are the only thing that stops a PlayStation 3 Rock Band controller from working on a Wii, and vice versa.

Now, you might be asking, what if you just tricked the game into thinking that the Wii controller was connected? Well, that's exactly what JosJuice implemented. When a game tries to identify a connected PlayStation 3 Rock Band controller, Dolphin will now tell it that the equivalent Wii controller is connected instead, allowing it to work.

If this is a behaviour that you do not want, it can be disabled via the option DisguisePlayStationAsWii in the Dolphin.ini configuration file.

2503-146 - Game Patch: Fix The Daring Game for Girls by flacs

Games can become notable for many reasons. There are those that have legendary difficulty, incredible stories, or amazing multiplayer, among other traits that make them desirable. Others are notorious, due to being rushed, broken, or downright bad and boring.

In the Dolphin community, sometimes games become famous (or infamous) due to how they behave in the emulator. Star Wars: Rogue Squadron III is legendary as a game that's nearly impossible to emulate. True Crime: New York City (GC) is infamous because of how many issues it has, even on console.

And then there's The Daring Game for Girls. Widely regarded as ordinary Wii shovelware, it has become notorious simply because it didn't boot in Dolphin. And with the list of incompatible games dwindling every year, the fact this game in particular was still broken just made it more interesting to people.

When it became the only reported title to not boot on Dolphin's compatibility list, a crosshair was placed upon it. And finally, someone took a look at fixing The Daring Game for Girls. If you're expecting some grand investigative adventure with twists and turns, sorry to disappoint you. The reason this game didn't work was actually very similar to several other games fixed in the last two years. The game's audio engine has a latent race condition bug that was exposed by Dolphin's poor timings. Thanks to debugging work by hthh, a veteran of debugging weird game behaviors, all flacs had to do was patch the game bug.

So now a game that was mostly notorious for not working in Dolphin was finally working. Its legacy was gone. And while we booted the game on console in the past for testing, no one put any serious play time on it and just blew it off as Wii shovelware. This time, we put significant hours into The Daring Game for Girls to make sure that it was working properly. And while it starts out like a typical crappy Wii motion-controlled minigame collection, something deeper lurked within...

The game has a horrible first impression. The first two minigames you play are a quiz and a slide puzzle. At this point, our guard was down and we thought we were dealing with a standard crappy Wii game. But those minigames weren't the point of the game. In fact, they simply distract you from the main gameplay loop that takes place in the overworld.

The idea is that you're surrounded by a myriad of customers that want things. By following the news on local trends, you can operate your business on the side of the road. For instance, you can set up a small garden and grow flowers to sell to people. If they like your flowers, they're certain to buy from you again. If you're strapped for cash, you can also serve lemonade, which is a cheap and simple product to get your business back into the green.

The gameplay works best if you keep yourself to a schedule, 1 task at a time. Obtain materials to create products to sell to people to make a bigger profit. Once you have enough money, you can buy yourself transportation in the form of a scooter. But if you just need to relax, there's a local basketball court where you can shoot hoops. But always remember to do things aboveboard, as breaking local ordinances could result in trouble. Don't scoot without a helmet!

The Daring Game for Girls is no masterpiece by any means. To beat the game, you do have to deal with some truly uninspired and awful minigames. But if you're a trash connoisseur that can weather that storm, the game's weirdness can be charming. You'll be going along, obtaining power tools, collecting elements from the periodic table, and making lemonade, only to be sidetracked by a surprisingly in-depth scooter building minigame that puts American Chopper 2 to shame.

In the end, after playing The Daring Game for Girls for longer than any human should... we came to a horrifying conclusion. The game isn't the worst thing in the world. Is it empowering for girls? Sometimes, maybe. Does it come off as patronizing toward the target audience? A lot of the time, yes. But is it devoid of any entertainment? In our opinion, it's a weird enough game that it actually manages to escape the doldrums of being an awful shovelware game.

If you happen to encounter The Daring Game for Girls in a garage/boot/yard sale or thrift store, it is well worth a look.

2503-324 - Android: Show time played in game details by JosJuice

In our last release, Dolphin gained the ability to display a "Time Played" value in the game list that accurately reflects how long you've played each game. Unfortunately, Android didn't get this feature... sort of. After the initial pull request was merged, Dolphin began recording play time on Android, but there was no way to actually see it in the Android UI.

Thankfully, JosJuice came to the rescue of our Android users and added a way to see the time played.

2503-517 - Add VBI Frequency Override by samb and SuperSamus

Emulators can allow players to experience their games in brand new ways. With higher resolution, high resolution texture packs, different controllers, and even playing local games online using netplay, emulators can push way beyond the limitations of the original hardware.

Hacks that increase frame rate are one type of enhancement that has been sweeping through the emulation community. Over the years, many popular games have been taken from their native 25/30 FPS target to 50/60 FPS via cheat codes and patches. However, in Dolphin, pushing them further beyond that has largely been impossible.

The GameCube and Wii were designed for analog televisions. The primary way these consoles keep track of the start or end of a frame is the Vertical Blank Interrupt (VBI) - an interrupt synchronized to the vertical blanking interval of analog displays. Most games for the GameCube and Wii listen for the VBI and either make a frame every VBI (to output 50/60 FPS) or every other VBI (to output 25/30 FPS). Getting a game to update at every VBI instead of every other VBI is fairly straightforward, but going beyond 60 FPS would require detaching from how the consoles think of frames. Rejecting their reality and substituting our own is much more difficult.

samb, our favourite chaotic tinkerer, enjoys playing with these limitations. While they were experimenting with the VBI Skip hack, which allowed games to run at lower frame rates, they had a rather terrible thought. What if instead of removing VBIs, they added some? If it was possible to make a game skip frames, would it be possible to make them add more through this method?

At a glance, it seemed like the answer was... kinda. The games they experimented with did output more frames, but their gameplay was also sped up. After all, the modern idea of "delta time", where a game's physics are calculated independently of frame rate, wasn't standardized or even common back in the GameCube/Wii era.

samb was disappointed by these initial results and moved on to other shenanigans. However, the original pull request was never closed and left open for others to experiment with. After finding promising results with it, SuperSamus took up the maintenance mantle and rebased it on the latest builds of Dolphin. They thought that perhaps we overlooked this feature too quickly and sought to prove that the feature should be included in Dolphin.

By combining the hack with game patches, SuperSamus created incredible demonstrations that showed what was truly possible. Compatibility was still low, but the games supported became numerous enough that the potential couldn't be ignored.

To clarify things: many major titles like Super Mario Galaxy and Wind Waker do not respond well to this hack. Their physics are programmed to function at one specific frame rate, and they don't have any variable that controls how much things move every frame. They are the worst candidates for ever supporting this hack.

But some games are the complete opposite. Super Mario Strikers and Mario Strikers Charged don't even require patches, and will run at whatever frame rate you suggest without affecting gameplay speed!

We can't stress enough that games which maintain the same speed regardless of VBI frequency are the exception, not the rule. However, there are some cases where you might want a game to speed up or slow down. That's because VBI Frequency Override does not affect audio, meaning that it if a game doesn't require technical gameplay, you can greatly speed it up without distorting sound effects or music. However, you should note that VBI Frequency Override comes with the same risks as increasing the Emulated CPU Clock (in fact, it will automatically modify it to match the VBI frequency), and may cause hangs in games that are sensitive to CPU timings.

We've crafted a list of games that are known to respond to VBI Frequency Override. A game being on this list does not mean that it is stable when adding VBIs! It only means that these games calculate game physics using delta time. Other games do have a variable that controls game speed, but won't adjust it dynamically, meaning that it must be manually changed through a patch. Finding these games can take much experimentation, so even if a game isn't in the list, it may still be possible to make a patch for it. There are also games that arbitrarily limit the frame rate, and others that arbitrarily clamp their delta time to a certain range. Since it's very easy to control when these behaviors are in action, Branch Watch is an incredibly useful tool for finding and patching these functions.

Even in games that use delta time, there can still be cases where developers tie something to the frame rate. For example, in Digimon World 4, certain special moves require you to spin the stick. As you increase the frame rate, the timing window for spinning the stick becomes smaller and smaller, making it more difficult to do the special move. In XGIII: Extreme Racing, the actual racing uses delta time, but certain animated textures are hardcoded to advance per frame. In Scooby Doo! Night of 100 Frights, swinging on ropes will cover less distance at high frame rates.

If it isn't clear by now, don't use this feature if you're doing your first playthrough of a game, even if it is on our list. We can't promise stability, we can't promise compatibility, and we can't promise that your device is fast enough to handle the feature.

But, as fans, experiencing some of these games at high frame rates is an interesting enough novelty that we want to give those interested a chance to try it themselves. We're hopeful that games which almost work properly can be modded and adjusted to work on a more complete level with cheat codes or patches. SuperSamus has already patched several games to be more playable. One such game, Need For Speed: Nitro, works pretty much perfectly in our experience, but requires incredibly high-end hardware to push to 120 FPS or higher.

As an aside, special mention has to go to Next Level Games, as Mario Strikers Charged even syncs up in online matches between Dolphin instances running at different frame rates. For example, A 60 FPS player can play with a 144 FPS player without major issues. Both of the Mario Strikers games seem to work at pretty much any frame rate without any serious issues, so kudos to them.

And because the world is a very strange place, the newly supported The Daring Game for Girls works with this feature as well. Joy.

2503-580 - Wii Speak Emulation by shuffle2, degasus, noahpistilli, and sepalani

Nintendo's Wii Speak was probably meant for bigger things. But every so often, one of Nintendo's accessories flops, and when they flop, they often flop hard. Out of the entire Wii library, the only software to outright require it is the Wii Speak Channel, which is self explanatory, and only fifteen games (to our knowledge) utilized it as an optional accessory.

Perhaps the most notorious usage of the Wii Speak games were the Wii versions of Wheel of Fortune and Jeopardy!, which used it for voice recognition. In 2010. Completely offline. On a console with hardware from 2001. Anyone who had these games will remember it hearing the wrong answer when you had the right answer, giving you the right answer when you had the wrong answer, and outright ignoring what you said. It's like Hey You, Pikachu!, but with thousands of imaginary dollars on the line!

Using Wii Speak exclusive features has been possible in Dolphin for many years, but real Wii Speak hardware was required. But now, thanks to work that bounced between four developers for over a decade, you can enjoy the Wii Speak experience with a standard microphone on your PC.

You're welcome.

On desktop you can find this feature under Tools > Emulated USB devices > Wii Speak. On Android, it's located under Settings > Config > Wii > Emulated USB Devices, and you'll need to give Dolphin permission to use the microphone.


This Release's Contributors...

Special thanks to all of the contributors that incremented Dolphin by 610 commits after Release 2503!



Dolphin vs. Aggressive AI Scraper Bots

We've recently observed a large increase in the amount of traffic on our websites, sometimes even reaching a point where the websites would become overwhelmed and crash. Many important services like the downloads and updates system, NetPlay, and Wii System Menu Updates rely on our websites to function correctly, so any outages have a direct impact on many Dolphin users. At one point, we even got an e-mail from our hosting provider asking that we reduce our excessive server load, as it was starting to cause problems for their other customers' websites!

When we investigated what was going on, we found that scraper bots owned by AI companies were making up a significant portion of the requests sent to our websites. Text written by humans is very valuable to companies creating large language models (LLMs). In order to create text datasets for training their models, these companies have deployed scraper bots to download all the text they can find from the Internet. These bots request a page, copy all of its text into their dataset, and then repeat the process with all of the links found on that page. They can even make requests from multiple IP addresses simultaneously. We were effectively being DDoSed by scrapers!

Thankfully, scrapers run by the major AI companies are generally well-behaved and comply with the Robots Exclusion Protocol. This means that we can provide files called robots.txt that specifies which bots are allowed or not allowed to access our websites. We went ahead and created a blocklist based on ai.robots.txt, an open list of bots that are run by AI companies.

Unfortunately, even after blocking these bots, some sites like our wiki were still occasionally crashing. After looking closer at our server logs, we noticed something suspicious. Why were we getting hundreds of requests from computers claiming to run Windows 95!?

There was apparently another type of AI scraper bot plaguing our wiki. These bots did not care about being good Internet citizens. They ignored the Robots Exclusion Protocol, and instead pretended to be browsers when identifying themselves to our server. They constantly switched between mimicking modern browsers, outdated browsers, and browsers that do not exist at all (like Internet Explorer 9 on Windows 95, or Google Chrome on a PowerPC Mac). Worst of all, they often made requests for pages that take a decent amount of work for the server to render, like revision history pages. While we're not sure exactly who is operating these bots, their request patterns did suggest that they were trying to download the text off of every possible page on our wiki.

In order to prevent this traffic from continuing to cause outages, we've deployed Anubis. When you first visit the wiki, your browser will now be checked by Anubis to ensure that it is a legitimate browser and not a bot. This should only take a few seconds, though it may take a bit more time on older devices. Once your browser has been verified, you will be redirected to the page that you were looking for. Checks should only occur approximately once a week, assuming you have cookies enabled.

Upon deploying Anubis, we immediately observed a drop in traffic hitting the wiki, and that it was loading much faster than before! We found that Anubis worked so well that, after seeing these results, we deployed it on our bug tracker and on FifoCI as well.

Anubis is built around the concept of "proof-of-work", where each request is validated by having the client solve a problem (a "challenge") that is hard to compute, but easy for the server to verify. The idea is to make it more difficult for bots to send out automated requests en masse, as now they need to expend additional time and computing power to solve challenges. In Anubis's implementation of proof-of-work, each challenge involves having the browser find a SHA-256 hash that starts with a specific number of zeros.

While Anubis works really well, there are still some limitations. The biggest limitation right now is that JavaScript must be enabled to pass challenges. If you have JavaScript disabled, you'll need to enable it to be able to access some of our sites. This may be resolved in a future version of Anubis. There may also be some problems when attempting to access Anubis-protected sites on a dual-stack Internet connection (one that supports both IPv4 and IPv6). If you see an "Invalid response" error, try clicking the "Go home" link and see if the Anubis check passes there.


We're not alone with this scraping problem. Several major open-source organizations like the Linux kernel, Sourcehut, and ScummVM have recently spoken about AI scrapers causing excessive server load, and many have already chosen to use Anubis to block these requests. Even the United Nations has decided to deploy Anubis.

It's a shame that we have make life a little more annoying for our users when protecting our servers, but unfortunately this is the reality of the modern Internet.


2506
  • Système audio amélioré : introduction du Granule Synthesis Audio System pour réduire les sauts audio lors des ralentissements, sans latence ni étirement forcé.
  • Correction critique pour macOS : version minimale requise relevée à macOS 11 Big Sur (suppression du support de Catalina), avec mise à jour de Qt vers 6.5 LTS.
  • Compatibilité étendue : émulation de Wii Speak fonctionnelle via micro, accessible via les paramètres USB ou Android.
  • Correction de bugs macOS : résolution d’un crash sur anciennes versions et de problèmes de connectivité GBA dans les jeux GameCube compatibles.
  • Amélioration des performances : optimisations du frame pacing pour une fluidité accrue, avec ajustements des timings vidéo (pré/post-blanking).
  • Correction de build : suppression du suffixe "a" pour les versions de développement après un hotfix mal appliqué en 2503.

Welcome to the Dolphin Progress Report for Release 2506! As we've alluded to a few times, we've had major changes in the pipeline that we've been very excited to show off. Some of those changes are finally here! Headlining this report are major adjustments to how Dolphin handled audio lag under slowdown by default. No longer will users have to choose between high-latency audio stretching or popping when dealing with small hitches in performance thanks to the new Granule Synthesis Audio System.

If the game is already running full speed, we still have some improvements for you. Dolphin has seen a suite of frame pacing improvements that will give you a smoother experience across almost every game. And, if your system is very powerful, there are a select group of games that can now push past the 60 FPS barrier for high frame rate gaming. Before you get too excited, this feature does not work with most Nintendo developed titles and has incredibly low compatibility in general. For a list of what games support this, we'll get into it later in the report.

If you care about preserving oddball Wii add-ons, we've got you covered here too. Wii Speak emulation is finally here after an incredibly long journey. In addition, long time incompatible game The Daring Game For Girls is finally compatible with Dolphin. We'll get into that game's story and more, but first, we need to get through quite a bit of housekeeping.

The Release Hotfix Fiasco

We finally had some big enough problems in a release that we had to create a hotfix using our new versioning system. First, the macOS build for 2503 had the wrong version number attached, causing it to be incompatible with cross-platform NetPlay. We also found that GBA connectivity in compatible GameCube games was broken, and that there was a crashing bug when running Dolphin on older macOS versions. To rectify these problems, we created hotfix 2503a. However, in doing so, we inadvertently caused all development builds from that point on to take the "a" suffix. Some of our systems temporarily broke in the immediate aftermath while support for the suffix was hastily added. We technically could have removed the suffix, but we decided not to in the end because removing it would have caused even more disruption.

In future releases, if a hotfix is needed it will not apply a suffix to the development builds. This should make things easier on us and anyone else that is maintaining Dolphin builds of their own. We apologize for any inconvenience that this error has caused.

For reader convenience and future consistency, the hotfix suffix has been removed from all changes in this article.

Windows 10 minimum version bumped to 1903

Although Windows 10 will reach End of Support later this year, it continued to receive major updates up until two and a half years ago. Thanks to that, we should be able to continue supporting the decade-old operating system for many more years. However, as new APIs, standards, and compiler features appear, our minimum Windows 10 version will slowly climb. As of 2503-152, we are now taking advantage of time zone APIs that require Windows 10 version 1903, meaning that any older versions of Windows 10 are no longer supported.

The last Dolphin release to support Windows 10 versions 1703 to 1809 is 2503a, and the last development build is 2503-148.

macOS minimum version bumped to macOS 11 Big Sur

We have also increased our minimum macOS version from macOS 10.15 Catalina to macOS 11 Big Sur. Unfortunately, Catalina lacks support for some C++20 APIs that we'd like to take advantage of, so we decided to go ahead and bump our minimum macOS version to accommodate those changes. This bump will also allow us to (finally) update the Qt in our macOS builds to 6.5 LTS, which we will aim to do before the next release.

The last Dolphin release to support macOS 10.15 Catalina is 2503a, and the last development build is 2503-270.

Notable Changes

2503-51 - Granule Synthesis Audio System by samb

When reporting performance issues, sometimes users don't even realize that the game is slowing down. They instead report audio hitching or stuttering as the main issue that's bothering them. In order to provide low latency audio, Dolphin employs a ring buffer. And, as long as the game is running full speed, this buffer remains full and you'll get a constant stream of audio.

When the emulator is not running at the target frame rate, the buffer won't be filled up. And when Dolphin runs out of audio in the buffer, there will be a small gap in audio that sounds rather unpleasant.

To combat this, Dolphin has given users the ability to enable audio stretching. At the cost of higher audio latency, Dolphin can stretch the existing data in the buffer to keep audio running smoothly. For many users, the increase in audio latency is large enough that this feature isn't worth the trouble.

samb wondered if there was a better way to handle things. While stuttering was annoying, he wanted a solution that improved the situation without the downsides of audio stretching. Enter the Granule Synthesis Audio System.

The actual idea of the system is rather simple. By breaking down audio granularly, piece by piece, we can get the opportunity to adjust samples just as they are being presented rather than having to hold them. If there is a gap in audio, Dolphin can see it in real time and stop the stutter from happening by repeating the last sample. For minor hitches and slowdowns, this almost completely hides audio oddities without increasing audio latency!

Obviously no solution will be perfect, but we believe that "Fill Gaps" provides a fairly high quality solution without the downsides provided by audio stretching. If for some reason you prefer the old behavior, you can disable the "Fill Gaps" option in the Options -> Configuration -> Audio tab in Dolphin.

Note that audio stretching is currently not implemented within the Granule Synthesis Audio System. For users that are experiencing consistent and heavy lag and used audio stretching, this may result in less than ideal audio in the short-term. However, samb plans to add a full-fledged audio stretching system on top of Granule Synthesis to improve these edge cases in the future. Considering that most players are going to be attempting to play games at or near full speed, we decided that rather than delaying the feature, we'd rather merge it and add on to it later.

Frame Pacing Improvements - 2503-54, 2503-56, and 2503-186, by Billiard

"Frame pacing" is a term used to describe the consistency at which frames are presented to your screen. This is an extreme example, but if you have a screen that refreshes every 16.6ms (60 Hz) and half of your frames present in 11.1 ms (90 FPS) and the other half present in 22.2 ms (45 FPS), you are in for an extremely bad time despite having an average frame rate of 60 FPS. It's not enough to simply run at 60 frames per second! The rendering and presentation of those frames needs to be consistent frame to frame and synchronize with your display for best results. We call that frame pacing.

Historically, Dolphin's frame pacing has been pretty good... when it was not bogged down by Windows 7's terrible borderless window mode, or getting screwed over by terrible graphics drivers, or if you were trying to run a 30 FPS title before we implemented skip duplicate frames... But those issues were solved, and Dolphin's frame pacing is now good! ...Right?

We thought we were doing a pretty good job, but after the merge of samb's FrameTime/VBlank Analyzer + Graph, it was made apparent that there was still a lot of room for improvement.

The graph you see above shows two lines. "Frame", the orange line, is the time sampled immediately after the video backend pushes a frame. Ideally, this would perfectly match the amount of time the game has to render a frame. For NTSC, it should be 1001/60 ms (~16.67 ms) for a 60 FPS title and 1001/30 ms (~33.33 ms) for a 30 FPS title. The blue line is "V-Blank", which is measured at the end of each emulated video field - when the console would be pushing a frame to the screen. Ideally, this number should always be at the output rate of the emulated console. However, V-Blank is not necessarily tied directly to presentation because Dolphin has various hacks to display at different times.

All of the wiggles you see in the lines are variance, where either the Frame or V-Blank are missing their timing windows. The numerical statistics below the graph lists ±0.40 ms of variance for V-Blank and ±0.24 ms of variance for Frame. This results in uneven frame delivery to your screen, which appears as judder to the user.

With long obfuscated issues now in plain sight, work quickly began on improving Dolphin's frame pacing.

One of the initial things that samb did after seeing these results was to throttle Dolphin more often. Throttling is essentially just a fancy way to keep the core running at the desired speed. By having Dolphin throttle 1200 times a second instead of 100, Dolphin would incidentally be more likely to throttle at a time useful for presenting frames.

Billiard took this concept and improved it with 2503-54. Instead of adding more throttling and potentially affecting performance, he removed almost all of the superfluous throttling and instead had Dolphin throttle for player input and frame presentation.

Despite these efforts, some games still had a consistent juddering. One such game was Super Mario Sunshine. After looking at it for a while, Billiard realized that something strange was going on. For some reason, there were games that established different analog video timing parameters between the odd and even fields. In Super Mario Sunshine specifically, it gives the even field a slightly longer pre-blanking time and an equivalently shorter post blanking time. This is fine on console where output is drawn line by line. But because Dolphin was centering frame presentation based on pre-blanking time without taking into account post-blanking time, we were improperly pacing output in these titles. 2503-56 addresses this issue by accounting for both pre-blanking and post-blanking timings into frame presentation timings.

Finally, we have 2503-186. This change added a high resolution timer to Dolphin on Windows, and made some other adjustments to sleeps on other OSes. The reason for the high resolution timer on Windows is because it was being problematic regardless of technique used and giving worse frame pacing than Linux. The timer change appears to bring it up to code with what we're expecting. The other OSes did not need this, but we were able to further improve frame pacing by adding ~1 ms of "busy waiting" to make sure we get control to present exactly when we want to instead of when the OS ends our sleep.

What was the result of all this work?

If you're sensitive to frame pacing issues, you'll notice the improvements immediately. Most of our testers reported immediate results across a variety of different titles. However, we can't guarantee every game will be perfect just yet. There's always the possibility that some titles have imperfect frame pacing even on console, or that they are doing something weird. For instance, Alien Hominid runs at thousands of frames per second on console!

As a final note, Immediately Present XFB copies will always try to present the frame as soon as it is done to reduce input latency, which reduces the impact of these frame pacing improvements.

2503-122 - Use Game Requested Anisotropic Filtering by Pokechu22 and Billiard

Anisotropic filtering is a texture filtering technique that improves the quality of textures at oblique angles. It is very memory bandwidth intensive, making high levels of anisotropic filtering still uncommon even on consoles today. When gaming on a PC, it's common to just crank it to the max and forget about it. Naturally, Dolphin has offered anisotropic filtering as an enhancement from nearly the beginning.

You may not know this, but the GameCube and Wii actually support anisotropic filtering. It is fairly uncommon across the library due to it being exceedingly expensive performance-wise, but it is still a feature that these consoles support. However, rather than applying it to every texture, developers would instead apply anisotropic filtering to specific textures as needed - usually repeated textures on large floors or walls.

However, Dolphin's anisotropic filtering enhancement is not emulation of the consoles' anisotropic filtering. In fact, Dolphin completely ignored all anisotropic filtering requests from the game entirely! Dolphin's enhancement was everything or nothing, and there was no way to only enable anisotropic filtering just for the textures that would have used it on console. As such, it was impossible to get console-matching texture output - without the enhancement some textures would be too soft, and with the enhancement some textures would be too sharp. It was never quite right.

This has now changed! If Dolphin's texture filtering is set to Default and a game requests anisotropic filtering, Dolphin will now listen to the game's request and apply the specific anisotropic filtering it asked for.

Existing texture filtering configurations are not affected by this change. If you had 16x set previously, Dolphin will still use 16x anisotropic filtering on all textures.

2503-270 - Disguise Rock Band PlayStation USB devices as Wii equivalents by JosJuice

The 7th generation of video game consoles was a wild time for official USB controllers. Before or since, we have never had more a varied selection of official shaped plastic input devices! Amusingly, PlayStation 3 and Wii-branded devices were usually cross-compatible between the consoles. However, Xbox 360 devices tended to work differently and were usually not compatible. But, if you were someone who played Skylanders on the PlayStation 3 and had a Portal of Power from a PlayStation 3 bundle, you could use that on a Wii without any issues.

Sadly, this wasn't always the case. The Rock Band PlayStation 3 and Wii controllers identify themselves with different device IDs, despite being nearly the same internally. And that's unfortunate, because the different IDs are the only thing that stops a PlayStation 3 Rock Band controller from working on a Wii, and vice versa.

Now, you might be asking, what if you just tricked the game into thinking that the Wii controller was connected? Well, that's exactly what JosJuice implemented. When a game tries to identify a connected PlayStation 3 Rock Band controller, Dolphin will now tell it that the equivalent Wii controller is connected instead, allowing it to work.

If this is a behaviour that you do not want, it can be disabled via the option DisguisePlayStationAsWii in the Dolphin.ini configuration file.

2503-146 - Game Patch: Fix The Daring Game for Girls by flacs

Games can become notable for many reasons. There are those that have legendary difficulty, incredible stories, or amazing multiplayer, among other traits that make them desirable. Others are notorious, due to being rushed, broken, or downright bad and boring.

In the Dolphin community, sometimes games become famous (or infamous) due to how they behave in the emulator. Star Wars: Rogue Squadron III is legendary as a game that's nearly impossible to emulate. True Crime: New York City (GC) is infamous because of how many issues it has, even on console.

And then there's The Daring Game for Girls. Widely regarded as ordinary Wii shovelware, it has become notorious simply because it didn't boot in Dolphin. And with the list of incompatible games dwindling every year, the fact this game in particular was still broken just made it more interesting to people.

When it became the only reported title to not boot on Dolphin's compatibility list, a crosshair was placed upon it. And finally, someone took a look at fixing The Daring Game for Girls. If you're expecting some grand investigative adventure with twists and turns, sorry to disappoint you. The reason this game didn't work was actually very similar to several other games fixed in the last two years. The game's audio engine has a latent race condition bug that was exposed by Dolphin's poor timings. Thanks to debugging work by hthh, a veteran of debugging weird game behaviors, all flacs had to do was patch the game bug.

So now a game that was mostly notorious for not working in Dolphin was finally working. Its legacy was gone. And while we booted the game on console in the past for testing, no one put any serious play time on it and just blew it off as Wii shovelware. This time, we put significant hours into The Daring Game for Girls to make sure that it was working properly. And while it starts out like a typical crappy Wii motion-controlled minigame collection, something deeper lurked within...

The game has a horrible first impression. The first two minigames you play are a quiz and a slide puzzle. At this point, our guard was down and we thought we were dealing with a standard crappy Wii game. But those minigames weren't the point of the game. In fact, they simply distract you from the main gameplay loop that takes place in the overworld.

The idea is that you're surrounded by a myriad of customers that want things. By following the news on local trends, you can operate your business on the side of the road. For instance, you can set up a small garden and grow flowers to sell to people. If they like your flowers, they're certain to buy from you again. If you're strapped for cash, you can also serve lemonade, which is a cheap and simple product to get your business back into the green.

The gameplay works best if you keep yourself to a schedule, 1 task at a time. Obtain materials to create products to sell to people to make a bigger profit. Once you have enough money, you can buy yourself transportation in the form of a scooter. But if you just need to relax, there's a local basketball court where you can shoot hoops. But always remember to do things aboveboard, as breaking local ordinances could result in trouble. Don't scoot without a helmet!

The Daring Game for Girls is no masterpiece by any means. To beat the game, you do have to deal with some truly uninspired and awful minigames. But if you're a trash connoisseur that can weather that storm, the game's weirdness can be charming. You'll be going along, obtaining power tools, collecting elements from the periodic table, and making lemonade, only to be sidetracked by a surprisingly in-depth scooter building minigame that puts American Chopper 2 to shame.

In the end, after playing The Daring Game for Girls for longer than any human should... we came to a horrifying conclusion. The game isn't the worst thing in the world. Is it empowering for girls? Sometimes, maybe. Does it come off as patronizing toward the target audience? A lot of the time, yes. But is it devoid of any entertainment? In our opinion, it's a weird enough game that it actually manages to escape the doldrums of being an awful shovelware game.

If you happen to encounter The Daring Game for Girls in a garage/boot/yard sale or thrift store, it is well worth a look.

2503-324 - Android: Show time played in game details by JosJuice

In our last release, Dolphin gained the ability to display a "Time Played" value in the game list that accurately reflects how long you've played each game. Unfortunately, Android didn't get this feature... sort of. After the initial pull request was merged, Dolphin began recording play time on Android, but there was no way to actually see it in the Android UI.

Thankfully, JosJuice came to the rescue of our Android users and added a way to see the time played.

2503-517 - Add VBI Frequency Override by samb and SuperSamus

Emulators can allow players to experience their games in brand new ways. With higher resolution, high resolution texture packs, different controllers, and even playing local games online using netplay, emulators can push way beyond the limitations of the original hardware.

Hacks that increase frame rate are one type of enhancement that has been sweeping through the emulation community. Over the years, many popular games have been taken from their native 25/30 FPS target to 50/60 FPS via cheat codes and patches. However, in Dolphin, pushing them further beyond that has largely been impossible.

The GameCube and Wii were designed for analog televisions. The primary way these consoles keep track of the start or end of a frame is the Vertical Blank Interrupt (VBI) - an interrupt synchronized to the vertical blanking interval of analog displays. Most games for the GameCube and Wii listen for the VBI and either make a frame every VBI (to output 50/60 FPS) or every other VBI (to output 25/30 FPS). Getting a game to update at every VBI instead of every other VBI is fairly straightforward, but going beyond 60 FPS would require detaching from how the consoles think of frames. Rejecting their reality and substituting our own is much more difficult.

samb, our favourite chaotic tinkerer, enjoys playing with these limitations. While they were experimenting with the VBI Skip hack, which allowed games to run at lower frame rates, they had a rather terrible thought. What if instead of removing VBIs, they added some? If it was possible to make a game skip frames, would it be possible to make them add more through this method?

At a glance, it seemed like the answer was... kinda. The games they experimented with did output more frames, but their gameplay was also sped up. After all, the modern idea of "delta time", where a game's physics are calculated independently of frame rate, wasn't standardized or even common back in the GameCube/Wii era.

samb was disappointed by these initial results and moved on to other shenanigans. However, the original pull request was never closed and left open for others to experiment with. After finding promising results with it, SuperSamus took up the maintenance mantle and rebased it on the latest builds of Dolphin. They thought that perhaps we overlooked this feature too quickly and sought to prove that the feature should be included in Dolphin.

By combining the hack with game patches, SuperSamus created incredible demonstrations that showed what was truly possible. Compatibility was still low, but the games supported became numerous enough that the potential couldn't be ignored.

To clarify things: many major titles like Super Mario Galaxy and Wind Waker do not respond well to this hack. Their physics are programmed to function at one specific frame rate, and they don't have any variable that controls how much things move every frame. They are the worst candidates for ever supporting this hack.

But some games are the complete opposite. Super Mario Strikers and Mario Strikers Charged don't even require patches, and will run at whatever frame rate you suggest without affecting gameplay speed!

We can't stress enough that games which maintain the same speed regardless of VBI frequency are the exception, not the rule. However, there are some cases where you might want a game to speed up or slow down. That's because VBI Frequency Override does not affect audio, meaning that it if a game doesn't require technical gameplay, you can greatly speed it up without distorting sound effects or music. However, you should note that VBI Frequency Override comes with the same risks as increasing the Emulated CPU Clock (in fact, it will automatically modify it to match the VBI frequency), and may cause hangs in games that are sensitive to CPU timings.

We've crafted a list of games that are known to respond to VBI Frequency Override. A game being on this list does not mean that it is stable when adding VBIs! It only means that these games calculate game physics using delta time. Other games do have a variable that controls game speed, but won't adjust it dynamically, meaning that it must be manually changed through a patch. Finding these games can take much experimentation, so even if a game isn't in the list, it may still be possible to make a patch for it. There are also games that arbitrarily limit the frame rate, and others that arbitrarily clamp their delta time to a certain range. Since it's very easy to control when these behaviors are in action, Branch Watch is an incredibly useful tool for finding and patching these functions.

Even in games that use delta time, there can still be cases where developers tie something to the frame rate. For example, in Digimon World 4, certain special moves require you to spin the stick. As you increase the frame rate, the timing window for spinning the stick becomes smaller and smaller, making it more difficult to do the special move. In XGIII: Extreme Racing, the actual racing uses delta time, but certain animated textures are hardcoded to advance per frame. In Scooby Doo! Night of 100 Frights, swinging on ropes will cover less distance at high frame rates.

If it isn't clear by now, don't use this feature if you're doing your first playthrough of a game, even if it is on our list. We can't promise stability, we can't promise compatibility, and we can't promise that your device is fast enough to handle the feature.

But, as fans, experiencing some of these games at high frame rates is an interesting enough novelty that we want to give those interested a chance to try it themselves. We're hopeful that games which almost work properly can be modded and adjusted to work on a more complete level with cheat codes or patches. SuperSamus has already patched several games to be more playable. One such game, Need For Speed: Nitro, works pretty much perfectly in our experience, but requires incredibly high-end hardware to push to 120 FPS or higher.

As an aside, special mention has to go to Next Level Games, as Mario Strikers Charged even syncs up in online matches between Dolphin instances running at different frame rates. For example, A 60 FPS player can play with a 144 FPS player without major issues. Both of the Mario Strikers games seem to work at pretty much any frame rate without any serious issues, so kudos to them.

And because the world is a very strange place, the newly supported The Daring Game for Girls works with this feature as well. Joy.

2503-580 - Wii Speak Emulation by shuffle2, degasus, noahpistilli, and sepalani

Nintendo's Wii Speak was probably meant for bigger things. But every so often, one of Nintendo's accessories flops, and when they flop, they often flop hard. Out of the entire Wii library, the only software to outright require it is the Wii Speak Channel, which is self explanatory, and only fifteen games (to our knowledge) utilized it as an optional accessory.

Perhaps the most notorious usage of the Wii Speak games were the Wii versions of Wheel of Fortune and Jeopardy!, which used it for voice recognition. In 2010. Completely offline. On a console with hardware from 2001. Anyone who had these games will remember it hearing the wrong answer when you had the right answer, giving you the right answer when you had the wrong answer, and outright ignoring what you said. It's like Hey You, Pikachu!, but with thousands of imaginary dollars on the line!

Using Wii Speak exclusive features has been possible in Dolphin for many years, but real Wii Speak hardware was required. But now, thanks to work that bounced between four developers for over a decade, you can enjoy the Wii Speak experience with a standard microphone on your PC.

You're welcome.

On desktop you can find this feature under Tools > Emulated USB devices > Wii Speak. On Android, it's located under Settings > Config > Wii > Emulated USB Devices, and you'll need to give Dolphin permission to use the microphone.


This Release's Contributors...

Special thanks to all of the contributors that incremented Dolphin by 610 commits after Release 2503!



Dolphin vs. Aggressive AI Scraper Bots

We've recently observed a large increase in the amount of traffic on our websites, sometimes even reaching a point where the websites would become overwhelmed and crash. Many important services like the downloads and updates system, NetPlay, and Wii System Menu Updates rely on our websites to function correctly, so any outages have a direct impact on many Dolphin users. At one point, we even got an e-mail from our hosting provider asking that we reduce our excessive server load, as it was starting to cause problems for their other customers' websites!

When we investigated what was going on, we found that scraper bots owned by AI companies were making up a significant portion of the requests sent to our websites. Text written by humans is very valuable to companies creating large language models (LLMs). In order to create text datasets for training their models, these companies have deployed scraper bots to download all the text they can find from the Internet. These bots request a page, copy all of its text into their dataset, and then repeat the process with all of the links found on that page. They can even make requests from multiple IP addresses simultaneously. We were effectively being DDoSed by scrapers!

Thankfully, scrapers run by the major AI companies are generally well-behaved and comply with the Robots Exclusion Protocol. This means that we can provide files called robots.txt that specifies which bots are allowed or not allowed to access our websites. We went ahead and created a blocklist based on ai.robots.txt, an open list of bots that are run by AI companies.

Unfortunately, even after blocking these bots, some sites like our wiki were still occasionally crashing. After looking closer at our server logs, we noticed something suspicious. Why were we getting hundreds of requests from computers claiming to run Windows 95!?

There was apparently another type of AI scraper bot plaguing our wiki. These bots did not care about being good Internet citizens. They ignored the Robots Exclusion Protocol, and instead pretended to be browsers when identifying themselves to our server. They constantly switched between mimicking modern browsers, outdated browsers, and browsers that do not exist at all (like Internet Explorer 9 on Windows 95, or Google Chrome on a PowerPC Mac). Worst of all, they often made requests for pages that take a decent amount of work for the server to render, like revision history pages. While we're not sure exactly who is operating these bots, their request patterns did suggest that they were trying to download the text off of every possible page on our wiki.

In order to prevent this traffic from continuing to cause outages, we've deployed Anubis. When you first visit the wiki, your browser will now be checked by Anubis to ensure that it is a legitimate browser and not a bot. This should only take a few seconds, though it may take a bit more time on older devices. Once your browser has been verified, you will be redirected to the page that you were looking for. Checks should only occur approximately once a week, assuming you have cookies enabled.

Upon deploying Anubis, we immediately observed a drop in traffic hitting the wiki, and that it was loading much faster than before! We found that Anubis worked so well that, after seeing these results, we deployed it on our bug tracker and on FifoCI as well.

Anubis is built around the concept of "proof-of-work", where each request is validated by having the client solve a problem (a "challenge") that is hard to compute, but easy for the server to verify. The idea is to make it more difficult for bots to send out automated requests en masse, as now they need to expend additional time and computing power to solve challenges. In Anubis's implementation of proof-of-work, each challenge involves having the browser find a SHA-256 hash that starts with a specific number of zeros.

While Anubis works really well, there are still some limitations. The biggest limitation right now is that JavaScript must be enabled to pass challenges. If you have JavaScript disabled, you'll need to enable it to be able to access some of our sites. This may be resolved in a future version of Anubis. There may also be some problems when attempting to access Anubis-protected sites on a dual-stack Internet connection (one that supports both IPv4 and IPv6). If you see an "Invalid response" error, try clicking the "Go home" link and see if the Anubis check passes there.


We're not alone with this scraping problem. Several major open-source organizations like the Linux kernel, Sourcehut, and ScummVM have recently spoken about AI scrapers causing excessive server load, and many have already chosen to use Anubis to block these requests. Even the United Nations has decided to deploy Anubis.

It's a shame that we have make life a little more annoying for our users when protecting our servers, but unfortunately this is the reality of the modern Internet.


2503a
  • Correction d’un bug bloquant la connectivité GBA dans certains jeux.
  • Correction d’un plantage lié à une erreur mémoire sur macOS, notamment sur les versions plus anciennes.
  • Correction d’un problème dans le système de build entraînant une étiquette erronée (2412 au lieu de 2503) sur certaines plateformes.

It's time for us to again delve into the latest changes hitting the newest release of Dolphin Emulator. If you've been keeping tabs on development channels, you'll know there are some exciting bombshell features waiting for us just over the horizon. Unfortunately, given the close proximity to this release, we've decided to hold a lot of them off so they can get more widespread testing in the development builds before hitting a release. Think of the March 2025 release as an iterative improvement that focuses on user experience and stacking many small iterative improvements instead of swinging for every homerun.

Having said all of that? We do have a few major changes that made the cut.

Probably the most requested of the features in this progress report is the ability to finally set custom graphical settings on a per game basis. Our advanced users may be thinking, "Wait, couldn't we already do that?" and they'd be right. The major change here is that per-game graphical settings has been added directly to the game properties page, allowing for a very easy, visual way to change settings and see what settings are force enabled.

For our achievement hunters out there, RetroAchievements has seen its first major upgrade that will bring a huge amount of quality of life to many games. And if you're into weird old game behaviors? A developer dove into Summoner: A Goddess Reborn to determine why it crashes so much. The catch with this one? Some of these crashes have been confirmed to happen on official hardware!

Additionally, there are a plethora of small, but tangible, changes that are the hallmark of an Open Source project. The desktop versions of Dolphin also saw a lot of improvements to input configuration and a few extra upgrades that might make people who want to track their time spent in games very happy. But, let's not spoil everything and get into the notable changes of the March 2025 release!

Release 2503a

On April 21 2025, we created Hotfix Release 2503a to fix some problems that snuck into Release 2503:

  • Fixed a bug that caused GBA connectivity in some games to not work properly.
  • Fixed a bug where Dolphin would crash with a memory error on some older macOS versions.
  • Fixed an problem with our build system which caused Release 2503 to be mislabeled as a 2412 development build on some platforms.

Notable Changes

Cheat Code Whitelist for Hardcore RetroAchievements - 2412-8 and 2412-173 by LillyJadeKatrin

RetroAchievements in Dolphin has received its first major update, and it's... cheat support in hardcore?! What gives?

Up until around the 7th generation, video game consoles did not have operating systems, and software had complete control over the hardware. While "running on the metal" is simple and efficient, the only security on such systems was the proprietary interfaces needed to load code onto the machine. If someone could fashion a device that could access the memory of one of these consoles, they could do effectively anything.

What did gamers do with this incredible power? Cheat at video games of course!

An entire cottage industry developed around cheating, with dedicated hardware, companies, jobs, and entire communities, all built on cheats! By the time the GameCube arrived, a cheat device video game enhancer was guaranteed to come out shortly after a console launched, a customer could buy one in the same retail store where they bought the console and buy games, and they could find tens of thousands of codes readily available for free on the internet! For a moment, cheating was mainstream (within the niche market that was video gaming at that time).

During this era, the kind of player who would buy a device to cheat at video games was also the kind of player who would dump their games to emulate them on PC. In fact, many game enhancers had the ability to dump games! This overlap made cheat support an essential feature for emulators. Because Dolphin's development began in this era, Dolphin supported Action Replay codes before it supported Wii games.

However, cheat systems are still just a way to edit memory. It didn't take long for emulator users to figure out that they could use cheat systems for far more than just cheating at video games. They could use cheats to change the game itself. Widescreen aspect ratio codes, anti-invert stick codes, bloom removal codes - most of the "cheats" being developed today aren't for cheating at all, but to adjust games to better fit modern sensibilities, add quality of life changes, or improve accessibility.

When RetroAchievement support in Dolphin launched late last year, cheats and many other features were disabled whenever RetroAchievements' hardcore mode was active. The leaderboard is for those that take achievements seriously and want a record of their accomplishments, so cheats could trivialize their efforts. But once RetroAchievement support was merged, those same overachievers pleaded with RA staff for limited cheat support in hardcore mode. Cheats remain the primary way to patch unfortunate game behaviors and add quality of life improvements, and the hardcore community wanted to be able to utilize those kinds of cheats while climbing the leaderboard.

After some deliberation within the RetroAchievements staff, the conclusion was an allowlist. Select and specific cheat codes are now able to be used in RetroAchievements' hardcore mode. Most of them are widescreen aspect ratio codes, but there are other changes as well, such as unlocking the C-Stick to smash feature in single player Super Smash Bros. Melee modes, or codes to fix game issues like freezes and bugs. Now overachievers can enjoy the thrills of Gotta Get 'Em All in the comfort of 16:9.

As part of this effort, LillyJadeKatrin went through our wiki looking for cheat codes, then spent hours adding hundreds of new cheats to Dolphin's built in cheat code database. Everyone benefits from this, whether achievement hunting or not!

Qt Input Mapping Lightning Round by Billiard

For the past couple of months, Billiard has been going through Dolphin's input mapping systems like a storm, cleaning up and improving dozens of things! There are too many for us to even show, but here are some highlights.

Note that most of these changes only apply to desktop builds of Dolphin; Android is not affected.

— 2412-105 - Make input mapping and output testing non-blocking

Input entry is now non-blocking, and multiple input mappings can be queued/un-queued/cleared without locking the UI.

— 2412-183 - DolphinQt: Replace MappingButton bold text with graphical indicators

For years, Dolphin's mapping windows have had some sort of indicator that would light up when the user presses a button that is mapped to an emulated button. This is a quick and easy way to confirm to the user that they have successfully mapped a button and that it is working correctly. However, how that indicator looks and works has changed dramatically.

When the mapping indicators were first introduced, they were red graphical indicators that were detached from their associated buttons.

When we moved from the WX interface to the Qt interface we now use on desktop, this was changed to lighting up the input within the mapped button itself simply by bolding it.

It was never a great solution, but it was good enough and was simple to implement in the storm that was our move to Qt. It left us a little wanting though.

Billiard, thinking back to the original design, realized that with Qt, we could do something MUCH better.

— 2412-289 - Add setting to enable waiting for alternate mappings

Dolphin's advanced mapping window is incredibly powerful, with all of our mapping complexity laid bare and ready for all the input shenanigans a power user could dream of. However, most users don't want to interact with all of our mapping complexity, but they may want to do some basics such as AND and OR. AND was possible simply by pressing two buttons at once, and then it would require the player to press both buttons to send the emulated input, simple. But OR required going into the advanced input mapping window. Given how often users want to be able to press either of two physical buttons to engage single emulated button, Billiard wanted some way to accomodate that without requiring users to plunge into the depths of our mapping system.

To achieve that goal, there is now a new option - Wait for Alternate Input Mappings. When this feature is enabled, there is a small delay added after each input, allowing users to make multiple individual inputs. For example, to map two physical buttons to one emulated button, with this feature all a user needs to do is press one button on their controller, then quickly press the next button. Now either input will trigger the emulated button. Simple as that!

To access this feature, click the arrow beside Refresh.

— 2412-292 - Add setting to enable iterative input mappings

Iterative input is a nice feature that can take some of the tedium away from configuring a controller. Having to look down, figure out what button you want to push, then use your mouse to go to the next input over and over again can be annoying, especially if you're just trying to set things up as a couch gamer. That's where iterative can really shine. But, unfortunately, its history with Dolphin has been rocky at best.

The upside is clear - with just a single click, iterative input allows a user to go through every input on the screen one by one without needing to return to your mouse or keyboard. This feature took so long to return because it's hard to do right, especially with controllers as complicated as the Wii Remote. Last time, problems were revealed and it was easier to remove it outright than to fix it.

Billiard has given it another go, with a brand new implementation that doesn't suffer any of the issues of the original. Plus, with the non-blocking changes above, it now is a much smoother experience simply from being implemented now. Iterative input is currently disabled by default, but can be enabled in the controller mapping window.

— Input mapping expression improvements - 2412-211, 2412-231, 2412-266 and more

For our advanced input mapping extraordinaires, Dolphin's input expression parser saw many improvements.

  • Conditional Operator Added
    Dolphin's mapping expressions have long provided an "if" function for creating conditional expressions: if(`A`, 1.0, 0.6)
    But this syntax can be cumbersome and unfamiliar, so the ternary conditional operator syntax that's present in many other programming languages has finally been added: `A` ? 1.0 : 0.6
  • Assignment Operator Fixed
    Probably unknown to most users, mapping expressions support user-defined variables. These can be used to share state across frames, with other mappings, or just in as a means of organization. This can allow for very customizable and dynamic control schemes. Variables are created with the $ symbol and can be given a value using the familiar assignment operator = . For instance: $x = `A` ? 1.0 : 0.6
    Sometimes writers of complex mapping expressions like to describe their calculations as a multiple step process. The comma operator was already provided for this, and functions like it does in other programming languages. This contrived example below effectively does the same thing as the previous example, but in two steps, which can sometimes create more-readable or maintainable code when the calculations get overly long winded. For example: $a = `A`, $x = $a ? 1.0 : 0.6
    For technical reasons that we won't get into, the previously mentioned assignment operator was implemented in a manner that did not play nice with the comma operator. It also didn't play nice with other assignment operators. While the operators worked fine in simple use-cases, power users could observe these two operators doing wrong or unexpected things when paired together.

    All of these *should* evaluate as 1.

    Comma and assignment operators can now be used together like intended and should do what someone familiar with them would expect them to do, even in complex cases.
  • Compound Assignment Operators Added
    One final nice-to-have was added to the mapping expressions - compound assignment operators. When altering a user-defined variable based on its current value, the variable name previously always had to be mentioned twice, once on either side of the assignment-operator. Here is an example that reduces the current value of a variable: $x = $x - 0.6
    So-called compound assignment operators are now provided to allow this previously verbose syntax to be much more succinct: $x -= 0.6
    This syntax can be used with all of the binary operators for which it makes sense: &|^+-*/%

2412-51 - Add ability to edit game-specific GFX settings from game properties tab by TryTwo

One thing that many users have been requesting for a very long time is a visual interface for editing per-game settings. While Dolphin has provided a single page with a few key settings, the majority of the settings had to be added via the text editor.

While this change doesn't add everything, now users can set most graphics settings directly in the game properties page. While this functionality already existed by using the text interface, the visual interface makes it easy to see what settings are force enabled, and allows users an easy way to set them without having to memorize the names of the settings.

Note that this feature should be considered a work in progress, and the current design may not reflect a more complete solution in the future.

2412-82 - AdvancedWidget: Replace FFV1 codec with Ut Video as Default by TryTwo

For those of you who do video dumping in Dolphin, you may have noticed that a lot of modern video editors didn't play nice with the lossless codec in Dolphin. That's because Dolphin used to default to the rather old FFV1 video codec. For TASers or people just wanting extremely high quality footage of the games, it frequently got in their way.

Fortunately, an alternative was added a few years ago - the Ut Video codec. This codec is what OBS chose for their lossless recording, granting it extremely widespread compatibility. Despite requiring an INI edit to use in Dolphin, the codec's popularity has compelled us to make the switch. By default Dolphin's lossless frame dumping feature will now use the Ut Video codec for greater compatibility. For those that want to still use FFV1, you still can do that through changing the config file manually.

2412-147 - Fix Summoner: Goddess Reborn sound system crash during transitions by Charlese2

Summoner: A Goddess Reborn has been a problematic title in Dolphin since the very beginning. While there were reports that some builds work better than others, the game has never been stable. In fact, playing through it from beginning to end in Dolphin was an arduous experience that meant dealing with crashes and constantly swapping between different CPU clock values in different parts of the game to just for a chance to get to the next section.

And now, we finally know why. This game is just broken and you can even cause the same crashes on console!

To be completely fair, the game isn't nearly as bad on console. While we did find some consistent crashes that helped us track down this bug, playing through the game isn't nearly as arduous. Still, the very same bug that causes the game to occasionally crash on console is what is causing it to crash in Dolphin, which means there isn't a great chance of us fixing it through emulation changes.

Charlese2 said enough was enough and decided to figure out what was going on with this mysterious crash. And within a few days, we had an answer. Summoner: A Goddess Reborn reinitializes its sound system buffers during transitions even if sounds are still being played. If there are still pointers in the sound list to sounds in the buffers when the buffers get cleared, the game crashes with a null pointer dereference.

This is a serious bug that should be affecting console at the same rate as Dolphin, but it doesn't. Our best guess is that the Audio Interface DMA interrupt timings are slightly different on console, which causes things to happen in a slightly different order most of the time. However, the bug is there - even in a perfect, cycle accurate emulator, Summoner would occasionally crash if it is not modified.

To address this, Charlese2 dove into the game and decided to fix the bug themselves! A lengthy patch (that is enabled by default in the latest builds of Dolphin) cleans up the pending sound list during sound system reinitialization before continuing to the sound system initialization call. With this patch, even known crashes when playing on console are fixed.

2412-305 - Track Time Played (Core and Qt) by aminoa

Tracking time played is something we almost take for granted these days. Whether you play on a Nintendo Switch, PlayStation, or Steam, all of these platforms track your playtime for all of their titles. It's just expected behavior now.

Dolphin however emulates the GameCube and Wii, consoles that came out long before this trend. Unlike modern systems, the GameCube didn't have a clue how many hours you've rolled around at the speed of sound, and the Wii would only show it on a day-by-day basis. But what if Dolphin could track your total play times?

And now it can! As of this change, Dolphin can now track the time played for all of its titles and display it in the game list.

Play time tracking is enabled by default, so all it takes to track your time played is a quick update to the latest Dolphin version! If you'd rather not, you can disable it by going to Config > Interface and unchecking Enable Time Tracking. You can also remove the time played column from the game list if you wish without impacting whether or not your play time is tracked.

Currently only our Qt graphical interface can display play time.

NOTE: Time played can only be tracked in 2412-305 and newer.

2412-321 - TAS: Use Improved Wii Remote Data Format by Billiard

For our TASers that need to use Wii Remotes, this is a long overdue change. For a basic rundown, when a person makes a Tool-Assisted Speedrun (TAS), they're essentially creating a long string of controller inputs that, when played back, completes a game quickly or accomplishes some other impressive feat. These controller inputs have to be stored in some way so they can be played back later. Like most emulators, Dolphin has a custom file format for this, and it's called DTM (Dolphin TAS Movie). It's a relatively simple format: 256 bytes of metadata and settings, followed by all the controller inputs and nothing else.

Depending on how optimized you intend your TAS to be, you might use Dolphin's input recordings alongside slowdown, frame-by-frame, savestates, or even rely on scripts (using specialized TASing forks) that generate inputs through bruteforcing across hundreds of hours!

Dolphin's DTM format was originally designed for GameCube controllers and works fairly well for them. For Wii Remotes, the format has been quite a bit more cumbersome. Wii Remotes are a nightmare for emulation on a level that no controller before them can match. The Bluetooth connectivity is annoying, you can swap attachments, it has an infrared receiver, a small amount of EEPROM, battery levels, and of course, its signature motion controls. In fact, a Wii Remote collects so much data that it can't be sent all at once! Games that support Wii Remotes have to tell them what reporting mode to use, with different reporting modes sending different data and using different levels of precision. And to make things even tricker, Nintendo decided to encrypt data from extension controllers. We don't know if this was to make things harder for third-party controller manufacturers or for some other reason, but we do know that it has made things harder both for TASers and Dolphin developers!

How do you bolt all of this into a format that was designed for GameCube controllers? Dolphin's solution was to store data in the same format a Wii Remote would send it, using whatever reporting mode the game specified. This did work, but came with a lot of consequences. At the start of a recording, you'd be locked into your Wii Remote configuration. You couldn't change attachments during a recording, and manually editing DTM files in a hex editor was almost impossible. The reason for this was that the game could change reporting modes throughout a playthrough, and if the wrong sort of data was provided at the wrong time, the game would refuse to accept it.

But it didn't have to be this way. When Wii Remotes were added to netplay, they suffered from all of these problems (and more!) which made Wii netplay into a nightmare. But, eventually AdmiralCurtiss addressed a lot of these issues to make Wii Remote netplay slightly more tolerable.

The new system, rather than naively copying the Wii Remote data as-is, used an intermediary structure that can then be translated into the game-requested format on the fly. This elegant solution allows the input data to be manipulated without fear of breakage from the ever-changing game state. On top of significantly improving stability, it gave support for more games by allowing users to change attachments mid-session.

While it may not seem like it at first glance, a lot of what netplay does overlaps with "movie" support which is used for TASing. They both require absolute determinism, recording inputs, and playing back inputs. When looking for ways to improve things for TASers, Billiard realized that AdmiralCurtiss's netplay improvements were never ported over to movies! He decided to replace the old way of storing Wii Remote data in DTM files with netplay's intermediary format, bringing many of the improvements over.

We're hoping that this new format makes creating optimized Wii TASes easier and more stable. On the Dolphin side of things, it was also a maintenance win. A bunch of ugly code related to reporting modes and extension data encryption became unnecessary and was removed. As per usual, if you've started a TAS on an older build of Dolphin, you're more-or-less stuck there. Not only is the new DTM format incompatible with the old one, any minor change to Dolphin could break the syncing of a TAS. When creating a new TAS, please ensure that the build of Dolphin you're using supports the feature set you need to accomplish your goals. This goes for whether you're using an official build of Dolphin or a scripting fork. And for the TASers out there doing crazy things in Dolphin, we're always looking forward to seeing what you do next.


This Release's Contributors...

Special thanks to all of the contributors that incremented Dolphin by 341 commits after Release 2412!


2503
  • Ajout d’un système de paramètres graphiques personnalisables par jeu directement dans l’onglet Propriétés du jeu, avec une interface visuelle simplifiée.
  • Correction d’un crash lié à la mémoire sur certaines versions anciennes de macOS, ainsi que d’un problème de connectivité GBA dans certains jeux.
  • Correction d’un bug de build rendant la version 2503 identifiable comme une bêta 2412 sur certaines plateformes.
  • Activation d’une liste blanche de codes tricheurs pour RetroAchievements en mode Hardcore, incluant des codes pour le widescreen, l’activation du C-Stick ou des corrections de bugs.
  • Amélioration majeure des mappings d’entrée Qt : suppression des blocages pendant la configuration, ajout d’indicateurs graphiques, et options pour les entrées alternatives ou itératives.
  • Ajout d’un suivi du temps de jeu (affichable dans la liste des jeux) via l’interface Qt, activé par défaut.

It's time for us to again delve into the latest changes hitting the newest release of Dolphin Emulator. If you've been keeping tabs on development channels, you'll know there are some exciting bombshell features waiting for us just over the horizon. Unfortunately, given the close proximity to this release, we've decided to hold a lot of them off so they can get more widespread testing in the development builds before hitting a release. Think of the March 2025 release as an iterative improvement that focuses on user experience and stacking many small iterative improvements instead of swinging for every homerun.

Having said all of that? We do have a few major changes that made the cut.

Probably the most requested of the features in this progress report is the ability to finally set custom graphical settings on a per game basis. Our advanced users may be thinking, "Wait, couldn't we already do that?" and they'd be right. The major change here is that per-game graphical settings has been added directly to the game properties page, allowing for a very easy, visual way to change settings and see what settings are force enabled.

For our achievement hunters out there, RetroAchievements has seen its first major upgrade that will bring a huge amount of quality of life to many games. And if you're into weird old game behaviors? A developer dove into Summoner: A Goddess Reborn to determine why it crashes so much. The catch with this one? Some of these crashes have been confirmed to happen on official hardware!

Additionally, there are a plethora of small, but tangible, changes that are the hallmark of an Open Source project. The desktop versions of Dolphin also saw a lot of improvements to input configuration and a few extra upgrades that might make people who want to track their time spent in games very happy. But, let's not spoil everything and get into the notable changes of the March 2025 release!

Release 2503a

On April 21 2025, we created Hotfix Release 2503a to fix some problems that snuck into Release 2503:

  • Fixed a bug that caused GBA connectivity in some games to not work properly.
  • Fixed a bug where Dolphin would crash with a memory error on some older macOS versions.
  • Fixed an problem with our build system which caused Release 2503 to be mislabeled as a 2412 development build on some platforms.

Notable Changes

Cheat Code Whitelist for Hardcore RetroAchievements - 2412-8 and 2412-173 by LillyJadeKatrin

RetroAchievements in Dolphin has received its first major update, and it's... cheat support in hardcore?! What gives?

Up until around the 7th generation, video game consoles did not have operating systems, and software had complete control over the hardware. While "running on the metal" is simple and efficient, the only security on such systems was the proprietary interfaces needed to load code onto the machine. If someone could fashion a device that could access the memory of one of these consoles, they could do effectively anything.

What did gamers do with this incredible power? Cheat at video games of course!

An entire cottage industry developed around cheating, with dedicated hardware, companies, jobs, and entire communities, all built on cheats! By the time the GameCube arrived, a cheat device video game enhancer was guaranteed to come out shortly after a console launched, a customer could buy one in the same retail store where they bought the console and buy games, and they could find tens of thousands of codes readily available for free on the internet! For a moment, cheating was mainstream (within the niche market that was video gaming at that time).

During this era, the kind of player who would buy a device to cheat at video games was also the kind of player who would dump their games to emulate them on PC. In fact, many game enhancers had the ability to dump games! This overlap made cheat support an essential feature for emulators. Because Dolphin's development began in this era, Dolphin supported Action Replay codes before it supported Wii games.

However, cheat systems are still just a way to edit memory. It didn't take long for emulator users to figure out that they could use cheat systems for far more than just cheating at video games. They could use cheats to change the game itself. Widescreen aspect ratio codes, anti-invert stick codes, bloom removal codes - most of the "cheats" being developed today aren't for cheating at all, but to adjust games to better fit modern sensibilities, add quality of life changes, or improve accessibility.

When RetroAchievement support in Dolphin launched late last year, cheats and many other features were disabled whenever RetroAchievements' hardcore mode was active. The leaderboard is for those that take achievements seriously and want a record of their accomplishments, so cheats could trivialize their efforts. But once RetroAchievement support was merged, those same overachievers pleaded with RA staff for limited cheat support in hardcore mode. Cheats remain the primary way to patch unfortunate game behaviors and add quality of life improvements, and the hardcore community wanted to be able to utilize those kinds of cheats while climbing the leaderboard.

After some deliberation within the RetroAchievements staff, the conclusion was an allowlist. Select and specific cheat codes are now able to be used in RetroAchievements' hardcore mode. Most of them are widescreen aspect ratio codes, but there are other changes as well, such as unlocking the C-Stick to smash feature in single player Super Smash Bros. Melee modes, or codes to fix game issues like freezes and bugs. Now overachievers can enjoy the thrills of Gotta Get 'Em All in the comfort of 16:9.

As part of this effort, LillyJadeKatrin went through our wiki looking for cheat codes, then spent hours adding hundreds of new cheats to Dolphin's built in cheat code database. Everyone benefits from this, whether achievement hunting or not!

Qt Input Mapping Lightning Round by Billiard

For the past couple of months, Billiard has been going through Dolphin's input mapping systems like a storm, cleaning up and improving dozens of things! There are too many for us to even show, but here are some highlights.

Note that most of these changes only apply to desktop builds of Dolphin; Android is not affected.

— 2412-105 - Make input mapping and output testing non-blocking

Input entry is now non-blocking, and multiple input mappings can be queued/un-queued/cleared without locking the UI.

— 2412-183 - DolphinQt: Replace MappingButton bold text with graphical indicators

For years, Dolphin's mapping windows have had some sort of indicator that would light up when the user presses a button that is mapped to an emulated button. This is a quick and easy way to confirm to the user that they have successfully mapped a button and that it is working correctly. However, how that indicator looks and works has changed dramatically.

When the mapping indicators were first introduced, they were red graphical indicators that were detached from their associated buttons.

When we moved from the WX interface to the Qt interface we now use on desktop, this was changed to lighting up the input within the mapped button itself simply by bolding it.

It was never a great solution, but it was good enough and was simple to implement in the storm that was our move to Qt. It left us a little wanting though.

Billiard, thinking back to the original design, realized that with Qt, we could do something MUCH better.

— 2412-289 - Add setting to enable waiting for alternate mappings

Dolphin's advanced mapping window is incredibly powerful, with all of our mapping complexity laid bare and ready for all the input shenanigans a power user could dream of. However, most users don't want to interact with all of our mapping complexity, but they may want to do some basics such as AND and OR. AND was possible simply by pressing two buttons at once, and then it would require the player to press both buttons to send the emulated input, simple. But OR required going into the advanced input mapping window. Given how often users want to be able to press either of two physical buttons to engage single emulated button, Billiard wanted some way to accomodate that without requiring users to plunge into the depths of our mapping system.

To achieve that goal, there is now a new option - Wait for Alternate Input Mappings. When this feature is enabled, there is a small delay added after each input, allowing users to make multiple individual inputs. For example, to map two physical buttons to one emulated button, with this feature all a user needs to do is press one button on their controller, then quickly press the next button. Now either input will trigger the emulated button. Simple as that!

To access this feature, click the arrow beside Refresh.

— 2412-292 - Add setting to enable iterative input mappings

Iterative input is a nice feature that can take some of the tedium away from configuring a controller. Having to look down, figure out what button you want to push, then use your mouse to go to the next input over and over again can be annoying, especially if you're just trying to set things up as a couch gamer. That's where iterative can really shine. But, unfortunately, its history with Dolphin has been rocky at best.

The upside is clear - with just a single click, iterative input allows a user to go through every input on the screen one by one without needing to return to your mouse or keyboard. This feature took so long to return because it's hard to do right, especially with controllers as complicated as the Wii Remote. Last time, problems were revealed and it was easier to remove it outright than to fix it.

Billiard has given it another go, with a brand new implementation that doesn't suffer any of the issues of the original. Plus, with the non-blocking changes above, it now is a much smoother experience simply from being implemented now. Iterative input is currently disabled by default, but can be enabled in the controller mapping window.

— Input mapping expression improvements - 2412-211, 2412-231, 2412-266 and more

For our advanced input mapping extraordinaires, Dolphin's input expression parser saw many improvements.

  • Conditional Operator Added
    Dolphin's mapping expressions have long provided an "if" function for creating conditional expressions: if(`A`, 1.0, 0.6)
    But this syntax can be cumbersome and unfamiliar, so the ternary conditional operator syntax that's present in many other programming languages has finally been added: `A` ? 1.0 : 0.6
  • Assignment Operator Fixed
    Probably unknown to most users, mapping expressions support user-defined variables. These can be used to share state across frames, with other mappings, or just in as a means of organization. This can allow for very customizable and dynamic control schemes. Variables are created with the $ symbol and can be given a value using the familiar assignment operator = . For instance: $x = `A` ? 1.0 : 0.6
    Sometimes writers of complex mapping expressions like to describe their calculations as a multiple step process. The comma operator was already provided for this, and functions like it does in other programming languages. This contrived example below effectively does the same thing as the previous example, but in two steps, which can sometimes create more-readable or maintainable code when the calculations get overly long winded. For example: $a = `A`, $x = $a ? 1.0 : 0.6
    For technical reasons that we won't get into, the previously mentioned assignment operator was implemented in a manner that did not play nice with the comma operator. It also didn't play nice with other assignment operators. While the operators worked fine in simple use-cases, power users could observe these two operators doing wrong or unexpected things when paired together.

    All of these *should* evaluate as 1.

    Comma and assignment operators can now be used together like intended and should do what someone familiar with them would expect them to do, even in complex cases.
  • Compound Assignment Operators Added
    One final nice-to-have was added to the mapping expressions - compound assignment operators. When altering a user-defined variable based on its current value, the variable name previously always had to be mentioned twice, once on either side of the assignment-operator. Here is an example that reduces the current value of a variable: $x = $x - 0.6
    So-called compound assignment operators are now provided to allow this previously verbose syntax to be much more succinct: $x -= 0.6
    This syntax can be used with all of the binary operators for which it makes sense: &|^+-*/%

2412-51 - Add ability to edit game-specific GFX settings from game properties tab by TryTwo

One thing that many users have been requesting for a very long time is a visual interface for editing per-game settings. While Dolphin has provided a single page with a few key settings, the majority of the settings had to be added via the text editor.

While this change doesn't add everything, now users can set most graphics settings directly in the game properties page. While this functionality already existed by using the text interface, the visual interface makes it easy to see what settings are force enabled, and allows users an easy way to set them without having to memorize the names of the settings.

Note that this feature should be considered a work in progress, and the current design may not reflect a more complete solution in the future.

2412-82 - AdvancedWidget: Replace FFV1 codec with Ut Video as Default by TryTwo

For those of you who do video dumping in Dolphin, you may have noticed that a lot of modern video editors didn't play nice with the lossless codec in Dolphin. That's because Dolphin used to default to the rather old FFV1 video codec. For TASers or people just wanting extremely high quality footage of the games, it frequently got in their way.

Fortunately, an alternative was added a few years ago - the Ut Video codec. This codec is what OBS chose for their lossless recording, granting it extremely widespread compatibility. Despite requiring an INI edit to use in Dolphin, the codec's popularity has compelled us to make the switch. By default Dolphin's lossless frame dumping feature will now use the Ut Video codec for greater compatibility. For those that want to still use FFV1, you still can do that through changing the config file manually.

2412-147 - Fix Summoner: Goddess Reborn sound system crash during transitions by Charlese2

Summoner: A Goddess Reborn has been a problematic title in Dolphin since the very beginning. While there were reports that some builds work better than others, the game has never been stable. In fact, playing through it from beginning to end in Dolphin was an arduous experience that meant dealing with crashes and constantly swapping between different CPU clock values in different parts of the game to just for a chance to get to the next section.

And now, we finally know why. This game is just broken and you can even cause the same crashes on console!

To be completely fair, the game isn't nearly as bad on console. While we did find some consistent crashes that helped us track down this bug, playing through the game isn't nearly as arduous. Still, the very same bug that causes the game to occasionally crash on console is what is causing it to crash in Dolphin, which means there isn't a great chance of us fixing it through emulation changes.

Charlese2 said enough was enough and decided to figure out what was going on with this mysterious crash. And within a few days, we had an answer. Summoner: A Goddess Reborn reinitializes its sound system buffers during transitions even if sounds are still being played. If there are still pointers in the sound list to sounds in the buffers when the buffers get cleared, the game crashes with a null pointer dereference.

This is a serious bug that should be affecting console at the same rate as Dolphin, but it doesn't. Our best guess is that the Audio Interface DMA interrupt timings are slightly different on console, which causes things to happen in a slightly different order most of the time. However, the bug is there - even in a perfect, cycle accurate emulator, Summoner would occasionally crash if it is not modified.

To address this, Charlese2 dove into the game and decided to fix the bug themselves! A lengthy patch (that is enabled by default in the latest builds of Dolphin) cleans up the pending sound list during sound system reinitialization before continuing to the sound system initialization call. With this patch, even known crashes when playing on console are fixed.

2412-305 - Track Time Played (Core and Qt) by aminoa

Tracking time played is something we almost take for granted these days. Whether you play on a Nintendo Switch, PlayStation, or Steam, all of these platforms track your playtime for all of their titles. It's just expected behavior now.

Dolphin however emulates the GameCube and Wii, consoles that came out long before this trend. Unlike modern systems, the GameCube didn't have a clue how many hours you've rolled around at the speed of sound, and the Wii would only show it on a day-by-day basis. But what if Dolphin could track your total play times?

And now it can! As of this change, Dolphin can now track the time played for all of its titles and display it in the game list.

Play time tracking is enabled by default, so all it takes to track your time played is a quick update to the latest Dolphin version! If you'd rather not, you can disable it by going to Config > Interface and unchecking Enable Time Tracking. You can also remove the time played column from the game list if you wish without impacting whether or not your play time is tracked.

Currently only our Qt graphical interface can display play time.

NOTE: Time played can only be tracked in 2412-305 and newer.

2412-321 - TAS: Use Improved Wii Remote Data Format by Billiard

For our TASers that need to use Wii Remotes, this is a long overdue change. For a basic rundown, when a person makes a Tool-Assisted Speedrun (TAS), they're essentially creating a long string of controller inputs that, when played back, completes a game quickly or accomplishes some other impressive feat. These controller inputs have to be stored in some way so they can be played back later. Like most emulators, Dolphin has a custom file format for this, and it's called DTM (Dolphin TAS Movie). It's a relatively simple format: 256 bytes of metadata and settings, followed by all the controller inputs and nothing else.

Depending on how optimized you intend your TAS to be, you might use Dolphin's input recordings alongside slowdown, frame-by-frame, savestates, or even rely on scripts (using specialized TASing forks) that generate inputs through bruteforcing across hundreds of hours!

Dolphin's DTM format was originally designed for GameCube controllers and works fairly well for them. For Wii Remotes, the format has been quite a bit more cumbersome. Wii Remotes are a nightmare for emulation on a level that no controller before them can match. The Bluetooth connectivity is annoying, you can swap attachments, it has an infrared receiver, a small amount of EEPROM, battery levels, and of course, its signature motion controls. In fact, a Wii Remote collects so much data that it can't be sent all at once! Games that support Wii Remotes have to tell them what reporting mode to use, with different reporting modes sending different data and using different levels of precision. And to make things even tricker, Nintendo decided to encrypt data from extension controllers. We don't know if this was to make things harder for third-party controller manufacturers or for some other reason, but we do know that it has made things harder both for TASers and Dolphin developers!

How do you bolt all of this into a format that was designed for GameCube controllers? Dolphin's solution was to store data in the same format a Wii Remote would send it, using whatever reporting mode the game specified. This did work, but came with a lot of consequences. At the start of a recording, you'd be locked into your Wii Remote configuration. You couldn't change attachments during a recording, and manually editing DTM files in a hex editor was almost impossible. The reason for this was that the game could change reporting modes throughout a playthrough, and if the wrong sort of data was provided at the wrong time, the game would refuse to accept it.

But it didn't have to be this way. When Wii Remotes were added to netplay, they suffered from all of these problems (and more!) which made Wii netplay into a nightmare. But, eventually AdmiralCurtiss addressed a lot of these issues to make Wii Remote netplay slightly more tolerable.

The new system, rather than naively copying the Wii Remote data as-is, used an intermediary structure that can then be translated into the game-requested format on the fly. This elegant solution allows the input data to be manipulated without fear of breakage from the ever-changing game state. On top of significantly improving stability, it gave support for more games by allowing users to change attachments mid-session.

While it may not seem like it at first glance, a lot of what netplay does overlaps with "movie" support which is used for TASing. They both require absolute determinism, recording inputs, and playing back inputs. When looking for ways to improve things for TASers, Billiard realized that AdmiralCurtiss's netplay improvements were never ported over to movies! He decided to replace the old way of storing Wii Remote data in DTM files with netplay's intermediary format, bringing many of the improvements over.

We're hoping that this new format makes creating optimized Wii TASes easier and more stable. On the Dolphin side of things, it was also a maintenance win. A bunch of ugly code related to reporting modes and extension data encryption became unnecessary and was removed. As per usual, if you've started a TAS on an older build of Dolphin, you're more-or-less stuck there. Not only is the new DTM format incompatible with the old one, any minor change to Dolphin could break the syncing of a TAS. When creating a new TAS, please ensure that the build of Dolphin you're using supports the feature set you need to accomplish your goals. This goes for whether you're using an official build of Dolphin or a scripting fork. And for the TASers out there doing crazy things in Dolphin, we're always looking forward to seeing what you do next.


This Release's Contributors...

Special thanks to all of the contributors that incremented Dolphin by 341 commits after Release 2412!


2503
  • Ajout d’un système de paramètres graphiques personnalisables par jeu directement dans l’onglet Propriétés du jeu, avec une interface visuelle simplifiée.
  • Correction d’un crash lié à la mémoire sur certaines versions anciennes de macOS et d’un bug de connectivité GBA dans certains jeux.
  • Mise à jour majeure de RetroAchievements avec une liste blanche de codes de triche pour le mode Hardcore, incluant des ajustements qualité de vie (ex. : aspect ratio 16:9, débloquage de fonctionnalités).
  • Améliorations des mappings d’entrée (Qt) : suppression des blocages lors de la configuration, ajout d’indicateurs graphiques pour les boutons, option d’attente pour les mappings alternatifs et activation de l’entrée itérative.
  • Ajout d’un suivi du temps de jeu (affichage dans la liste des jeux via l’interface Qt), activé par défaut.
  • Correction d’un crash du système sonore dans Summoner: A Goddess Reborn lors des transitions, reproduisant même sur le matériel officiel.

It's time for us to again delve into the latest changes hitting the newest release of Dolphin Emulator. If you've been keeping tabs on development channels, you'll know there are some exciting bombshell features waiting for us just over the horizon. Unfortunately, given the close proximity to this release, we've decided to hold a lot of them off so they can get more widespread testing in the development builds before hitting a release. Think of the March 2025 release as an iterative improvement that focuses on user experience and stacking many small iterative improvements instead of swinging for every homerun.

Having said all of that? We do have a few major changes that made the cut.

Probably the most requested of the features in this progress report is the ability to finally set custom graphical settings on a per game basis. Our advanced users may be thinking, "Wait, couldn't we already do that?" and they'd be right. The major change here is that per-game graphical settings has been added directly to the game properties page, allowing for a very easy, visual way to change settings and see what settings are force enabled.

For our achievement hunters out there, RetroAchievements has seen its first major upgrade that will bring a huge amount of quality of life to many games. And if you're into weird old game behaviors? A developer dove into Summoner: A Goddess Reborn to determine why it crashes so much. The catch with this one? Some of these crashes have been confirmed to happen on official hardware!

Additionally, there are a plethora of small, but tangible, changes that are the hallmark of an Open Source project. The desktop versions of Dolphin also saw a lot of improvements to input configuration and a few extra upgrades that might make people who want to track their time spent in games very happy. But, let's not spoil everything and get into the notable changes of the March 2025 release!

Release 2503a

On April 21 2025, we created Hotfix Release 2503a to fix some problems that snuck into Release 2503:

  • Fixed a bug that caused GBA connectivity in some games to not work properly.
  • Fixed a bug where Dolphin would crash with a memory error on some older macOS versions.
  • Fixed an problem with our build system which caused Release 2503 to be mislabeled as a 2412 development build on some platforms.

Notable Changes

Cheat Code Whitelist for Hardcore RetroAchievements - 2412-8 and 2412-173 by LillyJadeKatrin

RetroAchievements in Dolphin has received its first major update, and it's... cheat support in hardcore?! What gives?

Up until around the 7th generation, video game consoles did not have operating systems, and software had complete control over the hardware. While "running on the metal" is simple and efficient, the only security on such systems was the proprietary interfaces needed to load code onto the machine. If someone could fashion a device that could access the memory of one of these consoles, they could do effectively anything.

What did gamers do with this incredible power? Cheat at video games of course!

An entire cottage industry developed around cheating, with dedicated hardware, companies, jobs, and entire communities, all built on cheats! By the time the GameCube arrived, a cheat device video game enhancer was guaranteed to come out shortly after a console launched, a customer could buy one in the same retail store where they bought the console and buy games, and they could find tens of thousands of codes readily available for free on the internet! For a moment, cheating was mainstream (within the niche market that was video gaming at that time).

During this era, the kind of player who would buy a device to cheat at video games was also the kind of player who would dump their games to emulate them on PC. In fact, many game enhancers had the ability to dump games! This overlap made cheat support an essential feature for emulators. Because Dolphin's development began in this era, Dolphin supported Action Replay codes before it supported Wii games.

However, cheat systems are still just a way to edit memory. It didn't take long for emulator users to figure out that they could use cheat systems for far more than just cheating at video games. They could use cheats to change the game itself. Widescreen aspect ratio codes, anti-invert stick codes, bloom removal codes - most of the "cheats" being developed today aren't for cheating at all, but to adjust games to better fit modern sensibilities, add quality of life changes, or improve accessibility.

When RetroAchievement support in Dolphin launched late last year, cheats and many other features were disabled whenever RetroAchievements' hardcore mode was active. The leaderboard is for those that take achievements seriously and want a record of their accomplishments, so cheats could trivialize their efforts. But once RetroAchievement support was merged, those same overachievers pleaded with RA staff for limited cheat support in hardcore mode. Cheats remain the primary way to patch unfortunate game behaviors and add quality of life improvements, and the hardcore community wanted to be able to utilize those kinds of cheats while climbing the leaderboard.

After some deliberation within the RetroAchievements staff, the conclusion was an allowlist. Select and specific cheat codes are now able to be used in RetroAchievements' hardcore mode. Most of them are widescreen aspect ratio codes, but there are other changes as well, such as unlocking the C-Stick to smash feature in single player Super Smash Bros. Melee modes, or codes to fix game issues like freezes and bugs. Now overachievers can enjoy the thrills of Gotta Get 'Em All in the comfort of 16:9.

As part of this effort, LillyJadeKatrin went through our wiki looking for cheat codes, then spent hours adding hundreds of new cheats to Dolphin's built in cheat code database. Everyone benefits from this, whether achievement hunting or not!

Qt Input Mapping Lightning Round by Billiard

For the past couple of months, Billiard has been going through Dolphin's input mapping systems like a storm, cleaning up and improving dozens of things! There are too many for us to even show, but here are some highlights.

Note that most of these changes only apply to desktop builds of Dolphin; Android is not affected.

— 2412-105 - Make input mapping and output testing non-blocking

Input entry is now non-blocking, and multiple input mappings can be queued/un-queued/cleared without locking the UI.

— 2412-183 - DolphinQt: Replace MappingButton bold text with graphical indicators

For years, Dolphin's mapping windows have had some sort of indicator that would light up when the user presses a button that is mapped to an emulated button. This is a quick and easy way to confirm to the user that they have successfully mapped a button and that it is working correctly. However, how that indicator looks and works has changed dramatically.

When the mapping indicators were first introduced, they were red graphical indicators that were detached from their associated buttons.

When we moved from the WX interface to the Qt interface we now use on desktop, this was changed to lighting up the input within the mapped button itself simply by bolding it.

It was never a great solution, but it was good enough and was simple to implement in the storm that was our move to Qt. It left us a little wanting though.

Billiard, thinking back to the original design, realized that with Qt, we could do something MUCH better.

— 2412-289 - Add setting to enable waiting for alternate mappings

Dolphin's advanced mapping window is incredibly powerful, with all of our mapping complexity laid bare and ready for all the input shenanigans a power user could dream of. However, most users don't want to interact with all of our mapping complexity, but they may want to do some basics such as AND and OR. AND was possible simply by pressing two buttons at once, and then it would require the player to press both buttons to send the emulated input, simple. But OR required going into the advanced input mapping window. Given how often users want to be able to press either of two physical buttons to engage single emulated button, Billiard wanted some way to accomodate that without requiring users to plunge into the depths of our mapping system.

To achieve that goal, there is now a new option - Wait for Alternate Input Mappings. When this feature is enabled, there is a small delay added after each input, allowing users to make multiple individual inputs. For example, to map two physical buttons to one emulated button, with this feature all a user needs to do is press one button on their controller, then quickly press the next button. Now either input will trigger the emulated button. Simple as that!

To access this feature, click the arrow beside Refresh.

— 2412-292 - Add setting to enable iterative input mappings

Iterative input is a nice feature that can take some of the tedium away from configuring a controller. Having to look down, figure out what button you want to push, then use your mouse to go to the next input over and over again can be annoying, especially if you're just trying to set things up as a couch gamer. That's where iterative can really shine. But, unfortunately, its history with Dolphin has been rocky at best.

The upside is clear - with just a single click, iterative input allows a user to go through every input on the screen one by one without needing to return to your mouse or keyboard. This feature took so long to return because it's hard to do right, especially with controllers as complicated as the Wii Remote. Last time, problems were revealed and it was easier to remove it outright than to fix it.

Billiard has given it another go, with a brand new implementation that doesn't suffer any of the issues of the original. Plus, with the non-blocking changes above, it now is a much smoother experience simply from being implemented now. Iterative input is currently disabled by default, but can be enabled in the controller mapping window.

— Input mapping expression improvements - 2412-211, 2412-231, 2412-266 and more

For our advanced input mapping extraordinaires, Dolphin's input expression parser saw many improvements.

  • Conditional Operator Added
    Dolphin's mapping expressions have long provided an "if" function for creating conditional expressions: if(`A`, 1.0, 0.6)
    But this syntax can be cumbersome and unfamiliar, so the ternary conditional operator syntax that's present in many other programming languages has finally been added: `A` ? 1.0 : 0.6
  • Assignment Operator Fixed
    Probably unknown to most users, mapping expressions support user-defined variables. These can be used to share state across frames, with other mappings, or just in as a means of organization. This can allow for very customizable and dynamic control schemes. Variables are created with the $ symbol and can be given a value using the familiar assignment operator = . For instance: $x = `A` ? 1.0 : 0.6
    Sometimes writers of complex mapping expressions like to describe their calculations as a multiple step process. The comma operator was already provided for this, and functions like it does in other programming languages. This contrived example below effectively does the same thing as the previous example, but in two steps, which can sometimes create more-readable or maintainable code when the calculations get overly long winded. For example: $a = `A`, $x = $a ? 1.0 : 0.6
    For technical reasons that we won't get into, the previously mentioned assignment operator was implemented in a manner that did not play nice with the comma operator. It also didn't play nice with other assignment operators. While the operators worked fine in simple use-cases, power users could observe these two operators doing wrong or unexpected things when paired together.

    All of these *should* evaluate as 1.

    Comma and assignment operators can now be used together like intended and should do what someone familiar with them would expect them to do, even in complex cases.
  • Compound Assignment Operators Added
    One final nice-to-have was added to the mapping expressions - compound assignment operators. When altering a user-defined variable based on its current value, the variable name previously always had to be mentioned twice, once on either side of the assignment-operator. Here is an example that reduces the current value of a variable: $x = $x - 0.6
    So-called compound assignment operators are now provided to allow this previously verbose syntax to be much more succinct: $x -= 0.6
    This syntax can be used with all of the binary operators for which it makes sense: &|^+-*/%

2412-51 - Add ability to edit game-specific GFX settings from game properties tab by TryTwo

One thing that many users have been requesting for a very long time is a visual interface for editing per-game settings. While Dolphin has provided a single page with a few key settings, the majority of the settings had to be added via the text editor.

While this change doesn't add everything, now users can set most graphics settings directly in the game properties page. While this functionality already existed by using the text interface, the visual interface makes it easy to see what settings are force enabled, and allows users an easy way to set them without having to memorize the names of the settings.

Note that this feature should be considered a work in progress, and the current design may not reflect a more complete solution in the future.

2412-82 - AdvancedWidget: Replace FFV1 codec with Ut Video as Default by TryTwo

For those of you who do video dumping in Dolphin, you may have noticed that a lot of modern video editors didn't play nice with the lossless codec in Dolphin. That's because Dolphin used to default to the rather old FFV1 video codec. For TASers or people just wanting extremely high quality footage of the games, it frequently got in their way.

Fortunately, an alternative was added a few years ago - the Ut Video codec. This codec is what OBS chose for their lossless recording, granting it extremely widespread compatibility. Despite requiring an INI edit to use in Dolphin, the codec's popularity has compelled us to make the switch. By default Dolphin's lossless frame dumping feature will now use the Ut Video codec for greater compatibility. For those that want to still use FFV1, you still can do that through changing the config file manually.

2412-147 - Fix Summoner: Goddess Reborn sound system crash during transitions by Charlese2

Summoner: A Goddess Reborn has been a problematic title in Dolphin since the very beginning. While there were reports that some builds work better than others, the game has never been stable. In fact, playing through it from beginning to end in Dolphin was an arduous experience that meant dealing with crashes and constantly swapping between different CPU clock values in different parts of the game to just for a chance to get to the next section.

And now, we finally know why. This game is just broken and you can even cause the same crashes on console!

To be completely fair, the game isn't nearly as bad on console. While we did find some consistent crashes that helped us track down this bug, playing through the game isn't nearly as arduous. Still, the very same bug that causes the game to occasionally crash on console is what is causing it to crash in Dolphin, which means there isn't a great chance of us fixing it through emulation changes.

Charlese2 said enough was enough and decided to figure out what was going on with this mysterious crash. And within a few days, we had an answer. Summoner: A Goddess Reborn reinitializes its sound system buffers during transitions even if sounds are still being played. If there are still pointers in the sound list to sounds in the buffers when the buffers get cleared, the game crashes with a null pointer dereference.

This is a serious bug that should be affecting console at the same rate as Dolphin, but it doesn't. Our best guess is that the Audio Interface DMA interrupt timings are slightly different on console, which causes things to happen in a slightly different order most of the time. However, the bug is there - even in a perfect, cycle accurate emulator, Summoner would occasionally crash if it is not modified.

To address this, Charlese2 dove into the game and decided to fix the bug themselves! A lengthy patch (that is enabled by default in the latest builds of Dolphin) cleans up the pending sound list during sound system reinitialization before continuing to the sound system initialization call. With this patch, even known crashes when playing on console are fixed.

2412-305 - Track Time Played (Core and Qt) by aminoa

Tracking time played is something we almost take for granted these days. Whether you play on a Nintendo Switch, PlayStation, or Steam, all of these platforms track your playtime for all of their titles. It's just expected behavior now.

Dolphin however emulates the GameCube and Wii, consoles that came out long before this trend. Unlike modern systems, the GameCube didn't have a clue how many hours you've rolled around at the speed of sound, and the Wii would only show it on a day-by-day basis. But what if Dolphin could track your total play times?

And now it can! As of this change, Dolphin can now track the time played for all of its titles and display it in the game list.

Play time tracking is enabled by default, so all it takes to track your time played is a quick update to the latest Dolphin version! If you'd rather not, you can disable it by going to Config > Interface and unchecking Enable Time Tracking. You can also remove the time played column from the game list if you wish without impacting whether or not your play time is tracked.

Currently only our Qt graphical interface can display play time.

NOTE: Time played can only be tracked in 2412-305 and newer.

2412-321 - TAS: Use Improved Wii Remote Data Format by Billiard

For our TASers that need to use Wii Remotes, this is a long overdue change. For a basic rundown, when a person makes a Tool-Assisted Speedrun (TAS), they're essentially creating a long string of controller inputs that, when played back, completes a game quickly or accomplishes some other impressive feat. These controller inputs have to be stored in some way so they can be played back later. Like most emulators, Dolphin has a custom file format for this, and it's called DTM (Dolphin TAS Movie). It's a relatively simple format: 256 bytes of metadata and settings, followed by all the controller inputs and nothing else.

Depending on how optimized you intend your TAS to be, you might use Dolphin's input recordings alongside slowdown, frame-by-frame, savestates, or even rely on scripts (using specialized TASing forks) that generate inputs through bruteforcing across hundreds of hours!

Dolphin's DTM format was originally designed for GameCube controllers and works fairly well for them. For Wii Remotes, the format has been quite a bit more cumbersome. Wii Remotes are a nightmare for emulation on a level that no controller before them can match. The Bluetooth connectivity is annoying, you can swap attachments, it has an infrared receiver, a small amount of EEPROM, battery levels, and of course, its signature motion controls. In fact, a Wii Remote collects so much data that it can't be sent all at once! Games that support Wii Remotes have to tell them what reporting mode to use, with different reporting modes sending different data and using different levels of precision. And to make things even tricker, Nintendo decided to encrypt data from extension controllers. We don't know if this was to make things harder for third-party controller manufacturers or for some other reason, but we do know that it has made things harder both for TASers and Dolphin developers!

How do you bolt all of this into a format that was designed for GameCube controllers? Dolphin's solution was to store data in the same format a Wii Remote would send it, using whatever reporting mode the game specified. This did work, but came with a lot of consequences. At the start of a recording, you'd be locked into your Wii Remote configuration. You couldn't change attachments during a recording, and manually editing DTM files in a hex editor was almost impossible. The reason for this was that the game could change reporting modes throughout a playthrough, and if the wrong sort of data was provided at the wrong time, the game would refuse to accept it.

But it didn't have to be this way. When Wii Remotes were added to netplay, they suffered from all of these problems (and more!) which made Wii netplay into a nightmare. But, eventually AdmiralCurtiss addressed a lot of these issues to make Wii Remote netplay slightly more tolerable.

The new system, rather than naively copying the Wii Remote data as-is, used an intermediary structure that can then be translated into the game-requested format on the fly. This elegant solution allows the input data to be manipulated without fear of breakage from the ever-changing game state. On top of significantly improving stability, it gave support for more games by allowing users to change attachments mid-session.

While it may not seem like it at first glance, a lot of what netplay does overlaps with "movie" support which is used for TASing. They both require absolute determinism, recording inputs, and playing back inputs. When looking for ways to improve things for TASers, Billiard realized that AdmiralCurtiss's netplay improvements were never ported over to movies! He decided to replace the old way of storing Wii Remote data in DTM files with netplay's intermediary format, bringing many of the improvements over.

We're hoping that this new format makes creating optimized Wii TASes easier and more stable. On the Dolphin side of things, it was also a maintenance win. A bunch of ugly code related to reporting modes and extension data encryption became unnecessary and was removed. As per usual, if you've started a TAS on an older build of Dolphin, you're more-or-less stuck there. Not only is the new DTM format incompatible with the old one, any minor change to Dolphin could break the syncing of a TAS. When creating a new TAS, please ensure that the build of Dolphin you're using supports the feature set you need to accomplish your goals. This goes for whether you're using an official build of Dolphin or a scripting fork. And for the TASers out there doing crazy things in Dolphin, we're always looking forward to seeing what you do next.


This Release's Contributors...

Special thanks to all of the contributors that incremented Dolphin by 341 commits after Release 2412!


2412
  • Amélioration majeure de la synchronisation CPU/GPU réduisant les popups d'erreurs non fatales dans plusieurs jeux (plus de 20 titres concernés).
  • Correction des problèmes d'audio HLE (High-Level Emulation) pour des jeux comme Need for Speed: Nitro et amélioration des filtres DSP-HLE (AX et Zelda microcodes).
  • Correction d'un bug lié aux Bounding Box dans Dolphin avec l'option Auto IR Size, causé par un oubli de marquage de la gestion des shaders.
  • Correction d'un deadlock sous Linux avec les pilotes NVIDIA Vulkan lors du redimensionnement de la fenêtre.
  • Correction des problèmes graphiques dans LIT (School of Darkness) via le cache des normales, révélant un comportement matériel non émulé.
  • Correction du patch de contournement MetaFortress pour Kirby’s Adventure Wii (version européenne), évitant un plantage en écran noir.
  • Ajout d'un manifest pour la construction sous Flatpak, facilitant l'installation multi-distributions Linux.

Dolphin 2412 is here and we've got the details for what's new in the latest release. The biggest thing to note is that there's a lot of polishing to help make playing games a little more pleasant. Several key fixes to Dolphin's HLE audio helps bring a few more games toward audio perfection, and adjustments to Dolphin's CPU <-> GPU syncing reduces the number of harmless, but annoying, popup errors that happen in certain games.

That isn't to say there aren't any titles seeing significant improvements. LIT (School of Darkness) had a unique problem that exposed yet another unemulated hardware behavior. And if you're looking for a deep dive into problematic behavior in a game? We have one of those as well. Eternal Darkness has been a thorn in our side the past couple of months and required some special attention to get working again in time for this release.

For details on all that and more, join us for Release 2412's Notable Changes!

Notable Changes

All of the changes below are available in Release 2412.

2409-17 - DSP-HLE: Fix Low Pass/Biquad Clipping by Tilka

Tilka has been perfecting DSP-HLE over the last few years. A majority of their changes have been minor and fix subtle effects that most users won't notice unless they've recently played the game on console with a high-end sound system. In the last progress report, we covered their implementation of the Zelda microcode's low-pass and biquad filters, but we didn't mention that Tilka also took the time to implement the biquad filter in the AX microcode! Doing so fixed an issue in I SPY: Spooky Mansion where the wind was too loud.

Unfortunately, it also started causing issues in Need for Speed: Nitro's audio.

Thankfully, the issue was found relatively quickly after it was reported. The implementation of the filters didn't take into account that the real AX microcode was using the DSP's set40 (40-bit sign extension) mode, which caused some calculations to be incorrect. After fixing an off-by-one error and adding some clamping, Need for Speed: Nitro's issues were resolved.

2409-71 - Auto IR Size - Fix Bounding Box Corruption by TellowKrinkle

Since the epic battle against Bounding Box that lasted throughout a good chunk of 2021, our foe has remained mostly subdued. But much like Bowser inevitably returns again and again after being defeated by Mario Luigi, a Bounding Box issue has risen from the ashes.

Unlike previous Bounding Box issues, this one wasn't as simple to reproduce. Users have been reporting it for a better part of the year, but upon actually trying to investigate it, the issue would often disappear. We did know that it wasn't specific to any particular bounding box title. It could happen in Disney's Magical Mirror: Starring Mickey Mouse all the way to the most complicated of Bounding Box games, Paper Mario: The Thousand Year Door.

The only constant was that resetting the user's graphics settings would permanently fix the issue. Something was interacting poorly with Bounding Box, but we didn't know what.

On the issue tracker, ZephyrSurfer eventually managed to figure out that the issue centered around Dolphin's Auto IR (Internal Resolution) setting. Auto IR lets Dolphin automatically set the internal resolution based on the size of the window or full-screen monitor (rounded to the closest whole multiple). Users who don't want to mess with their settings can just set this and forget it. The key discovery that had us realize it was the problem was that changing the window size while the game was running was all it took for the affected users to reproduce.

In order to get this fixed, TellowKrinkle jumped in and analyzed the issue. He figured out that Dolphin was forgetting to mark the pixel shader manager as dirty when changing the window size with Auto IR. Essentially, Dolphin is letting the GPU driver know that scaling values used for the bounding box calculation in the pixel shader have changed in RAM, so that the GPU driver will send the data to VRAM again. Because Dolphin wasn't doing that, all bounding box calculations were using the old internal resolution even after the window size changed. Oops.

A simple one line change later and Bounding Box works correctly when using Auto IR.

2409-84 - Linux + NVIDIA + Vulkan - Fix Deadlock by TellowKrinkle

Around March of this year, several of Dolphin's developers on Linux began noticing that they shared a rather inconvenient issue. When using the Vulkan video backend with proprietary Nvidia drivers, attempting to resize the game window while emulation was running would often completely lock up Dolphin's UI.

The deadlock was quickly traced to a call to the vkWaitForFences function in the Vulkan backend's command buffer manager. Seeing this, Pokechu22 joined the conversation and dug deeper to figure out what sequence of events was causing the blockage. Eventually, it was discovered that a call to the vkAcquireNextImageKHR function was failing in a way that was not being handled entirely correctly, leaving a semaphore unsignaled forever.

With a cause found, it was time to bisect recent changes to figure out which one was to blame for it. What happened next was unexpected. Every build that could be tested, going as far back as The Great VideoCommon Unification of 2019, was exhibiting this deadlock. But hang on, wasn't this a relatively recent issue? Something wasn't adding up, and without an obvious mistake to fix, the case went cold.

As JMC47 was reviewing TellowKrinkle's fix for auto IR size, he naturally needed to test resizing the game window. However, as a developer on Linux using the Vulkan backend, he had to pause emulation before doing so in order to prevent the deadlock from occuring. It became such a nuisance that he brought it up in conversation on the official Dolphin Discord server. This time, the issue caught the attention of CasualPokePlayer, who joined the conversation after independently discovering the problem that Pokechu22 found earlier.

Already knee-deep in graphics backend work and aided by CasualPokePlayer's insight, TellowKrinkle decided he should remedy this issue once and for all. Amazingly, he was able to put together a working solution all while being unaffected by the issue himself! Once it was confirmed to work by other developers who were affected by the issue, the fix was in.

The exact source of the Linux + NVIDIA + Vulkan deadlock was still a mystery even though it was already fixed. However, after a bit of digging, we found the smoking gun. In the changelog for Nvidia's Linux x64 (AMD64/EM64T) Display Driver 550.54.14 from February 23, 2024, it says this:


Fixed a bug where vkAcquireNextImageKHR() was not returning VK_ERROR_OUT_OF_DATE_KHR when it should with WSI X11 swapchains.


This error code being returned by the vkAcquireNextImageKHR function was one of the symptoms that was observed while debugging this deadlock! Does that mean that this version of the proprietary Nvidia driver broke Dolphin? We installed an older version of Dolphin and various proprietary Nvidia driver versions onto a fresh copy of Debian Linux to find out.

  • ✅ 550.54.14 from February 23, 2024, the aforementioned version, would deadlock.
  • ❌ 550.40.07 from January 24, 2024, the preceding version and the first beta of the 550 series, would not deadlock.
  • ✅ 565.57.01 from October 22, 2024, the latest beta version, would deadlock.
  • ❌ 535.216.01 from October 22, 2024, the latest long-term support version at the time of writing, would not deadlock.

It's also worth noting that the vkAcquireNextImageKHR function in driver versions without the deadlock would always return VK_SUCCESS, even while aggressively resizing the game window. So, in conclusion, every proprietary Nvidia driver from the 550 series and onward (excluding the first 550 beta version) exhibits this new behavior has to be accounted for by Dolphin.

2409-150 - Cache Normals in Addition to Binormals and Tangents by pokechu22

Nowadays, it's rare that Dolphin sees an actual core emulation change to fix a game, but it still happens occasionally! We recently received an issue report that the WiiWare title LIT (known as School of Darkness in Japan) had severe graphical issues in Dolphin involving the text on its map and menu screens.

When pokechu22 looked into the issue, they found that the devs at WayForward accidentally enabled lighting when rendering the text. The geometry which made up the text also didn't include any normals, which are used when calculating lighting. If a normal vector isn't specified and lighting is enabled, Dolphin uses a default value of (0, 0, 0) in lighting calculations. This is what results in the text showing up as all black. But why doesn't the bug appear on real hardware?

To figure out why, pokechu22 used the fifoplayer to reproduce the problem on an actual Wii and wrote some hardware tests. They found that when lighting is enabled without any corresponding normals, a real Wii GPU instead reuses the last normal it received. In LIT, the last valid normal vector sent to the GPU is (0, 0, 1), which comes from rendering the map's background. Using this value in the lighting calculations allows the text to show up with its intended color.

After normal vector caching was implemented in Dolphin, the text was fixed!

This GPU quirk is actually similar to one that was abused by Factor 5 in the Rogue Squadron series for bump mapping. In those games, Factor 5 sends a single dummy triangle containing common bi-normal and tangent vectors to the GPU, and then sends the actual geometry which relies on the vectors but doesn't include them. As the GPU reuses the bi-normal and tangent vectors from the dummy triangle when rendering the real geometry, the game doesn't need to send them multiple times. This saves memory and improves performance.

2409-161 - Fix Some Common Opcode Decoding Errors by Tilka

One of the highest levels of accuracy in emulation is when an emulator is deemed "cycle accurate." Assuming all things are handled properly, a cycle accurate emulator will, in theory, allow a game to run exactly the same as it would on original console. This would include things like framerate lag, timing issues, race conditions, and everything else you'd expect. Given identical start states, an input recording from a cycle accurate emulator would play back exactly the same on the original console. This is how we have console verified Tool Assisted Speedruns on many older consoles.

Dolphin isn't cycle accurate and doesn't try particularly hard to reach cycle accuracy. Why is that?

Obtaining cycle accuracy is a ton of work and a lot slower than just using estimations. Just emulating a few pieces of cycle accuracy (such as the CPU instruction pipeline, cycle timings, and various cache hits/misses) is arduous and would massively reduce performance. And that's only just part of what we'd need for one component. Cycle accurate GameCube/Wii emulation is a long ways off for the purpose of actually playing games.

Dolphin is a general use emulator that wants to be as accurate and compatible as it reasonably can while maintaining good performance. All throughout Dolphin you'll find tons of tradeoffs between accuracy, performance, and compatibility. Many of the most accurate options in Dolphin are disabled by default to keep performance at an acceptable level.

For something like cycle timings, Dolphin just tries to get close enough. On the GameCube/Wii CPU, how many cycles an instruction can take varies greatly. Sometimes the code might hit the L1/L2 cache, sometimes it won't. Sometimes the instructions around an instruction can reduce the number of cycles it takes to execute that instruction! And that's just what we as blog writers can understand about it. The actual details are frightening, but what you need to know is that Dolphin just fudges the numbers to get reasonably close and most games are fine with this.

The amusing thing about Dolphin's estimations is that it will sometimes be a little faster than console, and sometimes a little slower. A good example of a scenario where Dolphin is slower is the video player in Tales of Symphonia. The video decoding logic is super optimized for the GameCube's CPU, and Dolphin's estimations on how many cycles can be used per frame is off by enough to cause stuttering during playback. Note that Tales of Symphonia is only being used as an example of the problems that can happen with a non-cycle accurate emulator, and this particular problem is not being addressed at this time.

For the GameCube/Wii, there are also other complications, with one of them being CPU <-> GPU communication. How fast each runs and how often they are allowed communicate can greatly affect both compatibility and performance. Too little communication and interrupts can get missed or fired at the wrong time, and the state that each component is in might not match what they are expecting!

Warning: Dual Core Rant

Dual core is a performance hack that allows Dolphin to separate the CPU and GPU emulation into their own threads and let them run independently of one another (with occasional synchronization points). Because they are running at the same time and synchronization has to be kept at a minimum in order to gain performance, it is entirely possible that performance hiccups can cause one thread to fall too far behind the other. And because the actual state of the component can be affected, these are slowdowns that the emulated software can actually feel! Depending on how sensitive a game is to these problems, they may be perfectly stable in dual core, or entirely unusable to the point where it has to be force disabled.

There are also interesting cases where some games are perfectly fine as long as the host computer is fast enough. Fire Emblem: Path of Radiance is perfectly stable when using dual core on most devices, but becomes unstable on the extremely low-end hardware that needs dual core the most. Developers have tried to fix dual core in the past, however all of the attempts have either greatly reduced dual core's performance advantage while still not matching single core's compatibility, or further reduced its compatibility in exchange for determinism. Dual Core as it is has proven hard to replace despite the downsides.

Single core does not have these problems at the expense of running both the CPU and GPU threads on the same core. Performance hiccups cannot leak through to the emulated software and stability is essentially guaranteed, or at least guaranteed to be consistent in cases where something is broken. The following explanation describes single core's deterministic way of syncing the CPU and GPU works.

Dolphin switches between emulating the CPU and emulating the GPU in set intervals. As a balance between accuracy and performance, Dolphin doesn't swap every emulated cycle. Instead, Dolphin emulates the CPU and GPU in time slices. Essentially, Dolphin will let GPU commands accumulate in memory for 1000 cycles, and then make the GPU catch up. However, when Dolphin is emulating the GPU, there is a possibility that the data at the end of that command stream doesn't form a complete command yet. If that happens, and the game reconfigures the location in memory from where the GPU reads the command stream, then that incomplete command can be combined with a new unrelated command!

When this happens, there's a chance that this new command could become an unknown opcode that causes an annoying popup for users. In order to fix this, Tilka changed it so Dolphin now forcibly processes all pending GPU commands if the game reconfigures the location in memory that it is reading from.

Doing this fixes unknown opcode popups in over 20 games!

Note that almost all of these unknown opcodes were non-fatal and mostly just an annoyance for users. Still, the fact they were popping up showed that emulation was problematic to some degree in these titles. Overall, we expected this change to boost our accuracy without introducing any regressions. As an added bonus, the changes to the command processing allows Harvest Moon: Tree of Tranquility to finally boot without green flashes in single core mode.

2409-268 - GamePatch: Fix Opcode Decoding Regression in Eternal Darkness by Tilka

The previous change tightened up Dolphin's CPU/GPU synchronization to prevent unknown opcodes. There's no way that could cause a regression, right?

...

Whelp.

One of the potential issues with making timings more accurate is that sometimes you break things that shouldn't have been working, but were working for the wrong reasons. In this case, Eternal Darkness started hanging on boot.

The previous opcode decoding fixes were an improvement to overall accuracy, so Tilka didn't want to revert them because of one game. That meant diving into Eternal Darkness in a way no one else ever had.

As with many of the remaining broken games, Dolphin was only half of the problem. The other half was actually an issue in the game itself. Make no mistake - with the opcode decoding fixes, Dolphin was now emulating the game closer to how it would run on console. However, by being closer, it was now triggering a race condition that would never happen on real hardware.

In order to explain this issue, we have to get a bit messy with an in-depth explanation. If you're not interested in the internal behavior of this game's FIFO, feel free to skip the next two paragraphs.

In essence, Eternal Darkness has a race condition within its graphics rendering code. It uses the GXSetDrawDone function to add a draw done command to the command stream, which makes the GPU raise an interrupt when executed. Some time after adding the command, it then reconfigures the GPU command stream. As previously mentioned, Dolphin wouldn't properly execute commands at the end of the stream. This meant that the draw done command was never executed and the interrupt was never raised. Because of that, the game didn't hang in Dolphin! Wait, what?

The difference between Dolphin and real hardware is that an actual GameCube GPU would always raise the draw done interrupt before Eternal Darkness has a chance to change the command stream address. Without the opcode decoding fixes, the draw done interrupt would never be raised due to its command being ignored, avoiding the race condition altogether. However, with the opcode decoding fixes, we now get interesting behavior that's closer to console but still not quite correct. This time, all the GPU commands are processed as per normal and the draw done command is executed. However, because our cycle timings are inaccurate, Dolphin has a hack that delays raising the draw done interrupt by a minimum of 500 cycles. This hack gives games some time to finish any necessary setup that may not be finished if the interrupt is raised immediately. Eternal Darkness is able to change the GPU command stream address during the delay. When the interrupt is finally raised 500+ cycles later, the game promptly hangs because the code that handles the interrupt doesn't expect a different command stream address at that point in time.

This hang is technically a game bug, albeit one that never manifests on real hardware. We could change the 500 cycle delay until we found a number that won the race, but we ultimately decided not to make an arbitrary decision like that based on the results of one game. Instead, Tilka made a patch for Eternal Darkness to replace the problematic GXSetDrawDone function with the safer GXDrawDone, which forces the game to wait for the interrupt to be raised before it can proceed. This is an incredibly efficient fix, as it comes with no performance cost, doesn't require any change to Dolphin itself, and means we won't break any other games while trying to find a delay that works for Eternal Darkness. Correct emulation would require incredibly small GPU slices which would drag down performance of the emulator in general.

To prevent any confusion surrounding this regression, the patch has automatically been enabled in the latest release for all regional variants of the game. If you wish to disable the patch or view what patches are available for other games, simply access the game properties page and go to the "Patches" tab.

2409-181 - DSP-HLE: Fix Wii Remote Audio in Multiple Games by Tilka

The Wii Remote is a rather complex controller to emulate. It has attachments, a weird layout, motion controls, a small amount of savedata, infrared, and even a speaker! The speaker part of the Wii Remote is one of its more forgotten features simply because most games used it for entirely optional sound flourishes (the Wii allows the player to turn the speaker off), and the speaker itself was rather puny. When using an emulated Wii Remote, Dolphin pumps the Wii Remote speaker data to the standard audio output device. However, when using Real Wii Remotes or Bluetooth Passthrough, Wii Remote audio can work in Dolphin just as it does on console. In fact, with Bluetooth Passthrough and a strong enough adapter, you can enjoy the same mediocre sound quality as console!

The fact this feature has been so maligned is why very few people noticed or cared that Wii Remote audio was very broken in some games. For a revision of the AX microcode used early in the Wii's lifecycle, there were some serious bugs in our DSP-HLE implementation:

  • The size difference between the high-pass and biquad filter was not accounted for, causing adjacent memory to become corrupted.
  • The Wiimote sample buffer pointers were advanced by 32 samples per millisecond instead of 6 samples. Any audio corruption caused by this was usually hidden by the first bug.
  • PB updates on Wii were being byte-swapped twice. However, no games that use this feature were found.

While we don't know if the third bug affected any games, the first two affect a lot of games released between 2006 and 2007. Tilka gave us an example list of games that they noted are fixed by their changes:

Fun fact - WarioWare: Smooth Moves was the only one of these titles with an active issue report saying that Wii Remote audio was broken.

Also, games that use the Zelda microcode were not affected by these bugs. For example, The Legend of Zelda: Twilight Princess was not affected despite being released in 2006.

2409-260 - Add manifest for building as a Flatpak by cpba

Unlike Windows and macOS, there isn't a single OS that you can point to and call "Linux". Instead, when a user wants to run Linux on their system, they are able to choose between many different "flavours" of Linux known as distributions. Each distribution bundles the Linux kernel together with a set of packages containing various drivers, software, libraries, frameworks, and more. There are many benefits to this system. For example, a user can choose a distribution that is tailored to their own needs. Newbies might gravitate towards beginner-friendly distributions like Ubuntu, while more advanced users may prefer distributions that offer lots of customizability, like Arch Linux or NixOS.

However, this system also comes with several disadvantages. The biggest issue relevant to us at Dolphin is that each distribution tends to have its own vision for how software should be packaged and installed on the system. They also update their packages independently of each other, meaning that one distribution could have the most up to date version of a specific framework, while another distribution is stuck on an out of date version. Unfortunately for app developers, all these factors make it difficult to create a single build of an app that can run across every possible Linux distribution. As a result, creating desktop apps on Linux has historically been a bit of a mess. While Dolphin has offered official builds for Ubuntu in the past, those builds wouldn't install on other non-Ubuntu distributions, and would only be guaranteed to work correctly on the specific Ubuntu version that it was built for. After we stopped offering official Ubuntu builds, our policy has been to just let each distribution be responsible for producing their own Dolphin builds. If a Linux user wanted to install Dolphin, they would either need to compile it themselves or use the package from their distribution.

In an attempt to solve the problem, several competing solutions for packaging Linux apps with cross-distribution compatibility have emerged over the past decade. One of these solutions is known as Flatpak. Flatpak allows a developer to build their app against a common base "runtime", which contains all of the libraries and frameworks that an app may need. When an app is installed, its corresponding runtime is also downloaded and installed along with it. Since all of the dependencies are found in the runtime or bundled with the app itself, a Flatpak build of an app doesn't rely on the packages provided by the installed distribution! The distribution just has to support the Flatpak system itself.

But why are we choosing to make Flatpak builds over all of the other competing solutions? The answer lies in the Steam Deck. Valve has adopted Flatpak as the official way to install non-Steam apps on SteamOS. When a user wants to install something that isn't available on the Steam Store, all they have to do is switch to Desktop Mode and open the Discover Software Center. There, they can find a plethora of software available for download in the Flatpak format, including many emulators!

Apps in Flatpak format are most commonly distributed by repositories, and the largest Flatpak repository is known as Flathub. The Steam Deck has Flathub installed by default, which is what allows users to instantly get access to a large library of Flatpak software. Surprisingly, Dolphin is actually one of the oldest apps that was added to Flathub. Ever since Flathub launched in 2017, a group of dedicated individuals has been maintaining an unofficial Flatpak version of Dolphin! When we heard about this, it only made sense that we ask them for assistance in making our own Flatpak builds.

With the help of cpba and ColinKinloch, all of the necessary files to create Flatpak builds have now been merged into the upstream Dolphin repository. OatmealDome completed the necessary infrastructure work to allow our Buildbot CI to create Flatpak builds.

You can now add one of the following repositories to install our Flatpak builds:

Alternatively, you can also download single-file bundles for specific builds on our downloads page.

While we're launching our Flatpak builds with this report, we should note that there's a slight catch. The builds found on Flathub are still unofficial due to some pending changes to our infrastructure and various important people being away on vacation. (Yes, eagle-eyed readers, this is also why Dolphin isn't verified on Flathub yet.) We hope to have this fixed soon!

And to all of our AppImage fans: we're aware of the demand. We want to work on getting Flatpak up and running first.

2409-303 - Sync GPU just before PI_FIFO_RESET by Tilka

Just when we thought we were done, we were pulled back in. After all of the work Tilka did to reduce the number of unknown opcode errors that games would spew, we started seeing the worrying trend of new unknown opcode errors popping up across more games. Fortunately, none of these were fatal and almost every one centered around closing games.

New Super Mario Bros. Wii was the first culprit reported, so Tilka conducted an investigation to figure out what was going on.

If you've been reading the rest of the progress report, then you'll remember that in single core, Dolphin lets GPU commands accumulate in memory for 1000 cycles. There's something we didn't mention earlier, though: every now and then we also copy these commands from the game's memory into a Dolphin-internal buffer, partially to hide from the game that we're letting many commands accumulate. When processing these commands, we look at the Dolphin buffer first, and then whatever is in the game's memory.

If the console is asked to shut down, New Super Mario Bros. Wii calls GXAbortFrame to stop rendering the current frame and reset the GPU. When this happens, Dolphin empties its internal buffer but doesn't empty the game's memory as well. The last bytes seen by the opcode decoder could be a partial command in the internal buffer followed by bytes from commands in memory that were not cleared! In order to prevent command buffer execution from resuming in the middle of a command, Dolphin now allows the GPU to catch up to the CPU's reality and then resets the internal buffer. That means if there are only a few commands left to process, they will go through fine and there will be no problems.

Because the target of this fix was New Super Mario Bros. Wii's regression, we weren't expecting to fix any previously broken games. To our surprise, it turns out this flaw was causing problems across several games, even under the old GPU syncing behavior!

If you're keeping count, this means that Tilka has improved compatibility across at least thirty-four games for this release!

Unfortunately, this solution is a stop gap. The core issue of the internal buffers being cleared without clearing the game's buffer still exists. If a lot of GPU commands have been accumulated, problems can still occur. This is what causes SpongeBob SquarePants featuring Nicktoons: Globs of Doom to be broken in the latest release version. Tilka also conducted additional hardware testing and found some additional behavior that needs to be implemented. We'll hopefully have all these improvements in a future release.

2409-313 - Fix Kirby's Adventure Wii MetaFortress Bypass Patch by vaguerant

The name MetaFortress should ring a bell to long-time readers. For the unfamiliar, MetaFortress was an anti-piracy system used by a handful of games on the Wii. We previously covered MetaFortress's presence in the all-time classic game The Smurfs: Dance Party back in 2017:

While modern versions of Dolphin are able to handle MetaFortress's anti-piracy checks, we still include patches for bypassing MetaFortress entirely in some games. While MetaFortress's primary purpose is to check for piracy, it also does some trickery to detect if the game itself has been modified, just in case any of its anti-piracy checks were patched out. This can cause problems when making cheats and mods for MetaFortress-protected titles, as modifying the game's code could trip MetaFortress.

One of the games that we ship a MetaFortress bypass patch for is Kirby's Return to Dream Land (also known as Kirby's Adventure Wii in Europe). Unfortunately, when the patch was ported from the North American version to the European version, some mistakes were made in the porting process. If a user enabled the MetaFortress bypass patch and tried starting the game, it would hang on a black screen due to some patch addresses being incorrect. A lone user did report on the forums that the patch was broken earlier this year, but their post unfortunately fell through the cracks.

vaguerant independently discovered that the European version of the MetaFortress bypass patch was broken and took it upon themselves to fix it.

With this change, we hope that the scourge of MetaFortress has now been defeated once and for all.


Casual readers beware!

The following two sections cover changes to Dolphin's debugging interface, a normally hidden suite of tools used for deep-dives into the workings of emulated software. If this does not interest you, then that concludes today's Progress Report! Feel free to skip ahead for this release's contributors and a special message regarding the Stop Killing Games campaign.

...

Are you still here? Well then, let's get technical!

5.0-21724 - Branch Watch Tool: Add Set Breakpoints Submenu and 2409-15 - Branch Watch Tool: Refactors, Fixes, and Features by mitaclaw

Dolphin 5.0? What is a feature from that era doing in this progress report? Well, you may remember the Branch Watch Tool from its showing in the progress report for February, March, and April. Determined to make it feature-complete, mitaclaw continued building upon this reverse-engineering tool in the months following its release. The goal was to finish both of these improvements in time for the September progress report, but unfortunately the second pull request just barely missed the deadline. Thus, we're covering them both now!

As with the existing features of the Branch Watch Tool, a tutorial on the operation of these new features can be found in the Branch Watch Tool's menu bar, under Tool > Help.

The first new addition to the Branch Watch Tool is the ability to set instruction breakpoints en masse from a row selection. This is potentially useful when a number of branch candidates are found, but the order in which they are hit is in question. Additionally, the context menu shows if the locations selected already have breakpoints set; the large circle icon indicates every location already does, while the small square icon indicates only some locations do.

The second new addition to the Branch Watch Tool is more ways to inspect conditional branch candidates. Before, all one could do was replace a conditional branch with a no-operation instruction (nop). This is equivalent to forcing a conditional branch to always take its false path, but now one can also force a conditional branch to always take its true path by making it unconditional. But that's not all! For any conditional branch, one can now invert the branch's condition (turning beq into bne, ble into bgt, and so on) or invert the branch's decrement check (turning bdnz into bdz, and vice versa).

We hope these new features are helpful to anyone who uses the Branch Watch Tool for research and development.

2409-216 - DolphinQt: JIT Widget Refresh by mitaclaw

Among the likes of the code widget or the memory widget, there is the lesser-known JIT widget. Made to assist Dolphin's developers in understanding the output of its just-in-time recompiler, the JIT widget has an incredibly niche userbase. After all, only a fraction of Dolphin's developers are interested in working on the JITs! Thus, it should not be surprising that the JIT widget has not evolved much since its conception.

Apart from surviving the migration from DolphinWX to DolphinQt, the JIT widget's design and features have remained in 2008*. In its current form, the JIT widget does not display the far-code cache—a memory region where lesser-used recompiled code is sent to—as it predates the concept by nearly six years! What's more, using the JIT widget with the Cached Interpreter results in nonsense, as it predates that CPU emulation engine by nearly seven years! The large table consuming a great deal of space in the JIT widget is, and always has been, a placeholder!

It would take a developer seriously interested in Dolphin's JITs and in writing Qt widgets for the JIT widget to get the update it deserves. Luckily, that developer has arrived. While mitaclaw was working on his software JIT profiling restoration, which was featured in a previous progress report, he was simultaneously overhauling the JIT widget to make this profiling data easier to view while also fleshing out this skeleton of a widget. So, what does the JIT widget look like now?

Packed with new features, it's a huge improvement! For the first time, a list of every cached block of recompiled code is displayed by the JIT widget. It is also now possible to erase selected blocks of recompiled code from the JIT's cache, forcing them to be recompiled again for debugging purposes. The "PPC vs Host" action available from the code widget's context menu, which in the past was the only route to the functionality of the JIT widget, has been generalized as a filter option in the JIT widget (the "Recompiles Physical Address" input field). Finally, the missing support for the far-code cache and the Cached Interpreter has been addressed. Our hope is that, for the few people this drastic overhaul matters to, it can greatly benefit their work.


This Release's Contributors...

Special thanks to all of the contributors that incremented Dolphin by 323 commits after Release 2409!


What's Up with the Blue Banner?

You might have noticed that we've added a banner for the Stop Killing Games movement at the top of this website. If you're curious why, we'd like to take the opportunity to explain in a format less cramped than a small banner.

2024 has been a year of bad news for the emulation scene. Nintendo not only forced Switch emulator Yuzu and Switch emulator Ryujinx to shut down, but also hit 3DS emulator Citra as collateral damage. The US Copyright Office refused to let researchers remotely access emulated versions of out-of-print copy-protected video games even though it's already allowed for other forms of media. And Sega will delist SEGA Mega Drive & Genesis Classics from Steam on December 6, one of the few ways to legally get direct downloads of ROM files.

All of this goes to show that corporations in general don't really care if people can still play old games. Sure, the big classics like Super Mario Bros. will probably keep getting rereleases in perpetuity, but a lack of financial incentive for rereleasing less popular games has led an estimated 87 percent of older games to go out of print. The community is eager to help preserve video games, but they're held back by the current state of copyright law, and if you ask the Entertainment Software Association (the video game industry's lobbying organization in the United States), they'd very much like to keep the law as it is.

But still - at least for older consoles - the emulation scene is alive and kicking. For newer consoles, even if emulators aren't being developed right now, that time can come in the future. And even though old games can be hard to legally get hold of for the average person, the history of the console space so far has shown that few video games are at risk of being completely lost to time.

With one big exception: online-only games.

In the year the GameCube launched, console games that let you connect to the internet were a rarity, and popular PC games like Counter-Strike expected you to host your own server if you wanted to play online. Today, fueled by the rise of live service games, many multiplayer games can only be played by going online and connecting to the publisher's servers. There are now even single-player games that require a connection to a server! The mobile market is even worse, as games that can be played offline are the exception to the rule there. This is inconvenient if you don't have a reliable internet connection or if there are server outages, but the insidious part is what happens once the publisher loses interest in the game. Not only do they stop selling the game, but because they also shut down the servers, every copy of the game becomes unplayable in one fell swoop. Emulators aren't of much help when a game doesn't even work on the original hardware!

This is what the Stop Killing Games movement wants to stop. Their position is that when you buy a game as a one-time purchase, the company behind the game shouldn't be allowed to later render it unplayable. They're presenting the problem not only as a matter of game preservation but a matter of consumer rights, and through that angle, they're trying to get through to lawmakers and consumer protection agencies. Depending on the laws of your country, when you buy a product, it usually comes with some kind of warranty where if the product breaks within a certain timespan due to a defect that's the manufacturer's fault, they have to repair the product or refund you. But what about when you buy a live service game? The game's servers might shut down at any time, and you usually won't know the date until the shutdown is already imminent. So far, games companies haven't gotten any real pushback from consumer protection agencies for this.

In more concrete terms, the movement is trying to create change in two ways right now, both of which are detailed on the Stop Killing Games website. The first is asking consumers who bought the recently shut down Ubisoft game The Crew to complain to their consumer protection agency. The second is petitioning legislators in various countries. In particular, their European Citizens' Initiative is currently ongoing, and the petition of theirs is the most likely to end up making a change. But it has a tough goal to meet: one million signatures.

The outcome of Stop Killing Games won't directly affect Dolphin, since GameCube and Wii games aren't being made anymore. But as a project that would like to see video games both from the past and the future preserved, we recommend that you sign their European Citizens' Initiative if you can! Note that you must be an EU citizen to sign.

[…]

2409
  • Intégration de RetroAchievements : Support officiel ajouté pour les réalisations rétro, avec une première version stable mais limitée (fonctionnalités et options en cours de finalisation).
  • Amélioration des infobulles : Extension progressive aux onglets Interface et Général du menu de configuration, avec des corrections d’affichage.
  • Amélioration du Cached Interpreter 2.0 : Optimisations majeures (commandes de taille variable) offrant une accélération de 10 à 25 % par rapport à la version précédente.
  • Intégration de l’updater dans le bundle macOS : Suppression du bundle séparé pour l’updater, simplifiant l’installation et l’uniformisant avec les standards macOS.
  • Correction des sons dans Pikmin et Pikmin 2 : Résolution de problèmes d’audio mineurs (pitch incorrect, sons manquants) liés à l’émulation HLE du microcode Zelda.
  • Forçage de l’alignement des listes de rendu vidéo : Correction d’un bug visuel majeur dans Wallace & Gromit in Project Zoo (explosion des ombres) via un alignement mémoire respecté.

After an exciting round of feature articles, it's Progress Report time once again! However, a lot has changed. Dolphin has finally left the 5.0 era behind, and has entered the Release Era. Not only did we get our first release in eight years, but we also established a commitment to continuous releases going forward.

For the Reports, things will be more or less the same, but with a few changes.

Progress Reports are now also release changelogs. We'll be going over the notable additions and changes between each release in every Progress Report going forward, rather than within a range of dates. As such, the name of the Reports will reflect the release accompanying it - if you want the new features, just update to the version at the top or higher and you'll have them! (However, since 2407 had a release article without a changelog, this Report will be covering the changes in both Release 2407 and Release 2409.)

That also means that the next release is happening right now! Accompanying this report is Dolphin 2409. It is now rolling out via our updater, and is available for download here on our website.

But there was also another feature article since our last Report. Dolphin now has RetroAchievements support!

For those waiting for it to show up in a release build, the wait is now over. Throughout the past couple of months, we've ironed out one major issue alongside many smaller issues with RetroAchievements. The first iteration of RetroAchievements in a release build is stable, but not all that flashy. The groundwork is there for future improvements, but many features and options are yet to be finished. As well, Android support is still deadlocked with a few issues. Please pardon our progress!

We have a bunch of cool statistics from the RetroAchievements team regarding the launch, however, we need to get on with the Report! So just click this handy link to be taken to the bottom of the Report if you'd like to read more!

But before we get to the Notable Changes, we have a couple of things to cover.

Google Play Update Delay

Last month, we got a surprise email from Google Play saying that Dolphin doesn't comply with their policies because it "installs, but doesn't load". We have gotten emails like this before regarding Android TV, presumably because someone at Google tried to install Dolphin on one out of the vast majority of Android TV devices that don't meet Dolphin's hardware requirements, but this is the first time we've gotten a rejection for Android as a whole. Seeing as Dolphin generally does load correctly on devices that are able to install it, we're not quite sure what happened here.

What does this mean for Dolphin? Dolphin is still available on Google Play, but the next update we release has to be manually checked by Google before it becomes available to users. Because of this, it will take longer than normal for the 2409 release to show up on Google Play, but any updates after that should be smooth sailing again. If you're impatient and want the latest version of Dolphin right now, it's available on this website as always!

Visual Studio Twenty-Twenty-Woes

During the rollout of the latest release, a lot of people updated Dolphin for the first time in a while! But for some of our Windows users, when they fired up Dolphin 2407 for the first time they were met with a silent crash. They reached out to us, and the support vanguards on our Discord quickly found a solution - reinstalling the 64-bit Microsoft Visual C++ redistributable for Visual Studio 2022 got Dolphin working for them once again.

We're not entirely sure why exactly this happened. But we have a theory.

The Visual C++ 2022 Redistributable is a runtime library that contains everything needed to run programs compiled with Microsoft Visual Studio 2022. However, Visual Studio 2022 is not static: there are many subversions, and it gets regular updates. These updates should be backwards compatible with any other version of Visual Studio 2022. It would be madness to make a change to Visual Studio 2022 that breaks compatibility with Visual Studio 2022's own runtime libraries. However, Microsoft did exactly that.

In Visual Studio 2022 v17.10.0, Microsoft made a non-backwards compatible change to std::mutex::lock. This was reported to Microsoft, however, the issue report was marked as "Closed - Not a Bug". Apparently this was intended!

This puts us, as an application that uses Visual Studio, into a weird place. We set up an automated process to update our Visual Studio builder to new subversions as they come out, confident that it will never break anything. It's just subversions. So we have told our Windows users that all they need to run Dolphin is the Visual C++ 2022 Redistributable, confident that it would work. However, Visual Studio automatically utilized the new version of std::mutex::lock when compiling our Windows builds. If a user is running an older version of the Visual C++ 2022 Redistributable before that new version of std::mutex::lock was implemented, they may download and run our program and see a silent crash. And of course, if we ask them if they are using the Visual C++ 2022 runtime, they'll say yes, because they have it installed.

According to Microsoft, this is our problem. Their expectation is for applications to be distributed with installers that will include the redistributable and install it with the app if required. However, they hand out the redistributable to users precisely for applications like us that ship without an installer. It's not like what we're doing is novel. And perhaps Microsoft should have made it fail in a way that communicates to the user that they need to update the redistributable, instead of just crashing silently? Or perhaps just include the Visual C++ 2022 runtime libraries in Windows Update so every user is guaranteed to have the latest version and applications don't even need to worry about it?

...Anyway, unfortunately, we don't have a great solution for this issue. We could disable our automated update process for our Visual Studio builder, but there are security benefits to keeping it, so this is something we'd rather not do. For now, all we can tell our Windows users is that if you run a new version of Dolphin and encounter a crash, redownload and reinstall Visual C++ 2022 Redistributable. As always, we have a link to the redistributable on our download page.

On a happier note, it's time for our Notable Changes!

Notable Changes

All of the changes below are available in Release 2409.

5.0-21462 - Windows: Remove rounded corners on emulation render window by Filoppi

When Windows 11 released in late 2021, it brought the first major visual overhaul to Windows since Windows Phone from 2010. Gone were the sharp edges, bold colours, and dense squares of the Live Tile era, and in their place were soft tones, spacious design, and friendly round edges.

However, as part of this new aesthetic, Windows 11 applies round edges everywhere, even to game windows! Pixels that your computer spent your hard-earned money rendering are now hidden in windowed mode by default.


This was unacceptable!

Recognizing this travesty, Filoppi came to the rescue and saved our pixels. By configuring DWM_WINDOW_CORNER_PREFERENCE in our Windows builds, all pixels that Dolphin renders (on Windows 11 and in windowed mode) are now once again free to be seen by our illustrious eyeballs.

If only such relief could be bestowed upon our macOS users as well...

Balloon Tooltip Quality of Life Updates - 5.0-21123, 5.0-21635, and 2407-130 by Dentomologist

A few years ago we introduced our custom balloon tooltips. Rather than have a large description area permanently taking up space or a terrible native tooltip defined by the OS, we created our own custom tooltips that gave us the best of both worlds.

They have been serving us well since. However, after they were rolled out for the graphics area of our config, they haven't really been touched since then. Now that's changing, and our Balloon Tooltips are finally getting some much needed love and a wider rollout!

First is 5.0-21123, which reworked how they are drawn to resolve many longstanding quibbles with the tooltips.

Next is 5.0-21635, which added tooltips to the Interface tab of Config.

And finally 2407-130, which rolls out our tooltips to the General tab of Config!

Dentomologist is still chipping away at the tooltips, so expect them to continue to improve and be applied to more windows over time!

2407-103 - Cached Interpreter 2.0 by mitaclaw

After the merge of "Cached Interpreter 2.0", we've seen some misinformation floating around emulation communities regarding what the cached interpreter is and what this change has brought. So for the Progress Report, we felt it was prudent to take a deep dive, and properly explain a bunch of concepts we've been putting off for years now. Strap in everyone, we're going deep!


The primary task of CPU emulation is translation: we take code that was originally designed for a specific type of CPU and translate it into something that a different type of CPU can understand. This is not free. Even ignoring the work involved in the act of translating in and of itself (more on that later), having to account for hardware differences means that the resulting translated code will usually be many times larger and more complex than the original code was on the original hardware. As such, there are many different approaches to CPU emulation.

Interpretation is the most basic and literal CPU translation method. An interpreter decodes each individual instruction from the emulated architecture (guest), then translates that into the instructions (plural) that allow the host to perform the same work. And yes, it translates one instruction at a time. This is extremely accurate (able to preserve all nuance) and very straightforward, making interpreters the perfect entry point for most emulators and a fallback for other translation methods. However, interpreters are so straightforward that they have barely any wiggle-room for optimization. Interpreters will always be costly.

Recompilation gives us that wiggle-room. By translating the code in blocks rather than per instruction, recompilers can peek into what the code is doing and reimplement troublesome code in ways that are faster for the host hardware. However, reimplementation often causes inaccuracy, and correcting for that without sacrificing speed leads to ballooning complexity. Making a recompiler both fast and accurate can easily take thousands of hours from passionate engineers.

There are many different types of recompilers, but we're just going to focus on the primary recompiler type that Dolphin uses: JITs.

Just-In-Time Recompilation (JIT) recompiles small blocks of code while the program is running. A JIT will fetch blocks of code from the program, analyze and reimplement as much as it can, then pass the JITed code to the host system to be processed and ready just before the program needs to consume those blocks.

"Just-In-Time" is literal.

The live analysis that JITs perform is overhead. While modern JITs will mitigate this somewhat by caching JITed code blocks, the analysis is still work, which some other recompilation techniques avoid. However, JITs have many benefits. By recompiling blocks of code while the program is running, JITs are able to adapt to whatever the program is doing and don't need to rely on assumptions. This allows for maximum optimization potential, even in self-modifying programs!


With that, we've covered the two most common CPU emulation techniques. Generally, there is nothing inbetween these two options. Emulator authors make an interpreter first, and use it as a reference for building a recompiler. And that's it. Recompilers are so much faster than interpreters that making an interpreter faster is largely irrelevant.

There are several reasons for this. For example, interpreters can't place guest registers into the host registers, so any time the emulated CPU wants to read its registers, an interpreter has to fetch the registers' contents from host system memory, which is two orders of magnitude slower. Also, for Dolphin, our interpreter has the MMU enabled at all times, and the constant memory manipulation is even slower in the interpreter than it is for a JIT!

However, what slows down interpreters the most is branching.

In computer science, a branch is the act of diverging from the current flow of instructions. If a CPU is executing instructions sequentially, it can process them very very fast. But if an unpredictable branch occurs, the CPU will need to stop everything, flush all its pipelines, and spend the next 10-20 cycles building them back up again before it can resume processing. Branching is one of the most expensive low level operations in computing! As such, modern CPUs do everything they possibly can to improve branch performance, with branch prediction and speculative branch execution trying to get ahead of any branches and keep the pipelines flowing. These features are so important that improved branch prediction is one of the primary reasons why a 2024 CPU core at 4ghz is faster than a 2004 CPU core at 4ghz. It's that significant.

By operating on each instruction from the guest, one at a time, an interpreter will need to branch very frequently - several times for even a single instruction. And these branches are usually unpredictable, directly hurting what makes modern CPUs fast. With all factors combined and in a worst case scenario, a single instruction from the guest could take over a hundred cycles for our interpreter to decode! This occurs millions of times per second, thrashing our host CPU.

Interpreters are simple, straightforward, and readable, but they are fundamentally inefficient. A recompiler will always be faster, so there is little incentive to make an interpreter faster. Except, perhaps, for fun.

Nine years ago, degasus had a fun idea. How fast could an interpreter be made (while still being an interpreter) if we applied a bunch of ideas from JITs? The result of this little experiment was the Cached Interpreter.

With a JIT, code is collected into blocks and recompiled into host-specific machine code all together. This allows the JIT to reimplement some of the code to be faster for the host, but also allows the JIT to cache these JITed code blocks, so that any time code is reused, the JIT will just jump to the cache and skip the analysis for a speedup.

Dolphin's Cached Interpreter borrows this idea. Code is collected into blocks exactly like a JIT. However, rather than recompile it into JITed machine code, which is specific to the host and may be reimplemented, the code block is instead translated into an intermediate representation - code which stores the decoded instructions as "commands" that can be compiled into machine code that the host CPU can run.

This benefits our Cached Interpreter in many ways. Just like a JIT, the code blocks can be cached. Any time code reappears, the Cached Interpreter can just reuse the already decoded version in the cache, skipping the decode and all its associated branching. The act of interpreting in blocks rather than per instruction also reduces branching outright, down to roughly one branch per command, and makes branches more predictable too. This also reduces the cost of fetching instructions through the MMU, and brings several other benefits from the JIT, such as Idle Skipping. *

All combined, the Cached Interpreter was over twice as fast as our interpreter when it released! However, it was still an order of magnitude slower than our JITs. For most users, it was more or less irrelevant. However, the Cached Interpreter has found its niches. As it is still an interpreter, it retains the impeccable accuracy that interpreters provide, as well as the ability to run on any architecture - it's our interpreter, but faster. As such, it has become a useful tool for testing and JIT development. Plus, in situations where JIT recompilers are unavailable, the substantial speedup versus the standard interpreter is always welcome.

But what if the Cached Interpreter could be taken further?

Fast forward to 2024, and mitaclaw and Sam-Belliveau got into a competition to see just how optimized the Cached Interpreter could be. Eventually they merged their efforts, in what mitaclaw dubbed Cached Interpreter 2.0.

This change brought many optimizations to the Cached Interpreter, but the biggest change by far was variable sized commands. Previously, the commands inside the Cached Interpreter's intermediate representation had a fixed size, but mitaclaw and Sam-Belliveau realized that by allowing the commands to be any size, the most common bookkeeping commands could be bundled together into a single command. This significantly reduces the number of bookkeeping commands in total, further reducing the amount of branching in our Cached Interpreter.

Just how big of an impact could these optimizations have? Let's get to the numbers!


With a 10 to 25% uplift, the Cached Interpreter is better than ever! It's also now 3 to 4 times faster than the interpreter, and in games with lots of idle loops to skip, such as Cave Story, Cached Interpreter leaves our interpreter in the dust. However, our JITs are still MUCH faster in every scenario, so its role in Dolphin is unchanged. The Cached Interpreter still cannot serve as a JIT alternative. And according to mitaclaw, further optimizations had a negligible impact on its performance. Dolphin's Cached Interpreter will likely not see another significant performance bump again.

Nevertheless, for the niches where the Cached Interpreter thrives, it is now faster than it has ever been.

2407-165 - macOS: Embed the Updater into DolphinQt's app bundle by OatmealDome

One of the best things about macOS is application bundles.

On Windows, programs are largely intended to bring their own dependencies. However, each program will need many different files in many different and bizarre places, so much so that it is standard to ship a dedicated program whose only purpose is to place or remove all of the disparate files an application needs to function. If something goes wrong with this process, good luck.

Linux, on the other hand, works more like code - dependencies are separate from the program and should be linked, not duplicated. However, dependencies will need to be installed along with the application, so Linux has package managers to install applications and any dependencies that are needed. While this is certainly better than the backwards-compatibility mess that is Windows, installing a single application in Linux still results in installing lots of things in lots of places.

macOS is different. It has something called application bundles. All apps on macOS (with the exception of command-line tools and scripts) are distributed in the bundle format. Application bundles are really just regular folders that follow a very specific structure with their contents. They allow all of an application's files and dependencies to be grouped together in a single folder, nice and neat. To the user, however, the bundle is shown as a single icon and they never see or know about all of the files inside. This allows for one of the best things about bundles - the process of installing or uninstalling an app is just... drag and drop. That's it. And to run the application, just double-click the bundle as if it were the application itself.

However, for the past several years Dolphin on macOS has shipped not one, but two bundles - Dolphin, and Dolphin Updater. The updater didn't do anything if you double-clicked it, and would just give an error; it was intended to be used only by Dolphin itself. Unfortunately, this has occasionally caused confusion with users. After all, the majority of macOS apps are distributed as a single bundle. Why does Dolphin have two?

Fortunately, this has now been fixed. When creating the main Dolphin bundle during a build, we now insert the updater bundle inside of it! Whenever we need to perform a Dolphin update, we just load the updater bundle from within the main Dolphin bundle, create a copy of it in a separate temporary location, and run that. With this change, the user only ever sees one bundle when installing Dolphin for the first time. Glorious single drag and drop installation has been achieved!

2407-173 removes all remnants of the separate updater bundle if any are present. If you have previously installed both Dolphin and the updater to your Applications folder, by the time you are reading this the separate Dolphin Updater will likely already be gone. If not, update and it will be removed.

Note: A bug was fixed in 2407-111 which caused the updater to crash on startup on some Macs. If you are using an older build of Dolphin, you may need to update your copy of Dolphin manually first.

Zelda HLE Pikmin Fixes - 2407-177 and 2407-225 by flacs

Audio emulation has gone through an interesting transformation throughout the many eras of Dolphin. In the release era, HLE (High Level Emulation) audio is pretty much universally used for almost everything. Over the course of time, almost every gap in accuracy between HLE and the more in-depth LLE (Low-Level Emulation) has been closed up. Infamous HLE audio bugs like the screeching in Star Wars: Rogue Squadron games? Solved. The Grand Star hang in Super Mario Galaxy? Long gone.

It has been a massive struggle to get HLE audio to this point. Back in the old days, you had a choice to make - potentially broken audio (or even no audio in some games!) with HLE, or deal with the massive performance demand that came with getting proper audio using LLE. This all started to change back in the 3.5 era, when massive rewrites hit Dolphin's audio code.

Why does this all matter? Well, users didn't like LLE audio, and these massive rewrites to HLE audio had tons of benefits. The problem with HLE audio is that Dolphin has to correctly handle the functions of every revision of every microcode in order for things to work. Pikmin and Pikmin 2 use what we call the "Zelda Microcode". This microcode is used in games like the Zelda games (except Skyward Sword), the Super Mario games and Luigi's Mansion.

The problem with this is that pretty much every game uses a different version of the microcode. This meant that in order to emulate each game, you had to figure out what functions they supported, and how to emulate them correctly. For example, all of the microcode revisions will have functions to control volume, but earlier microcodes might have bugs that need to be emulated, later microcodes might have additional features, like controlling volume individually for different things. Apply this to everything, and it becomes apparent how much of a pain in the rear this can be.

In order to get these massive rewrites merged, support for each individual microcode wasn't necessarily perfect. Upon testing, the games sounded mostly correct, and the various problems of old-HLE audio were fixed. However, there were minor issues spread across the various games. Originally, New-Zelda-HLE had issues with the volume of echoes in Mario Kart: Double Dash. This was a known issue when it was merged, but was deemed acceptable due to all the other improvements.

The only difference between that and Pikmin and Pikmin 2 is that their small issues seemed like they were never going to be addressed. In fact, most users didn't even realize there was a problem. They were by and large playable, and unless you played the game recently on console, you wouldn't know that some menu sounds were the wrong pitch, or there were missing sounds for puffs of smoke in the opening cutscene. Thankfully, when New-Zelda-HLE was merged, the issues we did discover were archived, and flacs saw them and investigated them while looking for more audio issues to fix.

These may seem minor, but back in the day there were hundreds of issues like these due to HLE audio's imperfect emulation of the microcode. It seems almost surreal that, in most cases, HLE audio and LLE audio are now indistinguishable.

2407-228 - VideoCommon: Force Display List Alignment by flacs

Once upon a time, Dolphin bugs were obvious: a simple screenshot was all it took to convey just how broken Dolphin was in a particular title. Grey Zelda, Spider-man as a flying box, uwu Kirby, Batman as a flying crotch, on and on. However, once Dolphin's fundamental inaccuracies were resolved in the 3.5 and 4.0 eras, that largely became a thing of the past. Today, we have to use fifologs and automation to catch changes, and carefully pixel-peep against console to verify that something is in fact actually incorrect.

Wallace and Gromit in Project Zoo bucks this trend. The game's shadows looked fairly good on console, but in Dolphin? They could ƒ^&%ing explode.

We had no idea why the shadows in this fairly obscure game would sometimes fail so catastrophically, but something was clearly very wrong, so in 2013 we added a patch to remove these shadows from the game. It was an extreme solution, but the game had an extreme problem, so we did what we could to at least make the game playable. It was certainly better than the video above. But as time passed, the developers who investigated the problem moved on, and these troublesome shadows slowly faded from memory...

Ten years later, flacs happened to notice that Project Zoo's shadows were still broken, and looked into the issue. They soon spotted something suspicious: the game's display list (a group of GPU commands stored for later execution) wasn't aligned. Rather than prevaricate about the bush, flacs went straight to hardware testing and quickly adapted the triangle test homebrew to use display lists.

Turns out that hunch was spot on target! Wallace and Gromit in Project Zoo submits display lists unaligned, and Dolphin was erroneously processing them exactly as they were submitted. The hardware aligns the memory address by dropping its lower bits. So for example, the game would point toward 0x80fc9b04, and Dolphin would start executing from there (getting bad opcodes) when hardware would drop the lowest 5 bits as it was 32-byte aligned and start at 0x80fc9b00. By not forcing alignment, Dolphin thought the game wanted to render random garbage and told the GPU driver to render it, which the GPU driver would try its best to do. Sometimes this only resulted in minor visual bugs, other times it would utterly explode as shown above.

With a very small change to Dolphin, we can now render these shadows just fine, and yet another hardware quirk is being emulated correctly.

2407-236 - Android: Fix and enable input device sensor input by JosJuice

Last year, JosJuice rewrote our Android controller input handling from scratch. This rewrite replaced the old Java input handler with a brand new one written in C++ that more closely matched how Dolphin's PC input handlers work. Not only did this clean up some crusty old code with known problems, but it also unlocked dozens of "new" features for our Android users that were previously only in our desktop builds!

However, one very significant feature that was a part for that overhaul last year was disabled when the overhaul eventually landed - sensor input (accelerometers and gyroscopes) from external controllers, a feature available in Android 12 and up. During the final testing of the input rewrite, JosJuice received reports that using controller sensors could make Dolphin crash when navigating between screens. Because their phone was stuck on Android 11, they couldn't test the feature themselves, and decided that rather than hold off the rewrite to address the issue, it was best to just disable external sensors for the time being and continue the rollout without it.

With over a year passed since then, dreamsyntax showed up with not only willingness to investigate the crash, but also the needed hardware. The first step: Finding out why the crash is happening. The reports from a year prior included a stack trace showing where in the code the crash occurred, and JosJuice had used this information to theorize that when Dolphin turned off unused sensors to save battery, Android would start notifying Dolphin about a sensor that Dolphin never had asked to be notified about. dreamsyntax was able to replicate the crash and get a match stack trace, and then managed to take a step beyond the old investigation by figuring out the root cause of the crash. The sensor that Dolphin didn't recognize wasn't actually a new sensor - it was a new object representing the same sensor as before. The cause of the bug was that Dolphin checked if two sensor objects were literally the same object (referential equality) rather than checking if the objects had the same content (structural equality).

With that, it was time for the second step: Properly fixing the issue. dreamsyntax began by making a quick solution to check that their approach was correct, but alas, Dolphin was still crashing! It turned out there was a second crash that nobody had discovered until now because the other crash always happened first! Somewhere within the code of Android itself, a ConcurrentModificationException was being thrown when Dolphin turned sensors off. dreamsyntax couldn't quite make sense of why this was happening, but with all the information he had gathered, JosJuice once again stepped into the picture. They discovered that the cause of the crash was a simple coding mistake in the operating system itself - removing objects from a list while looping through the list - and implemented a workaround for this crash and a proper solution for the earlier crash. Finally, dreamsyntax tested the change to make sure motion controls were now working properly.

With the issues now solved, sensors from external controllers are available for mapping in Dolphin on Android! The sensors in controllers such as the DualShock 4 can now be used to better emulate motion in Dolphin. Keep in mind that the feature only works for controllers your version of Android has sensor support for. If you're using Android 11 or older, sensors aren't supported for any controllers at all.

Last Month's Contributors...

Special thanks to all of the contributors that incremented Dolphin 349 commits in the final days of the 5.0 era, and 279 commits after Release 2407!

The First Month of Dolphin RetroAchievements

The RetroAchievements team has shared with us a bunch of statistics for the first month of RetroAchievement support in Dolphin! And there's a lot of interesting bits in here. Enjoy!

General Statistics

Total Unlocks: 860,290

Total Hardcore Unlocks: 815,944

Total Points Earned: 5,864,862

Total Hardcore Points Earned: 5,558,151

Total Sessions: 284,432

Top Ten Games with the Most Players

Game Players
Super Mario Sunshine 2532
Super Smash Bros. Melee 2230
Mario Kart: Double Dash!! 1908
Luigi's Mansion 1148
Legend of Zelda, The: The Wind Waker 1084
WarioWare, Inc.: Mega Party Games! 946
Kirby Air Ride 893
Legend of Zelda, The: Twilight Princess 888
Animal Crossing 847
Pikmin 758

Top Ten Most Mastered Games

Game Masteries
Super Mario Sunshine 284
Piglet's Big Game 195
Magical Mirror Starring Mickey Mouse 172
Pokemon Channel 163
~Hack~ Samus Goes to the Fridge to Get a Glass of Milk 3D 152
Winnie the Pooh's Rumbly Tumbly Adventure 144
~Hack~ Luigi's Mansion Beta Restoration 140
Legend of Zelda, The: The Wind Waker 120
Wario World 112
WarioWare, Inc.: Mega Party Games! 101

Top Ten Most Beaten Games

Game Times Beaten
Super Mario Sunshine 626
WarioWare, Inc.: Mega Party Games! 551
Luigi's Mansion 505
Super Smash Bros. Melee 339
Dance Dance Revolution: Mario Mix 305
Pokemon Channel 297
Mario Kart: Double Dash!! 297
Pikmin 273
Legend of Zelda, The: The Wind Waker 243
Naruto: Clash of Ninja 232

View the official changelog

2407
  • Intégration de la mise à jour de Dolphin directement dans le bundle macOS (DolphinQt), supprimant le bundle séparé pour l’updater et facilitant l’installation/désinstallation par simple glisser-déposer.
  • Correction d’un bug macOS (commit 2407-111) provoquant un plantage de l’updater au démarrage sur certains appareils.
  • Ajout du support pour RetroAchievements, avec une première implémentation stable mais limitée (Android toujours bloqué par des problèmes techniques).
  • Optimisation majeure du Cached Interpreter 2.0 : amélioration de 10 à 25 % de ses performances, réduisant les branches et augmentant sa vitesse jusqu’à 3 à 4 fois par rapport à l’interpréteur classique.
  • Correction des problèmes audio dans Pikmin et Pikmin 2 liés à l’émulation HLE du microcode "Zelda".
  • Forçage de l’alignement des listes de rendu vidéo pour résoudre des artefacts graphiques dans Wallace & Gromit in Project Zoo.

After an exciting round of feature articles, it's Progress Report time once again! However, a lot has changed. Dolphin has finally left the 5.0 era behind, and has entered the Release Era. Not only did we get our first release in eight years, but we also established a commitment to continuous releases going forward.

For the Reports, things will be more or less the same, but with a few changes.

Progress Reports are now also release changelogs. We'll be going over the notable additions and changes between each release in every Progress Report going forward, rather than within a range of dates. As such, the name of the Reports will reflect the release accompanying it - if you want the new features, just update to the version at the top or higher and you'll have them! (However, since 2407 had a release article without a changelog, this Report will be covering the changes in both Release 2407 and Release 2409.)

That also means that the next release is happening right now! Accompanying this report is Dolphin 2409. It is now rolling out via our updater, and is available for download here on our website.

But there was also another feature article since our last Report. Dolphin now has RetroAchievements support!

For those waiting for it to show up in a release build, the wait is now over. Throughout the past couple of months, we've ironed out one major issue alongside many smaller issues with RetroAchievements. The first iteration of RetroAchievements in a release build is stable, but not all that flashy. The groundwork is there for future improvements, but many features and options are yet to be finished. As well, Android support is still deadlocked with a few issues. Please pardon our progress!

We have a bunch of cool statistics from the RetroAchievements team regarding the launch, however, we need to get on with the Report! So just click this handy link to be taken to the bottom of the Report if you'd like to read more!

But before we get to the Notable Changes, we have a couple of things to cover.

Google Play Update Delay

Last month, we got a surprise email from Google Play saying that Dolphin doesn't comply with their policies because it "installs, but doesn't load". We have gotten emails like this before regarding Android TV, presumably because someone at Google tried to install Dolphin on one out of the vast majority of Android TV devices that don't meet Dolphin's hardware requirements, but this is the first time we've gotten a rejection for Android as a whole. Seeing as Dolphin generally does load correctly on devices that are able to install it, we're not quite sure what happened here.

What does this mean for Dolphin? Dolphin is still available on Google Play, but the next update we release has to be manually checked by Google before it becomes available to users. Because of this, it will take longer than normal for the 2409 release to show up on Google Play, but any updates after that should be smooth sailing again. If you're impatient and want the latest version of Dolphin right now, it's available on this website as always!

Visual Studio Twenty-Twenty-Woes

During the rollout of the latest release, a lot of people updated Dolphin for the first time in a while! But for some of our Windows users, when they fired up Dolphin 2407 for the first time they were met with a silent crash. They reached out to us, and the support vanguards on our Discord quickly found a solution - reinstalling the 64-bit Microsoft Visual C++ redistributable for Visual Studio 2022 got Dolphin working for them once again.

We're not entirely sure why exactly this happened. But we have a theory.

The Visual C++ 2022 Redistributable is a runtime library that contains everything needed to run programs compiled with Microsoft Visual Studio 2022. However, Visual Studio 2022 is not static: there are many subversions, and it gets regular updates. These updates should be backwards compatible with any other version of Visual Studio 2022. It would be madness to make a change to Visual Studio 2022 that breaks compatibility with Visual Studio 2022's own runtime libraries. However, Microsoft did exactly that.

In Visual Studio 2022 v17.10.0, Microsoft made a non-backwards compatible change to std::mutex::lock. This was reported to Microsoft, however, the issue report was marked as "Closed - Not a Bug". Apparently this was intended!

This puts us, as an application that uses Visual Studio, into a weird place. We set up an automated process to update our Visual Studio builder to new subversions as they come out, confident that it will never break anything. It's just subversions. So we have told our Windows users that all they need to run Dolphin is the Visual C++ 2022 Redistributable, confident that it would work. However, Visual Studio automatically utilized the new version of std::mutex::lock when compiling our Windows builds. If a user is running an older version of the Visual C++ 2022 Redistributable before that new version of std::mutex::lock was implemented, they may download and run our program and see a silent crash. And of course, if we ask them if they are using the Visual C++ 2022 runtime, they'll say yes, because they have it installed.

According to Microsoft, this is our problem. Their expectation is for applications to be distributed with installers that will include the redistributable and install it with the app if required. However, they hand out the redistributable to users precisely for applications like us that ship without an installer. It's not like what we're doing is novel. And perhaps Microsoft should have made it fail in a way that communicates to the user that they need to update the redistributable, instead of just crashing silently? Or perhaps just include the Visual C++ 2022 runtime libraries in Windows Update so every user is guaranteed to have the latest version and applications don't even need to worry about it?

...Anyway, unfortunately, we don't have a great solution for this issue. We could disable our automated update process for our Visual Studio builder, but there are security benefits to keeping it, so this is something we'd rather not do. For now, all we can tell our Windows users is that if you run a new version of Dolphin and encounter a crash, redownload and reinstall Visual C++ 2022 Redistributable. As always, we have a link to the redistributable on our download page.

On a happier note, it's time for our Notable Changes!

Notable Changes

All of the changes below are available in Release 2409.

5.0-21462 - Windows: Remove rounded corners on emulation render window by Filoppi

When Windows 11 released in late 2021, it brought the first major visual overhaul to Windows since Windows Phone from 2010. Gone were the sharp edges, bold colours, and dense squares of the Live Tile era, and in their place were soft tones, spacious design, and friendly round edges.

However, as part of this new aesthetic, Windows 11 applies round edges everywhere, even to game windows! Pixels that your computer spent your hard-earned money rendering are now hidden in windowed mode by default.


This was unacceptable!

Recognizing this travesty, Filoppi came to the rescue and saved our pixels. By configuring DWM_WINDOW_CORNER_PREFERENCE in our Windows builds, all pixels that Dolphin renders (on Windows 11 and in windowed mode) are now once again free to be seen by our illustrious eyeballs.

If only such relief could be bestowed upon our macOS users as well...

Balloon Tooltip Quality of Life Updates - 5.0-21123, 5.0-21635, and 2407-130 by Dentomologist

A few years ago we introduced our custom balloon tooltips. Rather than have a large description area permanently taking up space or a terrible native tooltip defined by the OS, we created our own custom tooltips that gave us the best of both worlds.

They have been serving us well since. However, after they were rolled out for the graphics area of our config, they haven't really been touched since then. Now that's changing, and our Balloon Tooltips are finally getting some much needed love and a wider rollout!

First is 5.0-21123, which reworked how they are drawn to resolve many longstanding quibbles with the tooltips.

Next is 5.0-21635, which added tooltips to the Interface tab of Config.

And finally 2407-130, which rolls out our tooltips to the General tab of Config!

Dentomologist is still chipping away at the tooltips, so expect them to continue to improve and be applied to more windows over time!

2407-103 - Cached Interpreter 2.0 by mitaclaw

After the merge of "Cached Interpreter 2.0", we've seen some misinformation floating around emulation communities regarding what the cached interpreter is and what this change has brought. So for the Progress Report, we felt it was prudent to take a deep dive, and properly explain a bunch of concepts we've been putting off for years now. Strap in everyone, we're going deep!


The primary task of CPU emulation is translation: we take code that was originally designed for a specific type of CPU and translate it into something that a different type of CPU can understand. This is not free. Even ignoring the work involved in the act of translating in and of itself (more on that later), having to account for hardware differences means that the resulting translated code will usually be many times larger and more complex than the original code was on the original hardware. As such, there are many different approaches to CPU emulation.

Interpretation is the most basic and literal CPU translation method. An interpreter decodes each individual instruction from the emulated architecture (guest), then translates that into the instructions (plural) that allow the host to perform the same work. And yes, it translates one instruction at a time. This is extremely accurate (able to preserve all nuance) and very straightforward, making interpreters the perfect entry point for most emulators and a fallback for other translation methods. However, interpreters are so straightforward that they have barely any wiggle-room for optimization. Interpreters will always be costly.

Recompilation gives us that wiggle-room. By translating the code in blocks rather than per instruction, recompilers can peek into what the code is doing and reimplement troublesome code in ways that are faster for the host hardware. However, reimplementation often causes inaccuracy, and correcting for that without sacrificing speed leads to ballooning complexity. Making a recompiler both fast and accurate can easily take thousands of hours from passionate engineers.

There are many different types of recompilers, but we're just going to focus on the primary recompiler type that Dolphin uses: JITs.

Just-In-Time Recompilation (JIT) recompiles small blocks of code while the program is running. A JIT will fetch blocks of code from the program, analyze and reimplement as much as it can, then pass the JITed code to the host system to be processed and ready just before the program needs to consume those blocks.

"Just-In-Time" is literal.

The live analysis that JITs perform is overhead. While modern JITs will mitigate this somewhat by caching JITed code blocks, the analysis is still work, which some other recompilation techniques avoid. However, JITs have many benefits. By recompiling blocks of code while the program is running, JITs are able to adapt to whatever the program is doing and don't need to rely on assumptions. This allows for maximum optimization potential, even in self-modifying programs!


With that, we've covered the two most common CPU emulation techniques. Generally, there is nothing inbetween these two options. Emulator authors make an interpreter first, and use it as a reference for building a recompiler. And that's it. Recompilers are so much faster than interpreters that making an interpreter faster is largely irrelevant.

There are several reasons for this. For example, interpreters can't place guest registers into the host registers, so any time the emulated CPU wants to read its registers, an interpreter has to fetch the registers' contents from host system memory, which is two orders of magnitude slower. Also, for Dolphin, our interpreter has the MMU enabled at all times, and the constant memory manipulation is even slower in the interpreter than it is for a JIT!

However, what slows down interpreters the most is branching.

In computer science, a branch is the act of diverging from the current flow of instructions. If a CPU is executing instructions sequentially, it can process them very very fast. But if an unpredictable branch occurs, the CPU will need to stop everything, flush all its pipelines, and spend the next 10-20 cycles building them back up again before it can resume processing. Branching is one of the most expensive low level operations in computing! As such, modern CPUs do everything they possibly can to improve branch performance, with branch prediction and speculative branch execution trying to get ahead of any branches and keep the pipelines flowing. These features are so important that improved branch prediction is one of the primary reasons why a 2024 CPU core at 4ghz is faster than a 2004 CPU core at 4ghz. It's that significant.

By operating on each instruction from the guest, one at a time, an interpreter will need to branch very frequently - several times for even a single instruction. And these branches are usually unpredictable, directly hurting what makes modern CPUs fast. With all factors combined and in a worst case scenario, a single instruction from the guest could take over a hundred cycles for our interpreter to decode! This occurs millions of times per second, thrashing our host CPU.

Interpreters are simple, straightforward, and readable, but they are fundamentally inefficient. A recompiler will always be faster, so there is little incentive to make an interpreter faster. Except, perhaps, for fun.

Nine years ago, degasus had a fun idea. How fast could an interpreter be made (while still being an interpreter) if we applied a bunch of ideas from JITs? The result of this little experiment was the Cached Interpreter.

With a JIT, code is collected into blocks and recompiled into host-specific machine code all together. This allows the JIT to reimplement some of the code to be faster for the host, but also allows the JIT to cache these JITed code blocks, so that any time code is reused, the JIT will just jump to the cache and skip the analysis for a speedup.

Dolphin's Cached Interpreter borrows this idea. Code is collected into blocks exactly like a JIT. However, rather than recompile it into JITed machine code, which is specific to the host and may be reimplemented, the code block is instead translated into an intermediate representation - code which stores the decoded instructions as "commands" that can be compiled into machine code that the host CPU can run.

This benefits our Cached Interpreter in many ways. Just like a JIT, the code blocks can be cached. Any time code reappears, the Cached Interpreter can just reuse the already decoded version in the cache, skipping the decode and all its associated branching. The act of interpreting in blocks rather than per instruction also reduces branching outright, down to roughly one branch per command, and makes branches more predictable too. This also reduces the cost of fetching instructions through the MMU, and brings several other benefits from the JIT, such as Idle Skipping. *

All combined, the Cached Interpreter was over twice as fast as our interpreter when it released! However, it was still an order of magnitude slower than our JITs. For most users, it was more or less irrelevant. However, the Cached Interpreter has found its niches. As it is still an interpreter, it retains the impeccable accuracy that interpreters provide, as well as the ability to run on any architecture - it's our interpreter, but faster. As such, it has become a useful tool for testing and JIT development. Plus, in situations where JIT recompilers are unavailable, the substantial speedup versus the standard interpreter is always welcome.

But what if the Cached Interpreter could be taken further?

Fast forward to 2024, and mitaclaw and Sam-Belliveau got into a competition to see just how optimized the Cached Interpreter could be. Eventually they merged their efforts, in what mitaclaw dubbed Cached Interpreter 2.0.

This change brought many optimizations to the Cached Interpreter, but the biggest change by far was variable sized commands. Previously, the commands inside the Cached Interpreter's intermediate representation had a fixed size, but mitaclaw and Sam-Belliveau realized that by allowing the commands to be any size, the most common bookkeeping commands could be bundled together into a single command. This significantly reduces the number of bookkeeping commands in total, further reducing the amount of branching in our Cached Interpreter.

Just how big of an impact could these optimizations have? Let's get to the numbers!


With a 10 to 25% uplift, the Cached Interpreter is better than ever! It's also now 3 to 4 times faster than the interpreter, and in games with lots of idle loops to skip, such as Cave Story, Cached Interpreter leaves our interpreter in the dust. However, our JITs are still MUCH faster in every scenario, so its role in Dolphin is unchanged. The Cached Interpreter still cannot serve as a JIT alternative. And according to mitaclaw, further optimizations had a negligible impact on its performance. Dolphin's Cached Interpreter will likely not see another significant performance bump again.

Nevertheless, for the niches where the Cached Interpreter thrives, it is now faster than it has ever been.

2407-165 - macOS: Embed the Updater into DolphinQt's app bundle by OatmealDome

One of the best things about macOS is application bundles.

On Windows, programs are largely intended to bring their own dependencies. However, each program will need many different files in many different and bizarre places, so much so that it is standard to ship a dedicated program whose only purpose is to place or remove all of the disparate files an application needs to function. If something goes wrong with this process, good luck.

Linux, on the other hand, works more like code - dependencies are separate from the program and should be linked, not duplicated. However, dependencies will need to be installed along with the application, so Linux has package managers to install applications and any dependencies that are needed. While this is certainly better than the backwards-compatibility mess that is Windows, installing a single application in Linux still results in installing lots of things in lots of places.

macOS is different. It has something called application bundles. All apps on macOS (with the exception of command-line tools and scripts) are distributed in the bundle format. Application bundles are really just regular folders that follow a very specific structure with their contents. They allow all of an application's files and dependencies to be grouped together in a single folder, nice and neat. To the user, however, the bundle is shown as a single icon and they never see or know about all of the files inside. This allows for one of the best things about bundles - the process of installing or uninstalling an app is just... drag and drop. That's it. And to run the application, just double-click the bundle as if it were the application itself.

However, for the past several years Dolphin on macOS has shipped not one, but two bundles - Dolphin, and Dolphin Updater. The updater didn't do anything if you double-clicked it, and would just give an error; it was intended to be used only by Dolphin itself. Unfortunately, this has occasionally caused confusion with users. After all, the majority of macOS apps are distributed as a single bundle. Why does Dolphin have two?

Fortunately, this has now been fixed. When creating the main Dolphin bundle during a build, we now insert the updater bundle inside of it! Whenever we need to perform a Dolphin update, we just load the updater bundle from within the main Dolphin bundle, create a copy of it in a separate temporary location, and run that. With this change, the user only ever sees one bundle when installing Dolphin for the first time. Glorious single drag and drop installation has been achieved!

2407-173 removes all remnants of the separate updater bundle if any are present. If you have previously installed both Dolphin and the updater to your Applications folder, by the time you are reading this the separate Dolphin Updater will likely already be gone. If not, update and it will be removed.

Note: A bug was fixed in 2407-111 which caused the updater to crash on startup on some Macs. If you are using an older build of Dolphin, you may need to update your copy of Dolphin manually first.

Zelda HLE Pikmin Fixes - 2407-177 and 2407-225 by flacs

Audio emulation has gone through an interesting transformation throughout the many eras of Dolphin. In the release era, HLE (High Level Emulation) audio is pretty much universally used for almost everything. Over the course of time, almost every gap in accuracy between HLE and the more in-depth LLE (Low-Level Emulation) has been closed up. Infamous HLE audio bugs like the screeching in Star Wars: Rogue Squadron games? Solved. The Grand Star hang in Super Mario Galaxy? Long gone.

It has been a massive struggle to get HLE audio to this point. Back in the old days, you had a choice to make - potentially broken audio (or even no audio in some games!) with HLE, or deal with the massive performance demand that came with getting proper audio using LLE. This all started to change back in the 3.5 era, when massive rewrites hit Dolphin's audio code.

Why does this all matter? Well, users didn't like LLE audio, and these massive rewrites to HLE audio had tons of benefits. The problem with HLE audio is that Dolphin has to correctly handle the functions of every revision of every microcode in order for things to work. Pikmin and Pikmin 2 use what we call the "Zelda Microcode". This microcode is used in games like the Zelda games (except Skyward Sword), the Super Mario games and Luigi's Mansion.

The problem with this is that pretty much every game uses a different version of the microcode. This meant that in order to emulate each game, you had to figure out what functions they supported, and how to emulate them correctly. For example, all of the microcode revisions will have functions to control volume, but earlier microcodes might have bugs that need to be emulated, later microcodes might have additional features, like controlling volume individually for different things. Apply this to everything, and it becomes apparent how much of a pain in the rear this can be.

In order to get these massive rewrites merged, support for each individual microcode wasn't necessarily perfect. Upon testing, the games sounded mostly correct, and the various problems of old-HLE audio were fixed. However, there were minor issues spread across the various games. Originally, New-Zelda-HLE had issues with the volume of echoes in Mario Kart: Double Dash. This was a known issue when it was merged, but was deemed acceptable due to all the other improvements.

The only difference between that and Pikmin and Pikmin 2 is that their small issues seemed like they were never going to be addressed. In fact, most users didn't even realize there was a problem. They were by and large playable, and unless you played the game recently on console, you wouldn't know that some menu sounds were the wrong pitch, or there were missing sounds for puffs of smoke in the opening cutscene. Thankfully, when New-Zelda-HLE was merged, the issues we did discover were archived, and flacs saw them and investigated them while looking for more audio issues to fix.

These may seem minor, but back in the day there were hundreds of issues like these due to HLE audio's imperfect emulation of the microcode. It seems almost surreal that, in most cases, HLE audio and LLE audio are now indistinguishable.

2407-228 - VideoCommon: Force Display List Alignment by flacs

Once upon a time, Dolphin bugs were obvious: a simple screenshot was all it took to convey just how broken Dolphin was in a particular title. Grey Zelda, Spider-man as a flying box, uwu Kirby, Batman as a flying crotch, on and on. However, once Dolphin's fundamental inaccuracies were resolved in the 3.5 and 4.0 eras, that largely became a thing of the past. Today, we have to use fifologs and automation to catch changes, and carefully pixel-peep against console to verify that something is in fact actually incorrect.

Wallace and Gromit in Project Zoo bucks this trend. The game's shadows looked fairly good on console, but in Dolphin? They could ƒ^&%ing explode.

We had no idea why the shadows in this fairly obscure game would sometimes fail so catastrophically, but something was clearly very wrong, so in 2013 we added a patch to remove these shadows from the game. It was an extreme solution, but the game had an extreme problem, so we did what we could to at least make the game playable. It was certainly better than the video above. But as time passed, the developers who investigated the problem moved on, and these troublesome shadows slowly faded from memory...

Ten years later, flacs happened to notice that Project Zoo's shadows were still broken, and looked into the issue. They soon spotted something suspicious: the game's display list (a group of GPU commands stored for later execution) wasn't aligned. Rather than prevaricate about the bush, flacs went straight to hardware testing and quickly adapted the triangle test homebrew to use display lists.

Turns out that hunch was spot on target! Wallace and Gromit in Project Zoo submits display lists unaligned, and Dolphin was erroneously processing them exactly as they were submitted. The hardware aligns the memory address by dropping its lower bits. So for example, the game would point toward 0x80fc9b04, and Dolphin would start executing from there (getting bad opcodes) when hardware would drop the lowest 5 bits as it was 32-byte aligned and start at 0x80fc9b00. By not forcing alignment, Dolphin thought the game wanted to render random garbage and told the GPU driver to render it, which the GPU driver would try its best to do. Sometimes this only resulted in minor visual bugs, other times it would utterly explode as shown above.

With a very small change to Dolphin, we can now render these shadows just fine, and yet another hardware quirk is being emulated correctly.

2407-236 - Android: Fix and enable input device sensor input by JosJuice

Last year, JosJuice rewrote our Android controller input handling from scratch. This rewrite replaced the old Java input handler with a brand new one written in C++ that more closely matched how Dolphin's PC input handlers work. Not only did this clean up some crusty old code with known problems, but it also unlocked dozens of "new" features for our Android users that were previously only in our desktop builds!

However, one very significant feature that was a part for that overhaul last year was disabled when the overhaul eventually landed - sensor input (accelerometers and gyroscopes) from external controllers, a feature available in Android 12 and up. During the final testing of the input rewrite, JosJuice received reports that using controller sensors could make Dolphin crash when navigating between screens. Because their phone was stuck on Android 11, they couldn't test the feature themselves, and decided that rather than hold off the rewrite to address the issue, it was best to just disable external sensors for the time being and continue the rollout without it.

With over a year passed since then, dreamsyntax showed up with not only willingness to investigate the crash, but also the needed hardware. The first step: Finding out why the crash is happening. The reports from a year prior included a stack trace showing where in the code the crash occurred, and JosJuice had used this information to theorize that when Dolphin turned off unused sensors to save battery, Android would start notifying Dolphin about a sensor that Dolphin never had asked to be notified about. dreamsyntax was able to replicate the crash and get a match stack trace, and then managed to take a step beyond the old investigation by figuring out the root cause of the crash. The sensor that Dolphin didn't recognize wasn't actually a new sensor - it was a new object representing the same sensor as before. The cause of the bug was that Dolphin checked if two sensor objects were literally the same object (referential equality) rather than checking if the objects had the same content (structural equality).

With that, it was time for the second step: Properly fixing the issue. dreamsyntax began by making a quick solution to check that their approach was correct, but alas, Dolphin was still crashing! It turned out there was a second crash that nobody had discovered until now because the other crash always happened first! Somewhere within the code of Android itself, a ConcurrentModificationException was being thrown when Dolphin turned sensors off. dreamsyntax couldn't quite make sense of why this was happening, but with all the information he had gathered, JosJuice once again stepped into the picture. They discovered that the cause of the crash was a simple coding mistake in the operating system itself - removing objects from a list while looping through the list - and implemented a workaround for this crash and a proper solution for the earlier crash. Finally, dreamsyntax tested the change to make sure motion controls were now working properly.

With the issues now solved, sensors from external controllers are available for mapping in Dolphin on Android! The sensors in controllers such as the DualShock 4 can now be used to better emulate motion in Dolphin. Keep in mind that the feature only works for controllers your version of Android has sensor support for. If you're using Android 11 or older, sensors aren't supported for any controllers at all.

Last Month's Contributors...

Special thanks to all of the contributors that incremented Dolphin 349 commits in the final days of the 5.0 era, and 279 commits after Release 2407!

The First Month of Dolphin RetroAchievements

The RetroAchievements team has shared with us a bunch of statistics for the first month of RetroAchievement support in Dolphin! And there's a lot of interesting bits in here. Enjoy!

General Statistics

Total Unlocks: 860,290

Total Hardcore Unlocks: 815,944

Total Points Earned: 5,864,862

Total Hardcore Points Earned: 5,558,151

Total Sessions: 284,432

Top Ten Games with the Most Players

Game Players
Super Mario Sunshine 2532
Super Smash Bros. Melee 2230
Mario Kart: Double Dash!! 1908
Luigi's Mansion 1148
Legend of Zelda, The: The Wind Waker 1084
WarioWare, Inc.: Mega Party Games! 946
Kirby Air Ride 893
Legend of Zelda, The: Twilight Princess 888
Animal Crossing 847
Pikmin 758

Top Ten Most Mastered Games

Game Masteries
Super Mario Sunshine 284
Piglet's Big Game 195
Magical Mirror Starring Mickey Mouse 172
Pokemon Channel 163
~Hack~ Samus Goes to the Fridge to Get a Glass of Milk 3D 152
Winnie the Pooh's Rumbly Tumbly Adventure 144
~Hack~ Luigi's Mansion Beta Restoration 140
Legend of Zelda, The: The Wind Waker 120
Wario World 112
WarioWare, Inc.: Mega Party Games! 101

Top Ten Most Beaten Games

Game Times Beaten
Super Mario Sunshine 626
WarioWare, Inc.: Mega Party Games! 551
Luigi's Mansion 505
Super Smash Bros. Melee 339
Dance Dance Revolution: Mario Mix 305
Pokemon Channel 297
Mario Kart: Double Dash!! 297
Pikmin 273
Legend of Zelda, The: The Wind Waker 243
Naruto: Clash of Ninja 232

5.0

No details for this version.

5.0-rc

No details for this version.

4.0.2

No details for this version.

4.0.1

No details for this version.

4.0

No details for this version.

Reply on the forum

A question or a hands-on report? Open the discussion on the forum.

Reply on the forum