XInput Wrapper for DS3 and Play.com USB Dual DS2 Controller
(06-22-2015, 03:19 PM)SuperSteef Wrote: Anyone else running the preview version of Windows 10?

I've been having trouble getting the BT driver to install on Windows 10, presumably because it uses the 'default' install option. Win10 is closer to 7/8 and the drivers from 7 appear to work just fine on 10 for everything else I've used so far. Even force installing didn't work.

I was going through the thread for the past few pages but didn't see anyone posting any replies to Win10 questions. I also couldn't find any type of config file that determined what install method should be used for the driver, so I'm guessing that is hardcoded into the install file. If Win10 could be added to that, to use Win7/8 drivers, that'd be great.

EDIT: It works fine wired and I had it working via BT on Win7.

Thanks!

I am having this same issue, except when I restart Windows everything goes back to the default drivers and I have to reinstall the drivers to use the controller wired.


-Edit-
I got it to work and this is what I did.
I have not done a restart yet to see if this stays.
It is not recommended to leave these settings this way, I am leaving them like this for testing purposes only.
Right click my computer go to properties.
Go to advanced system settings.
Click on the hardware tab.
Open device installation settings.
Check the box that says "No, let me choose what to do."
Check the box that says "Never install driver software from Windows Update."
If checked un check the box that says "Automatically get the device app and info provided by your device manufacturer"
Locate your SCPDriver.exe right click run as administrator.
If drivers were previously installed uninstall them.
Check the box marked Force Install.
Click install and test.

Sponsored links

Ok so I have been playing with pcsx2 for a while and have been using Scarlet Crush for my DS3 controller the whole time. It worked perfectly (besides when I would have to remap the buttons every time I closed pcsx2).
But I didn't play for a while once and the controller didn't work with Scarlet Crush so I had to redo all of the installing and what not and it worked perfectly once again after that. But after not playing for a while again, the controller stopped working with Scarlet Crush.
The controller doesn't show up as devices on the device manager, it shows up as "unspecified". Also, I tried uninstalling and reinstalling Scarlet Crush several times. I deleted the xbox360 drivers and reinstalled them again, but didn't help.
The controller will react when i install Scarlet Crush but the LEDs will just flash and not connect to the computer.
Also I tried changing the usbs I was using everytime to see if there would be a differnce between USB 3.0 or not.
Need help, I just want to play Silent Hill 2 Sad
ok, this is driving me nuts. I've got everything installed, copied the xinput1_3.dll file over, but native mode is still grayed out. Any ideas?

Windows 8.1 x64
(06-23-2015, 11:16 AM)CRACING Wrote: Hello,

Check the attachment named ScpControl_00-F8-94.zip. Its for you and contains modified ScpControl.dll. Replace the existing ScpControl.dll in SCP program folder to the edited ScpControl.dll. Once replaced, restart the scp ds3 service in services. Run ScpMonitor. Connect your controller to USB, make sure its turned ON and wait few seconds before unplugging. Once you unplug wait until those four blinking leds convert to one stable led or if all goes off, then something else is wrong.

Thanks...
Best Regards

Thanks for the reply CRACING.

I tried the ScpControl.dll you had provided and had the same results unfortunately (fast blinking for a few seconds followed with no LEDs). After trying that three times I stopped to check ScpService.log:

Code:
2015-06-23 23:31:07.878 -- Device Removal [00:F8:94:65:63:25]
2015-06-23 23:31:07.882 -- USB Device : HID_Worker_Thread Exiting
2015-06-23 23:31:12.844 >> HCI_Connection_Request_EV [04]
2015-06-23 23:31:12.847 << HCI_Delete_Stored_Link_Key [0C12]
2015-06-23 23:31:12.850 << HCI_Remote_Name_Request [0419]
2015-06-23 23:31:12.853 >> HCI_Command_Complete_EV [0E] [00] [HCI_Delete_Stored_Link_Key]
2015-06-23 23:31:12.857 >> HCI_Command_Status_EV [0F] [00] [HCI_Remote_Name_Request]
2015-06-23 23:31:12.948 >> HCI_Remote_Name_Request_Complete_EV [07]
2015-06-23 23:31:12.950 -- Remote Name : 00:F8:94:65:63:25 - PLAYSTATION(R)3Conteroller-PANHAI
2015-06-23 23:31:12.953 << HCI_Accept_Connection_Request [0409]
2015-06-23 23:31:12.957 >> HCI_Command_Status_EV [0F] [00] [HCI_Null]
2015-06-23 23:31:12.961 >> HCI_Command_Status_EV [0F] [00] [HCI_Accept_Connection_Request]
2015-06-23 23:31:13.259 >> HCI_Role_Change_EV [12]
2015-06-23 23:31:13.264 >> HCI_Connection_Complete_EV [03]
2015-06-23 23:31:13.287 >> L2CAP_Connection_Request [02] PSM [11]
2015-06-23 23:31:13.292 << L2CAP_Connection_Response [03]
2015-06-23 23:31:13.295 << L2CAP_Configuration_Request [04]
2015-06-23 23:31:13.301 >> L2CAP_Configuration_Request [04]
2015-06-23 23:31:13.304 << L2CAP_Configuration_Response [05]
2015-06-23 23:31:13.307 >> L2CAP_Configuration_Response [05]
2015-06-23 23:31:17.969 >> HCI_Connection_Request_EV [04]
2015-06-23 23:31:17.972 << HCI_Delete_Stored_Link_Key [0C12]
2015-06-23 23:31:17.975 << HCI_Remote_Name_Request [0419]
2015-06-23 23:31:17.982 >> HCI_Command_Complete_EV [0E] [00] [HCI_Delete_Stored_Link_Key]
2015-06-23 23:31:17.985 >> HCI_Command_Status_EV [0F] [00] [HCI_Remote_Name_Request]
2015-06-23 23:31:23.048 >> HCI_Remote_Name_Request_Complete_EV [07]
2015-06-23 23:31:23.052 -- Remote Name : 00:F8:94:65:63:25 -
2015-06-23 23:31:23.054 << HCI_Reject_Connection_Request [040A]
2015-06-23 23:31:23.058 >> HCI_Command_Status_EV [0F] [00] [HCI_Null]
2015-06-23 23:31:23.060 >> HCI_Command_Status_EV [0F] [02] [HCI_Reject_Connection_Request]
2015-06-23 23:31:33.317 >> HCI_Disconnection_Complete_EV [05]

At this point, I wasn't certain the Bluetooth Dongle was working correctly. I grabbed my laptop and did a fresh install to see if I could go farther with the modified .dll on a different bluetooth adapter (I made sure to disconnect the first bluetooth adapter to avoid problems pairing with this one):

Code:
2015-06-23 19:04:10.749 >> HCI_Connection_Request_EV [04]
2015-06-23 19:04:10.759 << HCI_Delete_Stored_Link_Key [0C12]
2015-06-23 19:04:10.783 << HCI_Remote_Name_Request [0419]
2015-06-23 19:04:10.803 >> HCI_Command_Complete_EV [0E] [00] [HCI_Delete_Stored_Link_Key]
2015-06-23 19:04:10.825 >> HCI_Command_Status_EV [0F] [00] [HCI_Remote_Name_Request]
2015-06-23 19:04:10.863 >> HCI_Remote_Name_Request_Complete_EV [07]
2015-06-23 19:04:10.871 -- Remote Name : 00:F8:94:65:63:25 - PLAYSTATION(R)3Conteroller-PANHAI
2015-06-23 19:04:10.881 << HCI_Accept_Connection_Request [0409]
2015-06-23 19:04:10.901 >> HCI_Command_Status_EV [0F] [00] [HCI_Accept_Connection_Request]
2015-06-23 19:04:11.038 >> HCI_Role_Change_EV [12]
2015-06-23 19:04:11.187 >> HCI_Connection_Complete_EV [03]
2015-06-23 19:04:11.215 >> HCI_Max_Slots_Change_EV [1B]
2015-06-23 19:04:11.231 >> L2CAP_Connection_Request [02] PSM [11]
2015-06-23 19:04:11.249 << L2CAP_Connection_Response [03]
2015-06-23 19:04:11.269 << L2CAP_Configuration_Request [04]
2015-06-23 19:04:11.293 >> L2CAP_Configuration_Request [04]
2015-06-23 19:04:11.319 << L2CAP_Configuration_Response [05]
2015-06-23 19:04:11.341 >> L2CAP_Configuration_Response [05]
2015-06-23 19:04:32.087 >> HCI_Disconnection_Complete_EV [05]

This one has a different response. It apparently stopped on >> L2CAP_Configuration_Response [05] and then timed out.

I've been messing with the source code myself and trying different authentication identifiers without luck. I also tried the service bypass here to see if the bypass would work but it provides the same logs as above.

I'm going to try reading through more of the code to see if there's a reason why the bypass isn't kicking in. If you have any other ideas, I would be more than welcome to see if they work.
(06-24-2015, 04:48 AM)Khevarash Wrote: Thanks for the reply CRACING.

I tried the ScpControl.dll you had provided and had the same results unfortunately (fast blinking for a few seconds followed with no LEDs).

Damn, I thought it would work. Sad

(06-24-2015, 04:48 AM)Khevarash Wrote: After trying that three times I stopped to check ScpService.log:

Code:
2015-06-23 23:31:07.878 -- Device Removal [00:F8:94:65:63:25]
2015-06-23 23:31:07.882 -- USB Device : HID_Worker_Thread Exiting
2015-06-23 23:31:12.844 >> HCI_Connection_Request_EV [04]
2015-06-23 23:31:12.847 << HCI_Delete_Stored_Link_Key [0C12]
2015-06-23 23:31:12.850 << HCI_Remote_Name_Request [0419]
2015-06-23 23:31:12.853 >> HCI_Command_Complete_EV [0E] [00] [HCI_Delete_Stored_Link_Key]
2015-06-23 23:31:12.857 >> HCI_Command_Status_EV [0F] [00] [HCI_Remote_Name_Request]
2015-06-23 23:31:12.948 >> HCI_Remote_Name_Request_Complete_EV [07]
2015-06-23 23:31:12.950 -- Remote Name : 00:F8:94:65:63:25 - PLAYSTATION(R)3Conteroller-PANHAI
2015-06-23 23:31:12.953 << HCI_Accept_Connection_Request [0409]
2015-06-23 23:31:12.957 >> HCI_Command_Status_EV [0F] [00] [HCI_Null]
2015-06-23 23:31:12.961 >> HCI_Command_Status_EV [0F] [00] [HCI_Accept_Connection_Request]
2015-06-23 23:31:13.259 >> HCI_Role_Change_EV [12]
2015-06-23 23:31:13.264 >> HCI_Connection_Complete_EV [03]
2015-06-23 23:31:13.287 >> L2CAP_Connection_Request [02] PSM [11]
2015-06-23 23:31:13.292 << L2CAP_Connection_Response [03]
2015-06-23 23:31:13.295 << L2CAP_Configuration_Request [04]
2015-06-23 23:31:13.301 >> L2CAP_Configuration_Request [04]
2015-06-23 23:31:13.304 << L2CAP_Configuration_Response [05]
2015-06-23 23:31:13.307 >> L2CAP_Configuration_Response [05]
2015-06-23 23:31:17.969 >> HCI_Connection_Request_EV [04]
2015-06-23 23:31:17.972 << HCI_Delete_Stored_Link_Key [0C12]
2015-06-23 23:31:17.975 << HCI_Remote_Name_Request [0419]
2015-06-23 23:31:17.982 >> HCI_Command_Complete_EV [0E] [00] [HCI_Delete_Stored_Link_Key]
2015-06-23 23:31:17.985 >> HCI_Command_Status_EV [0F] [00] [HCI_Remote_Name_Request]
2015-06-23 23:31:23.048 >> HCI_Remote_Name_Request_Complete_EV [07]
2015-06-23 23:31:23.052 -- Remote Name : 00:F8:94:65:63:25 -
2015-06-23 23:31:23.054 << HCI_Reject_Connection_Request [040A]
2015-06-23 23:31:23.058 >> HCI_Command_Status_EV [0F] [00] [HCI_Null]
2015-06-23 23:31:23.060 >> HCI_Command_Status_EV [0F] [02] [HCI_Reject_Connection_Request]
2015-06-23 23:31:33.317 >> HCI_Disconnection_Complete_EV [05]

At this point, I wasn't certain the Bluetooth Dongle was working correctly.

HCI_Connection_Request_EV [04] is started again after L2CAP_Configuration_Response [05], instead of connecting to controller. Also next lines show negative response for connections. Could be Bluetooth Dongle's related issue.

(06-24-2015, 04:48 AM)Khevarash Wrote: I grabbed my laptop and did a fresh install to see if I could go farther with the modified .dll on a different bluetooth adapter (I made sure to disconnect the first bluetooth adapter to avoid problems pairing with this one):

Code:
2015-06-23 19:04:10.749 >> HCI_Connection_Request_EV [04]
2015-06-23 19:04:10.759 << HCI_Delete_Stored_Link_Key [0C12]
2015-06-23 19:04:10.783 << HCI_Remote_Name_Request [0419]
2015-06-23 19:04:10.803 >> HCI_Command_Complete_EV [0E] [00] [HCI_Delete_Stored_Link_Key]
2015-06-23 19:04:10.825 >> HCI_Command_Status_EV [0F] [00] [HCI_Remote_Name_Request]
2015-06-23 19:04:10.863 >> HCI_Remote_Name_Request_Complete_EV [07]
2015-06-23 19:04:10.871 -- Remote Name : 00:F8:94:65:63:25 - PLAYSTATION(R)3Conteroller-PANHAI
2015-06-23 19:04:10.881 << HCI_Accept_Connection_Request [0409]
2015-06-23 19:04:10.901 >> HCI_Command_Status_EV [0F] [00] [HCI_Accept_Connection_Request]
2015-06-23 19:04:11.038 >> HCI_Role_Change_EV [12]
2015-06-23 19:04:11.187 >> HCI_Connection_Complete_EV [03]
2015-06-23 19:04:11.215 >> HCI_Max_Slots_Change_EV [1B]
2015-06-23 19:04:11.231 >> L2CAP_Connection_Request [02] PSM [11]
2015-06-23 19:04:11.249 << L2CAP_Connection_Response [03]
2015-06-23 19:04:11.269 << L2CAP_Configuration_Request [04]
2015-06-23 19:04:11.293 >> L2CAP_Configuration_Request [04]
2015-06-23 19:04:11.319 << L2CAP_Configuration_Response [05]
2015-06-23 19:04:11.341 >> L2CAP_Configuration_Response [05]
2015-06-23 19:04:32.087 >> HCI_Disconnection_Complete_EV [05]

This one has a different response. It apparently stopped on >> L2CAP_Configuration_Response [05] and then timed out.

This is the same thing I faced when I first got my controller. Later I modified the ScpControl dll to match my controller mac address and the controller was successfully connected. I did the same for you but strange to know it didn't worked.

However, mine isn't a PANHAI controller but "PANHAI" is mentioned in ScpControl dll for connection.

This is the log of successful connection of ds3 controller via BTH:

   

(06-24-2015, 04:48 AM)Khevarash Wrote: I've been messing with the source code myself and trying different authentication identifiers without luck. I also tried the service bypass here to see if the bypass would work but it provides the same logs as above.

I'm going to try reading through more of the code to see if there's a reason why the bypass isn't kicking in. If you have any other ideas, I would be more than welcome to see if they work.

No idea about bypass nor I have done such to get my controller working. All I have used is latest version ScpControl dll source to modify. Apart from mac address in BthDongle.cs and BthDs3.cs, nothing else I have changed.

Some times, the controller doesn't connect via BTH and leds just go off but you have to try again. Plug again to USB, Turn ON the DS3, Wait few Sec and unplug.

You can also try using ScpServer program until you get the controller working and it shows live log report for easy debugging. However, you have stop scp ds3 service before running ScpServer otherwise it will conflict.

Thanks...
Best Regards
How to modify ScpControl.dll to make fake DS3 controller working through Bluetooh
(This trick doesn't work for all fake controllers including those that show "Remote [00:00:00:00:00:00]" in log.
Hello, noob to this software: I downloaded the program I have ran it successfully on my Windows 8.1 Laptop, but I can't get ScpDriver.exe to run on my Windows 10 Desktop - is there a workaround for this?
(06-24-2015, 09:31 PM)Krutonium Wrote: Hello, noob to this software: I downloaded the program I have ran it successfully on my Windows 8.1 Laptop, but I can't get ScpDriver.exe to run on my Windows 10 Desktop - is there a workaround for this?
5 posts up
http://forums.pcsx2.net/Thread-XInput-Wr...#pid465718
Not quite my issue, the program won't launch at all - as in zilch, nada.
(06-24-2015, 11:05 PM)Krutonium Wrote: Not quite my issue, the program won't launch at all - as in zilch, nada.

Just to make sure: you unblocked the archives before extracting them, right? Make sure you have at least .NET 4.0 and 2013 C++ Redistributable.
(06-25-2015, 12:15 AM)Khevarash Wrote: Just to make sure: you unblocked the archives before extracting them, right? Make sure you have at least .NET 4.0 and 2013 C++ Redistributable.

Yes to all.




Users browsing this thread: 10 Guest(s)