Greetings yuz-ers! Welcome to September’s progress report. This month we offer you the joy of motion, video playback, more input fixes and additions, small Vulkan improvements, and the initial groundwork needed to get Super Mario 3D All-Stars playable.
Many popular Nintendo Switch titles have mechanics designed with motion controls in mind, so naturally this was a long-awaited feature that a lot of people wanted to see implemented in yuzu. We are very happy to announce that, thanks to the efforts of the developer german77, it is now possible to use any controller that supports motion sensing and play these games the way they were meant to be played. Just be careful not to hit anything when you shake it!
Functional Motion Input ('A SixAxis tester by German77', a homebrew application).
This feature’s development began back in July, when german77 was working on the implementation of a native Joy-Con adapter for yuzu (a task still in the works). While he was analyzing the data sent by the controllers, he realized he could read the values reported by the accelerometer and the gyroscope as well. Feeling curious about what could be done with this knowledge, he experimented with implementing new inputs and feeding them the output from these sensors. The result was quite satisfactory: not only did this work, but it became the main motivation to investigate and implement motion controls the same way they work on the Switch.
german77 was aware of a previously discontinued PR for motion by anirudhb and decided the best course of action would be to take it from there, fix any incompatibilities, and sort out the subsequent bugs introduced. As he ironed out the implementation, he tested how it performed with the game
Captain Toad: Treasure Tracker. The results this time, however, were far from satisfactory. Controls felt unnatural and responded quite differently compared to the Switch, indicating an error in how the values sent by the controllers were processed. To better understand the problem, german77 developed two homebrew applications to identify and fix these inaccuracies.
After a long period of extensive testing, and with the help of theboy181 (who focused on testing the feature on different games), german77 finally realized the problem laid in the implementation’s logic: there was an error transforming a quaternion into a rotation matrix. For the people allergic to math, you can think of a quaternion as a system to describe orientations and rotations in a 3D space, and a rotation matrix as a “translation” from a quaternion to a familiar (x, y, z) Cartesian coordinate. Thankfully, once this error was fixed, almost all the games that showed problems started to work flawlessly!
Motion in action. Top: 'Super Mario Odyssey', bottom: 'The Legend of Zelda: Breath of the Wild'.
Motion controls currently work with Wiimotes, Joy-Cons, Pro Controllers, DualShock 4 Wireless Controllers, and even cellphones (provided they have an accelerometer and a gyroscope). To bridge these devices to yuzu, the implementation makes use of the DSU protocol (also known as “CemuHook UDP”), so users need to utilize BetterJoy (for Nintendo controllers), ds4windows (for Sony controllers), or any app that supports CemuHook for cellphones or other compatible devices. You can check this guide for more information regarding how to set up your controller. Make sure to try it out!
Bear in mind that devices such as generic copies of official Nintendo or Sony controllers may work, although it’s not guaranteed. Needless to say, no matter how hard you shake your keyboard and mouse, that’s not going to work, so please don’t do it!
If your favorite controller has no support for motion controls (such as Xbox controllers), don’t worry, not everything is lost. After implementing functional motion controls, german77 also made this follow-up PR to implement a button to simulate a shake. This will allow you to configure any key of your liking to work as if you were physically swinging your controller and activating the in-game motion mechanics.
While this should work with games such as
Super Mario Odyssey and others, do note it won’t be able to cover all cases or titles. Every game is different, and the required input is not always just a shake.
Also thanks to german77, yuzu can now proudly boast Rumble support. Any SDL2 compatible device will vibrate when asked by your Switch games. This includes but is not limited to: DualShock, Xbox, and Nintendo controllers.
HD Rumble is not possible, yet. The SDL2 specification is incompatible, and not everyone will play with Nintendo peripherals. This means that a Pro Controller or a pair of Joy-Cons cannot reach the same level of precision as the Switch. Additionally, some games seem to use different ways to ask for rumble and are not supported yet. We are investigating this.
Soon, german77 has plans to add native Joy-Con pairing support. This will allow for real HD Rumble compatibility.
It’s finally here! After such a long wait, and thanks to the work from ogniK and epicboy, yuzu can now play videos in-game! For now, only
VP9 videos are supported, which thankfully seems to cover all released games until now. Support for
VP8 will come later.
Video Killed the Radio Star (Mario Kart 8 Deluxe)
This is possible by using FFmpeg. For now, decoding happens in a single CPU thread, and support for multiple threads and GPU decoding is currently being worked on.
We have an entire article dedicated to showing how this feature came to be, how it works, its challenges, and current limitations in more detail here. Please take your time to read it: it also includes a list of games confirmed working and not-so-working yet.
Super Mario 3D All-Stars is a special case in several aspects. For starters, the game is just a container for several other binary executables (known as
Program NCAs), each one with their own Title ID. Step one to get this game to boot is to correctly handle these multi-content games, a job Morph did.
Good, finished, right? Wrong. Turns out, handling several integrated programs with different title IDs will make XCI game dumps conflict, as they include games and even firmware updates to account for users without internet access. Morph also had to add checks for cases like this.
Next step, unimplemented functions. Morph did a partial implementation of
LoadOpenContext, a function that several collections games use. Some examples are
Clubhouse Games: 51 Worldwide Classics,
Grandia HD Collection,
XCOM 2 Collection,
Baldur's Gate I and II,
Dr Kawashima's Brain Training, and of course
Super Mario 3D All-Stars.
GetPreviousProgramIndex needed to be stubbed. The result is getting the game-selector/menu working.
VK_KHR_timeline_semaphore is a relatively recent Vulkan extension only supported by desktop or laptop GPUs. In the past, resources were being assigned with
VkFence and freed when arbitrarily asked, leading to a possible small pileup. With
VK_KHR_timeline_semaphore, each resource is tied to a periodically checked “GPU tick,” and you only need to verify on which tick you are at the moment to know if that resource is now free.
Adding support for timeline semaphores in yuzu helps simplify the code a lot, improves VRAM use a small amount, and paves the way for the finalization of the
Texture Cache rewrite. Thank you, Rodrigo, for its addition! The result should be transparent for the user with no perceptible change besides a bit of VRAM savings.
A missing feature in the input rewrite was the ability to merge two separate single left and right Joy-Cons into a single dual Joy-Con, a function
Super Mario Odyssey needs. Morph implemented
MergeSingleJoyasDualJoy, so this is no longer a problem for Mario. He can return to work once again for nothing. Thirty-nine years and no rewards for the best hero the Mushroom Kingdom ever saw.
Users have been reporting input latency, so Tobi decided to test some changes and see if the situation improves. To further mitigate this issue if you experience it, be sure to enable
Radeon Anti-Lag or
Nvidia Ultra-Low Latency in your respective driver control panel. Nothing makes you ragequit more than losing in Smash due to lag.
Gamecube controllers will now be autoconfigured! Thanks to work done by german77, Gamecube Adapter controllers will show up as devices in the input window, and their buttons will be mapped automatically. Laziness is the best.
Clubhouse Games: 51 Worldwide Classics now manages to boot and, with a save, load the board games. Morph managed this by implementing the
Get/SetNpadHandheldActivationMode functions. However, the game will still render almost everything in black, so don’t consider it playable yet.
Paint it all black (Clubhouse Games: 51 Worldwide Classics)
If you ran a game in fullscreen and a pop-up needed to display (for example, naming a character), it used to render behind the main yuzu window, forcing you to exit fullscreen, focus the pop-up, complete the action, and then continue with your game. Quite annoying indeed. Morph is our savior for this one, by using the
Qt::WindowStaysOnTopHint flag, the pop-ups will now display on top of your game. Thanks a lot, poyo.
Recent Nvidia Geforce drivers (past the 446.14 version) introduced a performance regression mainly affecting
Paper Mario: The Origami King and
Super Smash Bros. Ultimate's menus, important enough that we had to recommend our users to stay on older driver versions until we could figure out what was going on. Turns out, the new drivers don’t seem to like how Qt handles VSync, so Rodrigo fixed it by calling
SwapBuffers from the emulation thread. This change means that Nvidia users are free to use the latest driver version without fearing low framerates.
Just in time for Ampere, eh! Good luck getting one for now (Super Smash Bros. Ultimate)
As mentioned in July’s progress report, toastUnlimited continued to work on solving crashes only experienced with recent Nvidia Vulkan drivers in Linux. Thanks to work done by DXVK, toast’s current implementation aims to be global, and so far we haven’t got any report on getting the issue or any sort of regression. Please feel free to contact us if you are still affected by this issue.
Not a fix in yuzu’s code, but in fact a fix AMD implemented in their drivers. As mentioned in the previous August progress report,
VK_EXT_extended_dynamic_state was giving problems on the AMD Vulkan Windows driver. This has been fixed in the latest 20.9.2 driver version, allowing yours truly to remove the previously needed blacklisting. No more nightmares when playing
Super Mario Odyssey.
Not much information can be given right now, but you all should know that Raptor is advancing at a very impressive speed. Our devs are so preoccupied with whether they can, they don’t stop to think if they should.
That’s all she wrote, folks! See you next time in the October progress report!