DSU Client: Difference between revisions

m
no edit summary
(→‎DSU Server Applications: minor updates, mention SDL support where appropriate)
mNo edit summary
Line 1: Line 1:
Since {{revision|5.0-11083}}, Dolphin can act as a client of the '''[https://v1993.github.io/cemuhook-protocol/ DSU protocol]''' (often referred as ''CemuHook Motion Provider'' protocol), which enables the emulator to receive motion and input data from compatible applications implementing the server-side part of the protocol. Those servers works as a middle-man between specific input devices and client applications like Dolphin in order to provide motion data not accessible through the other input APIs Dolphin supports, like DInput, XInput and SDL, although they also provide data from normal buttons and axes as well.
Since {{revision|5.0-11083}}, Dolphin can act as a client of the '''[https://v1993.github.io/cemuhook-protocol/ DSU protocol]''' (often referred as ''CemuHook Motion Provider'' protocol), which enables the emulator to receive motion and input data from compatible applications implementing the server-side part of the protocol. Those servers works as a middle-man between specific input devices and client applications like Dolphin in order to provide motion data not accessible through the other input APIs Dolphin supports, like DirectInput, XInput and Windows.Gaming.Input, although they also provide data from normal buttons and axes as well.


== DSU Server Applications ==
== DSU Server Applications ==