Using DualShock 3 controller
On Windows
Currently there are 2 methods of setting up your DualShock 3 (and SIXAXIS) to RPCS3:
- Using RPCS3's dedicated DualShock 3 pad handler by installing the official DualShock 3 driver from Sony (through PlayStation Now). (recommended)
- Using RPCS3's XInput pad handler together with the third-party tool ScpToolkit.
Both approaches have advantages and disadvantages to them as mentioned below:
Method Benefits Drawbacks Using dedicated DualShock 3 pad handler Non-intrusive and simple installation No Bluetooth connectivity Supports motion controls Can be used in combination with other XInput devices in RPCS3 Using XInput pad handler Preferable for users who already have ScpToolkit installed Slightly complex installation instructions Does not work with Nefarious's version of ScpToolkit. Need to use the original version linked below. Bluetooth connectivity present No support for motion controls Currently cannot be used in combination with other XInput devices in RPCS3
Using dedicated DualShock 3 pad handler
The recommended method is to use RPCS3's dedicated DualShock 3 pad handler. This is done by installing the official DualShock 3 driver from Sony and then allowing RPCS3 to handle the controller. While this option lets users take advantage of features such as pressure-sensitive buttons and motion controls, bluetooth functionality will be unavailable. To use RPCS3's dedicated DualShock 3 pad handler:
- Disable all third-party tools accessing the DualShock 3 (such as ScpToolkit).
- Download PlayStation Now for Windows and install it. During the installation process, you will be prompted with an option to install drivers for DualShock controllers. Accept this and install the drivers.
- After completion of all installation, users can uninstall PlayStation Now if they wish to do so. The drivers installed for the DualShock 3 will still remain after such uninstallation.
- Connect the controller using a USB cable and press the PS button (in the middle of the pad) to allow the DualShock 3 to start sending reports to RPCS3.
- Select RPCS3's dedicated DualShock 3 pad handler in the Gamepad Settings menu.
Using XInput pad handler with ScpToolkit
The alternative method is to use the XInput pad handler along with ScpToolkit. This option carries various benefits and drawbacks as mentioned in the table above. To use the XInput pad handler for the DualShock 3:
- Download ScpToolkit v1.2.0.160 along with Update v1.2.2.175.
- Extract ScpToolkit v1.2.0.160 and place the ScpServer folder in the location of your choice.
- Extract Update v1.2.2.175 over ScpServer folder and overwrite all files when prompted.
- Connect your controller to your PC using a USB cable or Bluetooth and let Windows automatically install the generic driver.
- Launch the ScpDriver.exe found in
ScpServer/bin/
and click Install. - Navigate to
ScpServer/bin/Win64/
and launch SCPUser.exe. Test whether the input from your controller is correctly recognised. If the input is not recognised, restart your PC and try again. - Once the input is correctly working, copy the XInput1_3.dll from the same location to your RPCS3 folder and place it next to the rpcs3.exe.
- Select RPCS3's XInput pad handler in the Gamepad Settings menu.
On Linux
The DualShock 3 on Linux works with HIDAPI, allowing for the controller to work through USB as well as Bluetooth. To use the DualShock 3 Backend, users need to create a file called /etc/udev/rules.d/99-ds3-controllers.rules
(you will need root permissions to create this file), and fill it with the following:
# DualShock 3 over USB KERNEL=="hidraw", ATTRS{idVendor}=="054c", ATTRS{idProduct}=="0268", MODE="0666" # DualShock 3 over Bluetooth KERNEL=="hidraw*", KERNELS=="*054C:0268*", MODE="0666"
After this you must either
- restart your computer for these settings to apply or
- run
sudo udevadm control --reload-rules
and replug in your controller
This will allow RPCS3 to communicate with the DualShock 3. Users can then select RPCS3's dedicated DualShock 3 pad handler in the Gamepad Settings menu.
Using DualShock 4 controller
On Windows
The DualShock 4 on Windows works with HIDAPI, allowing for the controller to work through USB as well as Bluetooth. There aren't any additional steps required and the controller should just work with RPCS3's dedicated DualShock 4 pad handler. However, please note that third-party tools like ScpToolkit or DS4Windows may interfere with RPCS3 and it is recommended to disable all such tools.
On Linux
The DualShock 4 on Linux works with HIDAPI, allowing for the controller to work through USB as well as Bluetooth. To use the DualShock 4 Backend, users need to create a file called /etc/udev/rules.d/99-ds4-controllers.rules
(you will need root permissions to create this file), and fill it with the following:
# DualShock 4 over USB KERNEL=="hidraw*", ATTRS{idVendor}=="054c", ATTRS{idProduct}=="05c4", MODE="0666" # DualShock 4 Wireless Adapter over USB KERNEL=="hidraw*", ATTRS{idVendor}=="054c", ATTRS{idProduct}=="0ba0", MODE="0666" # DualShock 4 Slim over USB # KERNEL=="hidraw*", ATTRS{idVendor}=="054c", ATTRS{idProduct}=="09cc", MODE="0666" # DualShock 4 over Bluetooth KERNEL=="hidraw*", KERNELS=="*054C:05C4*", MODE="0666" # DualShock 4 Slim over Bluetooth # KERNEL=="hidraw*", KERNELS=="*054C:09CC*", MODE="0666"
After this you must either
- restart your computer for these settings to apply or
- run
sudo udevadm control --reload-rules
and replug in your controller
This will allow RPCS3 to communicate with the DualShock 4. Users can then select RPCS3's dedicated DualShock 4 pad handler in the Gamepad Settings menu.
Analog sticks not centered with evdev pad handler
When using the evdev pad handler on Linux, some users may encounter cases where the analog sticks of the controller are not centered but stuck in the corner of the movement zone. This issue occurs when incorrect drivers are used for the controller.
Usually, analog sticks have a range from -x
to +x
while triggers use only a positive range from 0
to +x
. However, some controllers use positive ranges for analog sticks as well which does not directly work with RPCS3's implementation. Hence, the following workaround is required:
- Navigate to
~/.config/rpcs3/
and openevdev_positive_axis.yml
. If this file does not exist in the directory, create it. - Change the following lines from false to true:
Before After ABS_X: false ABS_Y: false ABS_RX: false ABS_RY: false
ABS_X: true ABS_Y: true ABS_RX: true ABS_RY: true
This is not an exhaustive list of options available. Users are requested to toggle other options as required by their specific controller or driver.