03-20-2013, 12:30 PM
(This post was last modified: 03-20-2013, 12:32 PM by Scarlet.Crush.)
@KiPhish:
@nTrancer:
added your hardware ids, see Post #301.
USB\VID_0A12&PID_0001 was already included in the list.
@cblair: the .inf file is located at bin\System\Windows 7\ScpDevlo.inf. [The driver files are extracted from ScpFilterDriver.exe when it is run]
@jhun23: 0xB7 => ERROR_ALREADY_EXISTS, Cannot create a file when that file already exists.
@kneecompany: ok, your DS3 is installed and functioning.
Open Devices and Printers, right-click on your PLAYSTATION®3 Controller and select Game controller settings. Click Properties. (see screenshots)
The properties displayed are the DInput properties of the controller. If your game supports DInput, you should be able to configure the pad within the game without any additional changes.
XInput based games require you to drop the XInput Wrapper (bin\Win32\XInput1_3.dll) in to the directory where your game binary is located. There are various versions of the XInput dll which are used by games - XInput9_1_0.dll, XInput1_1.dll, XInput1_2.dll, XInput1_3.dll. So you will have to rename the XInput dll to whatever is required by your game.
Some games perform extra checking on XInput devices and will not work with the supplied XInput Wrapper. This can be alleviated for a few games by using x360ce and one of it's compatibility modes.
These are the limitations of using an XInput Wrapper. I have been working on a set of replacement drivers for DS3s which aim to remove these limitations by presenting DS3s as Native XInput devices (specifically Wired Xbox 360 Controller for Windows devices). The replacement drivers are currently in Beta Phase and are available in Post #301.
Note: I intend to release the next version (Release Candidate) sometime today / tomorrow.
@chrispwnu: can you open Device Manager and verify that the driver is installed correctly on your DS3, and also perform the DInput checks as above.
In Device Manager, double-click DS3 Controller for Windows, select the Driver tab, click Driver Details.
@nTrancer:
added your hardware ids, see Post #301.
USB\VID_0A12&PID_0001 was already included in the list.
@cblair: the .inf file is located at bin\System\Windows 7\ScpDevlo.inf. [The driver files are extracted from ScpFilterDriver.exe when it is run]
@jhun23: 0xB7 => ERROR_ALREADY_EXISTS, Cannot create a file when that file already exists.
@kneecompany: ok, your DS3 is installed and functioning.
Open Devices and Printers, right-click on your PLAYSTATION®3 Controller and select Game controller settings. Click Properties. (see screenshots)
The properties displayed are the DInput properties of the controller. If your game supports DInput, you should be able to configure the pad within the game without any additional changes.
XInput based games require you to drop the XInput Wrapper (bin\Win32\XInput1_3.dll) in to the directory where your game binary is located. There are various versions of the XInput dll which are used by games - XInput9_1_0.dll, XInput1_1.dll, XInput1_2.dll, XInput1_3.dll. So you will have to rename the XInput dll to whatever is required by your game.
Some games perform extra checking on XInput devices and will not work with the supplied XInput Wrapper. This can be alleviated for a few games by using x360ce and one of it's compatibility modes.
These are the limitations of using an XInput Wrapper. I have been working on a set of replacement drivers for DS3s which aim to remove these limitations by presenting DS3s as Native XInput devices (specifically Wired Xbox 360 Controller for Windows devices). The replacement drivers are currently in Beta Phase and are available in Post #301.
Note: I intend to release the next version (Release Candidate) sometime today / tomorrow.
@chrispwnu: can you open Device Manager and verify that the driver is installed correctly on your DS3, and also perform the DInput checks as above.
In Device Manager, double-click DS3 Controller for Windows, select the Driver tab, click Driver Details.