XInput Wrapper for DS3 and Play.com USB Dual DS2 Controller

[Virtu]

Greetings, everyone!
Firstly, I'm really glad Scarlet.Crush released this since MotionInJoy is annoying. Thank you very much! (:

So far I've got USB to work flawlessly with my DS3 (which I'm positive is genuine), but bluetooth is giving me headaches. I've skimmed through many pages of this topic and followed many suggestions provided by the users, all to no avail. I'm thinking my BT dongle might be the problem, since it's a cheap, generic one, even though it has worked with MotionInJoy before.

My issue is I can't seem to establish a bluetooth connection (DS3 LEDs keep flashing rapidly) and Pad 1 only shows "Reserved" next to the saved MAC address. HCI and LMP versions are both 3.07A6.

I'm running SCP 1.1.0.138, fully uninstalled MotionInJoy, and tried disabling SSP, reinstalling drivers (even with Force Install ticked), manually adding my dongle's ID to BthWinUsb.inf, rebooting several times, installing the driver through Zadig, pinhole resetting the controller and nothing worked. (Additionally, everytime I restart the computer, the Host Address field in SCPMonitor shows "Disconnected" until I manually start the SCP Service. But that's really minor, I'm just mentioning it to make sure I didn't do anything wrong)

Finally, I've followed Scarlet.Crush's instructions to generate a fresh ScpService log after reboot and this is the result:

Code:

2014-01-19 19:04:36.646 ++ C:\Program Files\Scarlet.Crush Productions\bin\ScpService.exe 1.1.0.136
2014-01-19 19:04:36.661 ++ C:\Program Files\Scarlet.Crush Productions\bin\ScpControl.dll 1.1.0.138
2014-01-19 19:04:36.768 ++ Microsoft Windows 7 Ultimate Service Pack 1 (6.1.7601.65536 AMD64)
2014-01-19 19:04:36.813 -- Controller : UDP_Worker_Thread Starting
2014-01-19 19:04:36.815 -- Bluetooth  : L2CAP_Worker_Thread Starting [82,02]
2014-01-19 19:04:36.823 -- Bluetooth  : HCI_Worker_Thread Starting [81]
2014-01-19 19:04:36.826 << HCI_Reset [0C03]
2014-01-19 19:04:36.952 >> HCI_Command_Complete_EV [0E] [00] [HCI_Reset]
2014-01-19 19:04:37.204 << HCI_Read_BD_ADDR [1009]
2014-01-19 19:04:37.206 >> HCI_Command_Complete_EV [0E] [00] [HCI_Read_BD_ADDR]
2014-01-19 19:04:37.209 << HCI_Read_Buffer_Size [1005]
2014-01-19 19:04:37.210 >> HCI_Command_Complete_EV [0E] [00] [HCI_Read_Buffer_Size]
2014-01-19 19:04:37.210 -- 0180, 40, 0008, 0008
2014-01-19 19:04:37.212 << HCI_Read_Local_Version_Info [1001]
2014-01-19 19:04:37.214 >> HCI_Command_Complete_EV [0E] [00] [HCI_Read_Local_Version_Info]
2014-01-19 19:04:37.216 -- Master 00:15:83:3D:0A:57, HCI_Version 3.07A6, LMP_Version 3.07A6
2014-01-19 19:04:37.220 << HCI_Write_Scan_Enable [0C1A]
2014-01-19 19:04:37.222 >> HCI_Command_Complete_EV [0E] [00] [HCI_Write_Scan_Enable]
2014-01-19 19:05:02.115 ++ Notify [Arrival] [{E2824A09-DBAA-4407-85CA-C8E8FF5F6FFA}] [\\?\USB#VID_054C&PID_0268#6&38A36D0C&0&1#{E2824A09-DBAA-4407-85CA-C8E8FF5F6FFA}]
2014-01-19 19:05:02.116 -- DS3 Arrival Event
2014-01-19 19:05:02.127 -- Device Arrival [00:26:5C:49:0F:05]
2014-01-19 19:05:02.138 -- USB Device : HID_Worker_Thread Starting
2014-01-19 19:05:02.139 -- Started Device Instance [USB\VID_054C&PID_0268\6&38A36D0C&0&1] Local [00:26:5C:49:0F:05] Remote [D8:90:E8:A5:67:D6]
2014-01-19 19:05:02.142 ++ Paired DS3 [00:26:5C:49:0F:05] To BTH Dongle [00:15:83:3D:0A:57]
2014-01-19 19:07:00.224 ++ Notify [Removal] [{E2824A09-DBAA-4407-85CA-C8E8FF5F6FFA}] [\\?\USB#VID_054C&PID_0268#6&38A36D0C&0&1#{E2824A09-DBAA-4407-85CA-C8E8FF5F6FFA}]
2014-01-19 19:07:00.224 -- Device Removal [00:26:5C:49:0F:05]
2014-01-19 19:07:00.224 -- USB Device : HID_Worker_Thread Exiting
2014-01-19 19:07:03.211 >> HCI_Connection_Request_EV [04]
2014-01-19 19:07:03.215 << HCI_Read_Stored_Link_Key [0C0D]
2014-01-19 19:07:03.219 << HCI_Remote_Name_Request [0419]
2014-01-19 19:07:03.220 >> HCI_Command_Complete_EV [0E] [00] [HCI_Read_Stored_Link_Key]
2014-01-19 19:07:03.221 >> HCI_Command_Status_EV [0F] [00] [HCI_Remote_Name_Request]
2014-01-19 19:07:03.259 >> HCI_Remote_Name_Request_Complete_EV [07]
2014-01-19 19:07:03.259 -- Remote Name : 00:26:5C:49:0F:05 - PLAYSTATION(R)3 Controller
2014-01-19 19:07:03.263 << HCI_Accept_Connection_Request [0409]
2014-01-19 19:07:03.264 >> HCI_Command_Status_EV [0F] [00] [HCI_Accept_Connection_Request]
2014-01-19 19:07:03.427 >> HCI_Role_Change_EV [12]
2014-01-19 19:07:03.451 >> HCI_Connection_Complete_EV [03]
2014-01-19 19:07:03.462 >> HCI_Page_Scan_Repetition_Mode_Change_EV [20]
2014-01-19 19:07:03.467 >> HCI_Max_Slots_Change_EV [1B]
2014-01-19 19:07:03.496 >> L2CAP_Connection_Request [02] PSM [11]
2014-01-19 19:07:03.502 << L2CAP_Connection_Response [03]
2014-01-19 19:07:03.504 << L2CAP_Configuration_Request [04]
2014-01-19 19:07:03.533 >> L2CAP_Configuration_Request [04]
2014-01-19 19:07:03.537 << L2CAP_Configuration_Response [05]
2014-01-19 19:07:03.538 >> L2CAP_Configuration_Response [05]
2014-01-19 19:07:03.552 >> L2CAP_Connection_Request [02] PSM [13]
2014-01-19 19:07:03.553 << L2CAP_Connection_Response [03]
2014-01-19 19:07:03.554 << L2CAP_Configuration_Request [04]
2014-01-19 19:07:03.572 >> L2CAP_Configuration_Request [04]
2014-01-19 19:07:03.573 << L2CAP_Configuration_Response [05]
2014-01-19 19:07:03.576 >> L2CAP_Configuration_Response [05]
2014-01-19 19:07:03.577 << L2CAP_Connection_Request [02] PSM [01]
2014-01-19 19:07:49.112 >> HCI_Disconnection_Complete_EV [05]

Apparently it never gets past L2CAP_Configuration_Response. :x
Has anyone faced a similar issue and was able to solve it? If so, how?
Any help would be greatly appreciated! If ScpDriver.log is needed I can post it here as well, but it's quite cluttered due to my (many) attempts to reinstall the drivers to see if that would solve my problem.

Thanks a ton once again!!

[emisca]

it does what my fake dualshock does..
Please note mac address, it starts with 00:26:5C. So it could be fake.
Try using the same old version as me (se my older post) and tell us if it works!

+1 cent to my opinion.. scp-ds3 should integrate that fake ds3 fix....

see http://forums.pcsx2.net/Thread-XInput-Wr...#pid343056

[Rickhtoo]

it does what my fake dualshock does..
Please note mac address, it starts with 00:26:5C. So it could be fake.
Try using the same old version as me (se my older post) and tell us if it works!

+1 cent to my opinion.. scp-ds3 should integrate that fake ds3 fix....

see http://forums.pcsx2.net/Thread-XInput-Wr...#pid343056

It's interesting to note though, that 'Controller' is actually spelled correctly, and it does not have 'ghic' at the end of the line. Not sure if that makes a difference or not.. Also, there is no smiley face in the address as many fake ones show in translation.

[Virtu]

it does what my fake dualshock does..
Please note mac address, it starts with 00:26:5C. So it could be fake.
Try using the same old version as me (se my older post) and tell us if it works!

+1 cent to my opinion.. scp-ds3 should integrate that fake ds3 fix....

see http://forums.pcsx2.net/Thread-XInput-Wr...#pid343056

Oh my goodness that actually worked! Uninstalled drivers from latest version (not sure if needed), installed 1.0.0.103 with Nashi's DLL, booted up ScpMonitor and upon disconnection BT works like a charm. No lag at all.

Bothers me a bit that I paid full price for a fake controller but hey, it looks and feels just like a genuine one, and I've been using it for a long while. Now that I've got this working I can gladly ditch MotionInJoy for good and that alone is worth it.

Thanks!

[Foxhound4444]

Having a problem with the DS4 again. BT is still a little laggy but the connection is there to the controller. However, the computer doesn't recognize the controller when plugged via USB. The controller charges but the controller is still connected via BT so the lag issues are still there when the controller is not right next to the BT adapter on the computer (or pointed towards it). Why doesn't the DS4 play off of the USB when connected to the USB rather than BT? Anyone else having this issue?

[emisca]

Bothers me a bit that I paid full price for a fake controller but hey, it looks and feels just like a genuine one, and I've been using it for a long while. Now that I've got this working I can gladly ditch MotionInJoy for good and that alone is worth it.

Thanks!

I'm not an expert, but I start thinking that those 00:26:5C ds3 could be only an old revision, and fake ones are a clone of them...

[Scarlet.Crush]

@Foxhound4444: I think there is a DS4 issue with some USB ports.

On my games machine I have 2 front panel USB3.0 ports, rear panel ports are 2 USB3.0 & 6 USB2.0 ports. I use a 3m USB cable for my DS4, normally connected to a rear panel port. Front panel ports usually have my iPhone USB cable and a USB HDD attached.

I bought a 2nd DS4 & 3m USB cable - I plugged it in to one of the front panel ports to get it set up and charged. Windows didn't recognise anything connected on the port, but the LightBar was glowing Yellow showing that it was charging.

First thought was that the USB cable was dodgy - swapped it for my known good cable, no change. Then thought dodgy DS4 - plugged it in to a rear panel port, recognised by Windows immediately.

I verified that it wasn't a faulty port by testing it with iPhone, USB HDD, USB Stick, DS3 & PSP - all worked perfectly.

Both DS4s work perfectly on all my rear panel ports (USB2.0 & USB3.0), but neither is recognised as being attached by Windows on the front panel ports. Since all my other USB devices work on these front panel ports, the conclusion has to be that the DS4s are somewhat sensitive to something about these ports.

[geop0p3]

I'm having host adress error in the monitor....
I have USB\VID_0A12&PID_0001&REV_1915 bluetooth dongle

Code:

SUCCESS - Virtual Bus Created
INFO    - ENTER:  DriverPackageInstallW
INFO    - Looking for Model Section [SCProductions.NTamd64]...
INFO    - Installing INF file 'C:\Program Files\Scarlet.Crush Productions\bin\System\ScpVBus.inf' (Plug and Play).
INFO    - Looking for Model Section [SCProductions.NTamd64]...
INFO    - Installing devices with Id "root\ScpVBus" using INF "C:\Windows\System32\DriverStore\FileRepository\scpvbus.inf_amd64_21ca245c0e23d7a5\scpvbus.inf".
INFO    - Will force install because driver is not better and force flag is set.
INFO    - ENTER UpdateDriverForPlugAndPlayDevices...
SUCCESS - RETURN UpdateDriverForPlugAndPlayDevices.
INFO    - Installation was successful.
SUCCESS - Install completed
INFO    - RETURN: DriverPackageInstallW  (0x0)
INFO    - ENTER:  DriverPackageInstallW
INFO    - Looking for Model Section [SCProductions.NTamd64]...
INFO    - Installing INF file 'C:\Program Files\Scarlet.Crush Productions\bin\System\BthWinUsb.inf' (Plug and Play).
INFO    - Looking for Model Section [SCProductions.NTamd64]...
INFO    - Installing devices with Id "USB\VID_0A12&PID_0001&REV_1915" using INF "C:\Windows\System32\DriverStore\FileRepository\bthwinusb.inf_amd64_bb65126544cdaf87\BthWinUsb.inf".
INFO    - ENTER UpdateDriverForPlugAndPlayDevices...
SUCCESS - RETURN UpdateDriverForPlugAndPlayDevices.
INFO    - Installation was successful.
INFO    - Marked Phantom Device with Hardware/Compatible Id 'USB\VID_0A12&PID_0001&REV_1915' for reinstall on next plug-in.
INFO    - Marked Phantom Device with Hardware/Compatible Id 'USB\VID_0A12&PID_0001&REV_1915' for reinstall on next plug-in.
INFO    - Marked Phantom Device with Hardware/Compatible Id 'USB\VID_0A12&PID_0001&REV_1915' for reinstall on next plug-in.
INFO    - Marked Phantom Device with Hardware/Compatible Id 'USB\VID_0A12&PID_0001&REV_1915' for reinstall on next plug-in.
INFO    - Marked Phantom Device with Hardware/Compatible Id 'USB\VID_0A12&PID_0001&REV_1915' for reinstall on next plug-in.
INFO    - Marked Phantom Device with Hardware/Compatible Id 'USB\VID_0A12&PID_0001&REV_1915' for reinstall on next plug-in.
INFO    - Marked Phantom Device with Hardware/Compatible Id 'USB\VID_0A12&PID_0001&REV_1915' for reinstall on next plug-in.
INFO    - Phantom Device with Hardware/Compatible Id 'USB\VID_0A12&PID_0001&REV_1915' already has 'C:\Windows\System32\DriverStore\FileRepository\bthwinusb.inf_amd64_bb65126544cdaf87\BthWinUsb.inf' installed on it.
INFO    - Marked Phantom Device with Hardware/Compatible Id 'USB\VID_0A12&PID_0001&REV_1915' for reinstall on next plug-in.
INFO    - Marked Phantom Device with Hardware/Compatible Id 'USB\VID_0A12&PID_0001&REV_1915' for reinstall on next plug-in.
INFO    - Phantom Device with Hardware/Compatible Id 'USB\VID_0A12&PID_0001&REV_1915' already has 'C:\Windows\System32\DriverStore\FileRepository\bthwinusb.inf_amd64_bb65126544cdaf87\BthWinUsb.inf' installed on it.
SUCCESS - Install completed
INFO    - RETURN: DriverPackageInstallW  (0x0)
INFO    - ENTER:  DriverPackageInstallW
INFO    - Looking for Model Section [SCProductions.NTamd64]...
INFO    - Installing INF file 'C:\Program Files\Scarlet.Crush Productions\bin\System\Ds3WinUsb.inf' (Plug and Play).
INFO    - Looking for Model Section [SCProductions.NTamd64]...
INFO    - Installing devices with Id "USB\VID_054C&PID_0268&REV_0100" using INF "C:\Windows\System32\DriverStore\FileRepository\ds3winusb.inf_amd64_15691982ca5c21ae\Ds3WinUsb.inf".
INFO    - ENTER UpdateDriverForPlugAndPlayDevices...
SUCCESS - RETURN UpdateDriverForPlugAndPlayDevices.
INFO    - Installation was successful.
INFO    - Marked Phantom Device with Hardware/Compatible Id 'USB\VID_054C&PID_0268&REV_0100' for reinstall on next plug-in.
INFO    - Marked Phantom Device with Hardware/Compatible Id 'USB\VID_054C&PID_0268&REV_0100' for reinstall on next plug-in.
INFO    - Marked Phantom Device with Hardware/Compatible Id 'USB\VID_054C&PID_0268&REV_0100' for reinstall on next plug-in.
INFO    - Marked Phantom Device with Hardware/Compatible Id 'USB\VID_054C&PID_0268&REV_0100' for reinstall on next plug-in.
INFO    - Marked Phantom Device with Hardware/Compatible Id 'USB\VID_054C&PID_0268&REV_0100' for reinstall on next plug-in.
INFO    - Phantom Device with Hardware/Compatible Id 'USB\VID_054C&PID_0268&REV_0100' already has 'C:\Windows\System32\DriverStore\FileRepository\ds3winusb.inf_amd64_15691982ca5c21ae\Ds3WinUsb.inf' installed on it.
SUCCESS - Install completed
INFO    - RETURN: DriverPackageInstallW  (0x0)
INFO    - SCP DS3 Service Started.

Install Succeeded.

-- Install Summary --
SCP DS3 Service
Bus Device
Bus Driver
DS3 USB Driver
Bluetooth Driver

[Scarlet.Crush]

@geop0p3:

1. Run ScpMonitor.
2. Right-click on the Icon in the Task bar, select Configuration.
3. Check the "Disable SSP" box.
4. Click OK.
5. Restart your PC.

[cplusplus]

So, I'm having some trouble.

I'm attempting to connect multiple DS3 controllers.

It seems that when I do so however, 2 controllers show up under Control Panel > Hardware and Sound > Devices and Printers, but both controllers are registered to the first controller I connect.

The instructions on the first page say, "Make sure DS3(s) and bluetooth dongle are connected before installing."

Do I need to have all controllers connected via USB before pressing install? Or can I add more later? What if I only have one USB? Am I SOL until I purchase another?