Последние статьи

It feels like it's been some time since we've had actually had a monthly Progress Report. This is because there haven't been as many major changes landing, making it harder to fill out a substantial article. That isn't to say that things have slowed down, these smaller changes increase the quality of life for users and add up, especially when jumping from older builds to the latest. However, these changes are a lot harder to show and feature in a Progress Report compared to things that actually affect the core emulation and games. This time around, we had more than enough on our plate to write about, including support in the latest builds for a very interesting game: The Metroid Prime 3's E3 2006 Beta.

But before we get to the new changes, we need to cover something we missed last month. So, without further delay, please enjoy the mostly April Progress Report!

We understand that the past few months have been trying for many of us across the world. Something like this can make what you do feel so very small in the grand scheme of things. Everyone has their ways of coping with isolation, using the internet, games, emulation, and much more as forms of entertainment to keep spirits up. To those of you relying on Dolphin Emulator, we hope that Dolphin Emulator makes your day a little brighter in these trying times.

In this Progress Report, you'll find that we've got a lot of changes affecting things outside of core emulation. For instance, Dolphin on Android and macOS see the return of Dark Mode, perfect for late night gaming without straining your eyes. But if we're going to talk about the main event, we have a new way to use your Wii Remotes that brings tremendous flexibility. People that were disappointed by the removal of Hybrid Wii Remotes, forced Wii Remote disconnections on Save/Loadstates, and other limitations of Real Wii Remotes should be very excited. With two months of changes to get through, it's about time we just dived in. Please enjoy the February and March Progress Report!

The Progress Report has come and with it some major changes and decisions. However, before we get into new things, we need to go over an ongoing change as we've seen some users struggling. In the last progress report, we updated our project solutions to Microsoft Visual Studio C++ 2019. We thought there would be no issues at the time, after all, Microsoft says that VS2019 runtimes are forward and back compatible with VS2015 and VS2017, however, it turns out that is not always the case, and we definitely encountered one of the incompatible scenarios. Over the past two months, we've seen many reports of users encountering "VCRUNTIME140_1.dll was not found" errors and not knowing what to do. So just as a reminder, if you encounter MSVC or VCRUNTIME errors, install the latest x64 Microsoft Visual Studio runtimes from Microsoft's website (direct link). Even on updated versions of Windows, you may be missing the latest runtime as these runtimes are not distributed through Windows update for whatever reason. We hope this clears up any problems users were having regarding these issues.

With that, we've got a lot to get through from the past two months. From unintentionally stumbling into an Achilles's Heel of the Zen CPU architecture and tanking performance to supporting a brand new environment with Windows on ARM support, we're going to run the gamut of big features, decisions, and fixes. So without further ado, let's get to it.