62
edits
Motion evdev: Difference between revisions
Add notes for the DualSense
(Add dualsense axis based on discussion on discord) |
(Add notes for the DualSense) |
||
| Line 1: | Line 1: | ||
These instruction are made with a Nintendo Pro controller and Joy-Cons. While the overall process will be the same the motion axis may not match those found on a Sony DualShock 4. | These instruction are made with a Nintendo Pro controller and Joy-Cons. While the overall process will be the same the motion axis may not match those found on a Sony DualShock 4 or DualSense. The Sony DualSense also exposes two devices like the Nintendo controllers. | ||
* Recent dolphin version (do not use 5.0 stable!) | * Recent dolphin version (do not use 5.0 stable!) | ||
| Line 5: | Line 5: | ||
* Switch pro or Joy-Con. | * Switch pro or Joy-Con. | ||
The HID Nintendo kernel driver exposes 2 evdev devices, one for the buttons and another (IMU) for the accelerators/gyroscopes. Do note that Joy-Cons will have 2 devices each (4 in total). | The HID Nintendo kernel driver exposes 2 evdev devices, one for the buttons and another (IMU) for the accelerators/gyroscopes. Do note that Joy-Cons will have 2 devices each (4 in total). For the Sony DualSense controller the accelerators/gyroscopes are on the "Wireless Controller Motion Sensors" evdev device. | ||
The IMU input device does not automatically get tagged with `uaccess` while the "regular" device is. If you do not see an IMU device listed in Dolphin's devicelist add the following udev rule to /etc/udev/rules.f/99-hidnintendo.rules. reload udev rules with "udevadm control --reload-rules" and reconnect the device(s). | The IMU input device does not automatically get tagged with `uaccess` while the "regular" device is. If you do not see an IMU device listed in Dolphin's devicelist add the following udev rule to /etc/udev/rules.f/99-hidnintendo.rules. reload udev rules with "udevadm control --reload-rules" and reconnect the device(s). | ||