15,189
edits
DSU Client: Difference between revisions
→Troubleshooting: add common rumble question which is often asked on other communities
No edit summary |
(→Troubleshooting: add common rumble question which is often asked on other communities) |
||
| Line 70: | Line 70: | ||
=== I can't reach the left/right sides of the screen with the emulated pointer === | === I can't reach the left/right sides of the screen with the emulated pointer === | ||
Increasing "Total Yaw" on the Motion Input tab of Emulated Wii Remotes should fix that. Keep in mind there isn't a correct value as the amount of yaw needed for the emulated pointer reach both sides of the screen varies a lot between different games, so finding a value that works with all games is somewhat impossible. | Increasing "Total Yaw" on the Motion Input tab of Emulated Wii Remotes should fix that. Keep in mind there isn't a correct value as the amount of yaw needed for the emulated pointer reach both sides of the screen varies a lot between different games, so finding a value that works with all games is somewhat impossible. | ||
=== My controller has rumble support but I can't map it when using DSU Client === | |||
Since the DSU protocol doesn't carry rumble data, that's expected. Fortunately, most DSU Servers will also assign a virtual XInput device for every real controller connected to them, so you can map the rumble through this virtual device. To do that, right click the "Motor" binding on Emulated GameCube Controller or Emulated Wii Remote settings and select the appropriate XInput device in the dropdown list. | |||
=== I'm using a DualShock 3 controller and button presses only register if I press the buttons hard === | === I'm using a DualShock 3 controller and button presses only register if I press the buttons hard === | ||