15,189
edits
DSU Client: Difference between revisions
Re-add evdev mentions now that PR #8473 got merged
(→Windows: I'm not entirely happy pointing to this this chinese forum but it seems to be the only place where WiimoteHook can be found now, as the Cemu forums are down for quite long and there's no ETA on when they'll be back...) |
(Re-add evdev mentions now that PR #8473 got merged) |
||
| Line 5: | Line 5: | ||
=== Linux === | === Linux === | ||
As of {{revision|5.0-11484}}, 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 49: | Line 50: | ||
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 most controllers by selecting the corresponding <code>evdev/x/xxxx</code> entry on the Devices drop-down menu, thanks to the Linux evdev API natively exposing motion axes. | |||
=== Emulated pointer === | === Emulated pointer === | ||