Progress Continues
We've already had 21646 updates since Dolphin 5.0. Keep up with Dolphin's continuing progress through the Dolphin Blog: February, March, and April 2024 Dolphin Progress Report.
User-info.png The Dolphin Emulator Wiki needs your help!
Dolphin can play thousands of games, and changes are happening all the time. Help us keep up! Join in and help us make this the best resource for Dolphin.

DSU Client: Difference between revisions

Jump to navigation Jump to search
(→‎Troubleshooting: added info about emulated pointer total yaw)
(Minor additions to the Troubleshooting area and removed evdev references for now, it needs further work before it's ready.)
Line 5: Line 5:


=== Linux ===
=== Linux ===
As of {{revision|5.0-11083}}, motion axis of Wii Remotes, DualShock 3 and DualShock 4 controllers can be directly mapped in Dolphin through evdev input API. Additionally, the following servers are available:
* '''[https://github.com/TheDrHax/ds4drv-cemuhook ds4drv] (TheDrHax fork):''' compatible with all DualShock 4 controllers.
* '''[https://github.com/TheDrHax/ds4drv-cemuhook ds4drv] (TheDrHax fork):''' compatible with all DualShock 4 controllers.
* '''[https://github.com/v1993/linuxmotehook linuxmotehook]:''' compatible with Wii Remotes. For Wii titles, it's recommended to connect the Wii Remotes directly to Dolphin instead of using a DSU Server.
* '''[https://github.com/v1993/linuxmotehook linuxmotehook]:''' compatible with Wii Remotes. For Wii titles, it's recommended to connect the Wii Remotes directly to Dolphin instead of using a DSU Server.
Line 50: Line 49:


If they are blank (e.g. the current controller configuration was created by an older Dolphin version), you can manually assign the corresponding motion axes by right-clicking each binding and picking the corresponding axis on the end of the list or you can simply click on the Default button in the main window (but keep in mind this will reset all bindings in all tabs).
If they are blank (e.g. the current controller configuration was created by an older Dolphin version), you can manually assign the corresponding motion axes by right-clicking each binding and picking the corresponding axis on the end of the list or you can simply click on the Default button in the main window (but keep in mind this will reset all bindings in all tabs).
Additionally, if you're on Linux, you can completely skip the whole setup of DSU Server/Client and directly assign the motion sensor axes of DualShock 3 and 4 controllers by selecting the corresponding <code>evdev/x/xxxx</code> entry on the Devices drop-down menu, thanks to the Linux evdev API natively supporting those controllers.


=== Emulated pointer ===
=== Emulated pointer ===
Line 57: Line 54:


== Troubleshooting ==
== Troubleshooting ==
=== <code>DSUClient/x/xxxx</code> entries doesn't appear on Dolphin's Devices List ===
=== <code>DSUClient/x/xxxx</code> entries doesn't appear on Dolphin's Devices list ===
Assuming you've set up your DSU Server correctly, here's a common checklist:
Assuming you've set up your DSU Server correctly, here's a common checklist:
* Is the DSU Server running?
* Did you enable DSU Client in Dolphin? (Controller Settings => Alternate Input Sources)
* Did you enable DSU Client in Dolphin? (Controller Settings => Alternate Input Sources)
* Did you specify the correct server IP Address and server port on Dolphin?
* Did you specify the correct server IP Address and server port on Dolphin?
Retrieved from "https://wiki.dolphin-emu.org/index.php?title=DSU_Client"