So far, ScpToolkit is the only real and effective solution for using Sony DualShock 3/4 controllers (including the fake ones) to play console emulator games on Windows computers. Finally, its installation is fairly simple and straightforward, but does require a few things as stated in the “System Requirements” section.
In addition to being able to better match and connect the gamepad to Windows, support vibration and six-axis sensing, provide keystroke operation schemes, allow custom keystrokes, support Windows Vista and higher, and be perfectly compatible with various Bluetooth modules and DS3/DS4 gamepads, ScpToolkit also allows user to set various parameters/properties of the PS3/4 controller for better control of gamepad. Simply speaking, this tool enables you to connect the PS 3/4 controller to your computer via Bluetooth or USB cable (mainly to play various video games via console emulators).
Launch the DevManView.exe executable (you'll be prompted to give administrative consent)Įxample of some ScpToolkit v1.7.ScpToolkit is a free and universal gamepad driver and XInput wrapper software specially developed for Sony DualShock 3/4 controllers on Windows, whether they are official or fake ones.Get the free tool DevManView from Nir Sofer (download link at the bottom of the page).Not sure if everything's cleaned up like it should? Devices still not showing up normally or behaving funny? How about this: Same deal here right-click, select Uninstall and confirm: Locate the device named Scp Virtual Bus Driver: While still in Device Manager, expand the System devices node: Rinse and repeat until the devices won't show up under this node anymore. Then, in Device Manager go through the same "right-click, Uninstall" procedure: In Driver Store Explorer, things will pop up slightly different, nevertheless select and force removal:
The procedure for 1.7 is very similar to the steps described for 1.6 above, except that the node you'll find the devices under is called Universal Serial Bus devices:
Great! Now there's the Bluetooth dongle back running the default Windows drivers and the controller is under Human Interface Devices where it belongs Remove drivers from v1.7 If you've done well, this is how your devices should pop up as again:
Observe and repeat carefully or you'll be left with unusable devices If your controller or Bluetooth dongle is still showing up in the libusbK node, right-click, uninstall and re-plug until it's gone for good I strongly recommend you re-plug all devices and check if they are still running under the SCP drivers! You might think that you're done now but there's a twist! A copy of the driver can still remain in memory and therefore won't be deleted. Right-click on each of those and select Uninstall:Īlternatively the section and device names may differ, depending on your specific case, like so: Open Device Manager and look for a node titled libusbK USB Devices:Įxpanding said node shall reveal the devices running under SCP's drivers: Sweet! Now we need to instruct Windows to revert the devices to their default drivers. Select those, tick the Force Deletion box on the right and then click Delete Package: The highlighted entries belong to the toolkit installation. You'll be presented with a list of drivers found on your machine: Make sure to run it with administrative permissions! We'll use this to safely remove the driver files from the system. If you don't have enough USB ports just repeat the described steps for each device, plugging it in one after another.ĭownload and run the DriverStore Explorer tool.
Have MSBuild/nmake available in PowerShellįor this procedure to work properly make sure you've got your controller(s) and Bluetooth dongle(s) connected. Virtual Vendor and Product IDs used by NSS drivers SIXAXIS/DualShock 3 native HID Report Descriptor
How to check which architecture I'm runningįix Symbol loading for Kernel Driver minidump analysis Amazon's Choice "Pro Controller" CompatibilityĬORSAIR GLAIVE RGB native HID Report Descriptor