BOTW Gyro stops working at shrines, CEMU is latest version, no CEMUHook available

[causeburn]

This seems to be an issue for a few people.

I have emudeck installed, the latest Cemu version installed and SteamDeckGyroDSU installed.

The gyro functionality works great outside of shrines but when I need to do the puzzles, it stops working.

The instructions seem to be outdated and assume Cemuhook is still being created for the latest Cemu version. Since Cemuhook is depreciated how are people supposed to get this problem fixed?

I can see the old instructions here https://github.com/kmicki/SteamDeckGyroDSU but as I mentioned, Cemuhook doesnt appear to work with the latest Cemu.

[kmicki]

Hi,

Gyro working outside of shrines means that Steam is translating gyro into right joystick input and SteamDeckGyroDSU isn't used at all.

In Cemu 2 it needs to be configured using "DSU controller" in input settings. I think Emudeck does that automatically but I am not sure. I will update the instructions as soon as I have some time.

[kmicki]

The controller settings in steam are completely independent from SteamDeckGyroDSU. They can even work together. But Steam can only use gyro to emulate joystick or mouse so it will not work in shrines.

Could you execute a command in Konsole in Desktop Mode when Cemu is running (game doesn't have to be started):

systemctl --user status sdgyrodsu

and paste the output here?

[causeburn]

Well it doesnt appear to be running at least.

I launched Cemu for Emudeck and have the main program window open, not running any games (per your post).

This is the response I get for the command

• https://i.ibb.co/qscCvgm/MVIMG-20221224-120553.jpg

[kmicki]

That means it's not installed. I guess installation of sdgyrodsu by Emudeck is not working properly.

Try installing using the instructions on the readme page.

[Godsbane]

Hi Kmicki - we have fixed the installer. Sorry for any inconvenience.

When we moved from a script installer to the AppImage, it stopped working because of some sudo -V / sudo -S / environment interaction we couldn't get around.

Found a solution though, and it should work again.

[Philomorph]

I was pulling my hair out trying to find this solution - so much old info using cemuhook, etc, is still out there.
But even once I got here, Cemu couldn't find the controller from the server, even though I knew it was running. The key was systemctl command above - it showed me that the server was running on IP address 0.0.0.0, but Cemu by default was looking at the LOCALHOST address. Once I manually typed in the correct IP it found the controller and I was up and running.

Thanks!