15,189
edits
(→DSU Server Applications: new server for Android and iOS) |
(→Motion sensors: mention SDL, minor rewording) |
||
Line 67: | Line 67: | ||
=== Motion sensors === | === Motion sensors === | ||
The configuration of motion sensors are mostly used on the "Motion Input" tab (since {{revision|5.0-11083}}) and on "Extension Motion Input" tab (since {{revision|5.0-11478}}, visible only when Nunchuk is the currently selected extension) of Emulated Wii Remotes, although nothing prevents you from binding the motion sensor | The configuration of motion sensors are mostly used on the "Motion Input" tab (since {{revision|5.0-11083}}) and on "Extension Motion Input" tab (since {{revision|5.0-11478}}, visible only when Nunchuk is the currently selected extension) of Emulated Wii Remotes, although nothing prevents you from binding the motion sensor axles in other places as well. By default, the Accelerometer and Gyroscope bindings of the "Motion Input" tab should be already populated with the matching axles from the DSU Server. | ||
If they are blank (e.g. the current controller configuration was created by an older Dolphin version), you can manually assign the corresponding motion | If they are blank (e.g. the current controller configuration was created by an older Dolphin version), you can manually assign the corresponding motion axles 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). | ||
Alternatively, you can completely skip the setup of a DSU Server/Client and directly assign the motion sensor axles of most controllers by selecting the corresponding <code>evdev/x/xxxx</code> entry on the Devices drop-down menu on Linux (or <code>SDL/x/xxxx</code> on Windows and macOS), thanks to the evdev and SDL APIs natively exposing motion axles. | |||
=== Emulated pointer === | === Emulated pointer === |