..:: PCSX2 Forums ::..

@dead_pixel: may be a race condition, eg Atheros bootrom not completed before ScpService starts.

Can you set the service to Manual instead of Automatic, and start it when you get the desktop up. [can create a batch file containing: net start "SCP DS3 Service"]

I can look into adding a delayed start if this fixes your issue.

@Scarlet.Crush
Well, I've tried delayed start, even task schedule after Atheros logged events, with no luck. Actually I'm the only one with this problem and heck, hypervisors and VM's made ​​me too lazy. So I'll look into bootlog to see sequence. Will try to debug if this persists then PM you with details . Sorry for vain disturbance.

(02-18-2013, 12:09 PM)Scarlet.Crush Wrote: [ -> ]@zoomHYPERIONzoom: can you run this to get some debug -

1. Plug in your knock-off controller to USB. Disconnect your official DS3.
2. Reboot.
3. Verify in ScpMonitor that Pad 1 is displayed.
4. Unplug the controller.
5. Wait 20secs or so till the LEDs stop flashing.
6. Plug it in to USB again.
7. Wait 20secs.
8. Unplug again.
9. Wait 20secs or so till the LEDs stop flashing.
10. Plug in to USB again.
11. Wait 20secs.
12. Post the ScpService.log as an attachment.

Thanks again. See attached.

EDIT: Apparently the log file is not allowed as an attachment. Here's it's contents:

2/19/2013 4:24:55 PM.723 ++ C:\Program Files\Scarlet.Crush Productions\bin\ScpService.exe 0.7.0.96
2/19/2013 4:24:55 PM.803 ++ C:\Program Files\Scarlet.Crush Productions\bin\ScpControl.dll 0.7.0.96
2/19/2013 4:24:56 PM.013 ++ Microsoft Windows 7 Home Premium Service Pack 1 (6.1.7601.65536 AMD64)
2/19/2013 4:24:56 PM.143 -- USB Device : HID_Worker_Thread Starting
2/19/2013 4:24:56 PM.153 -- Bluetooth : HCI_Worker_Thread Starting
2/19/2013 4:24:56 PM.153 -- Bluetooth : L2CAP_Worker_Thread Starting
2/19/2013 4:24:56 PM.153 << HCI_Reset [0C03]
2/19/2013 4:24:56 PM.193 -- Controller : UDP_Worker_Thread Starting
2/19/2013 4:24:56 PM.223 >> HCI_Command_Complete_EV [0E] [00]
2/19/2013 4:24:56 PM.473 << HCI_Read_BD_ADDR [1009]
2/19/2013 4:24:56 PM.473 >> HCI_Command_Complete_EV [0E] [00]
2/19/2013 4:24:56 PM.473 << HCI_Read_Buffer_Size [1005]
2/19/2013 4:24:56 PM.473 >> HCI_Command_Complete_EV [0E] [00]
2/19/2013 4:24:56 PM.473 -- 01FE, 30, 0008, 000A
2/19/2013 4:24:56 PM.473 << HCI_Read_Local_Version_Info [1001]
2/19/2013 4:24:56 PM.473 >> HCI_Command_Complete_EV [0E] [00]
2/19/2013 4:24:56 PM.473 -- Master 00:11:67:00:0E:FE, HCI_Version 5.4881, LMP_Version 5.4881
2/19/2013 4:24:56 PM.473 << HCI_Write_Scan_Enable [0C1A]
2/19/2013 4:24:56 PM.473 >> HCI_Command_Complete_EV [0E] [00]
2/19/2013 4:40:27 PM.529 ++ Notify [Removal] [{E2824A09-DBAA-4407-85CA-C8E8FF5F6FFA}] [\\?\USB#VID_054C&PID_0268#6&1A8123C&0&6#{E2824A09-DBAA-4407-85CA-C8E8FF5F6FFA}]
2/19/2013 4:40:27 PM.529 -- Device Removal [00:32:00:FE:5F:A1]
2/19/2013 4:40:27 PM.529 -- USB Device : HID_Worker_Thread Exiting
2/19/2013 4:40:29 PM.994 >> HCI_Connection_Request_EV [04]
2/19/2013 4:40:29 PM.994 << HCI_Remote_Name_Request [0419]
2/19/2013 4:40:30 PM.010 >> HCI_Command_Status_EV [0F] [00]
2/19/2013 4:40:30 PM.026 >> HCI_Remote_Name_Request_Complete_EV [07]
2/19/2013 4:40:30 PM.041 -- Remote Name : 00:1E:3DE:36:83 - PLAYSTATION®3Conteroller-ghic
2/19/2013 4:40:30 PM.041 << HCI_Accept_Connection_Request [0409]
2/19/2013 4:40:30 PM.041 >> HCI_Command_Status_EV [0F] [00]
2/19/2013 4:40:30 PM.197 >> HCI_Role_Change_EV [12]
2/19/2013 4:40:30 PM.213 >> HCI_Connection_Complete_EV [03]
2/19/2013 4:40:30 PM.213 >> L2CAP_Connection_Request [02] PSM [11]
2/19/2013 4:40:30 PM.213 << L2CAP_Connection_Response [03]
2/19/2013 4:40:30 PM.213 << L2CAP_Configuration_Request [04]
2/19/2013 4:40:30 PM.244 >> L2CAP_Configuration_Request [04]
2/19/2013 4:40:30 PM.244 << L2CAP_Configuration_Response [05]
2/19/2013 4:40:30 PM.275 >> L2CAP_Configuration_Response [05]
2/19/2013 4:40:30 PM.275 >> L2CAP_Connection_Request [02] PSM [13]
2/19/2013 4:40:30 PM.275 << L2CAP_Connection_Response [03]
2/19/2013 4:40:30 PM.275 << L2CAP_Configuration_Request [04]
2/19/2013 4:40:30 PM.306 >> L2CAP_Configuration_Request [04]
2/19/2013 4:40:30 PM.306 << L2CAP_Configuration_Response [05]
2/19/2013 4:40:30 PM.322 >> L2CAP_Configuration_Response [05]
2/19/2013 4:40:30 PM.322 << L2CAP_Connection_Request [02] PSM [01]
2/19/2013 4:40:30 PM.322 >> L2CAP_Connection_Response [03] [01]
2/19/2013 4:40:30 PM.322 >> L2CAP_Connection_Response [03] [00]
2/19/2013 4:40:30 PM.322 << L2CAP_Configuration_Request [04]
2/19/2013 4:40:30 PM.338 >> L2CAP_Configuration_Response [05]
2/19/2013 4:40:30 PM.338 >> L2CAP_Configuration_Request [04]
2/19/2013 4:40:30 PM.338 << L2CAP_Configuration_Response [05]
2/19/2013 4:41:21 PM.459 >> HCI_Disconnection_Complete_EV [05]
2/19/2013 4:41:47 PM.183 ++ Notify [Arrival] [{E2824A09-DBAA-4407-85CA-C8E8FF5F6FFA}] [\\?\USB#VID_054C&PID_0268#6&1A8123C&0&6#{E2824A09-DBAA-4407-85CA-C8E8FF5F6FFA}]
2/19/2013 4:41:47 PM.183 -- Device Arrival [00:1E:3DE:36:83]
2/19/2013 4:41:47 PM.183 -- USB Device : HID_Worker_Thread Starting
2/19/2013 4:41:47 PM.183 ++ Paired DS3 [00:1E:3DE:36:83] To BTH Dongle [00:11:67:00:0E:FE]
2/19/2013 4:42:33 PM.137 ++ Notify [Removal] [{E2824A09-DBAA-4407-85CA-C8E8FF5F6FFA}] [\\?\USB#VID_054C&PID_0268#6&1A8123C&0&6#{E2824A09-DBAA-4407-85CA-C8E8FF5F6FFA}]
2/19/2013 4:42:33 PM.137 -- Device Removal [00:1E:3DE:36:83]
2/19/2013 4:42:33 PM.137 -- USB Device : HID_Worker_Thread Exiting
2/19/2013 4:42:37 PM.898 >> HCI_Connection_Request_EV [04]
2/19/2013 4:42:37 PM.898 << HCI_Remote_Name_Request [0419]
2/19/2013 4:42:37 PM.898 >> HCI_Command_Status_EV [0F] [00]
2/19/2013 4:42:37 PM.929 >> HCI_Remote_Name_Request_Complete_EV [07]
2/19/2013 4:42:37 PM.929 -- Remote Name : 00:1E:3DE:36:83 - PLAYSTATION®3Conteroller-ghic
2/19/2013 4:42:37 PM.929 << HCI_Accept_Connection_Request [0409]
2/19/2013 4:42:37 PM.929 >> HCI_Command_Status_EV [0F] [00]
2/19/2013 4:42:38 PM.085 >> HCI_Role_Change_EV [12]
2/19/2013 4:42:38 PM.101 >> HCI_Connection_Complete_EV [03]
2/19/2013 4:42:38 PM.101 >> L2CAP_Connection_Request [02] PSM [11]
2/19/2013 4:42:38 PM.101 << L2CAP_Connection_Response [03]
2/19/2013 4:42:38 PM.101 << L2CAP_Configuration_Request [04]
2/19/2013 4:42:38 PM.132 >> L2CAP_Configuration_Request [04]
2/19/2013 4:42:38 PM.132 << L2CAP_Configuration_Response [05]
2/19/2013 4:42:38 PM.163 >> L2CAP_Configuration_Response [05]
2/19/2013 4:42:38 PM.163 >> L2CAP_Connection_Request [02] PSM [13]
2/19/2013 4:42:38 PM.163 << L2CAP_Connection_Response [03]
2/19/2013 4:42:38 PM.163 << L2CAP_Configuration_Request [04]
2/19/2013 4:42:38 PM.194 >> L2CAP_Configuration_Request [04]
2/19/2013 4:42:38 PM.194 << L2CAP_Configuration_Response [05]
2/19/2013 4:42:38 PM.210 >> L2CAP_Configuration_Response [05]
2/19/2013 4:42:38 PM.210 << L2CAP_Connection_Request [02] PSM [01]
2/19/2013 4:42:38 PM.241 >> L2CAP_Connection_Response [03] [01]
2/19/2013 4:42:38 PM.241 >> L2CAP_Connection_Response [03] [00]
2/19/2013 4:42:38 PM.241 << L2CAP_Configuration_Request [04]
2/19/2013 4:42:38 PM.257 >> L2CAP_Configuration_Response [05]
2/19/2013 4:42:38 PM.257 >> L2CAP_Configuration_Request [04]
2/19/2013 4:42:38 PM.257 << L2CAP_Configuration_Response [05]
2/19/2013 4:43:10 PM.065 ++ Notify [Arrival] [{E2824A09-DBAA-4407-85CA-C8E8FF5F6FFA}] [\\?\USB#VID_054C&PID_0268#6&1A8123C&0&6#{E2824A09-DBAA-4407-85CA-C8E8FF5F6FFA}]
2/19/2013 4:43:10 PM.065 -- Device Arrival [00:1E:3DE:36:83]
2/19/2013 4:43:10 PM.065 -- USB Device : HID_Worker_Thread Starting
2/19/2013 4:43:10 PM.065 ++ Paired DS3 [00:1E:3DE:36:83] To BTH Dongle [00:11:67:00:0E:FE]
2/19/2013 4:43:25 PM.464 >> HCI_Disconnection_Complete_EV [05]

@dead_pixel: if delayed start isn't working it sounds like it's either a problem downloading the loadware or the device itself that has an issue. Loadware for my Atheros device is in System32\Drivers\AtherosBT.bin, might want to verify that there is no issue reading it off disk.

@zoomHYPERIONzoom: the logs are showing that the controller is not far off from connecting, it doesn't seem to be responding to the Service channel initialisation reports. I've attached a zipped ScpControl.dll to which I've added a timeout for these reports which you can try.

1. Stop the Service.
2. Replace "C:\Program Files\Scarlet.Crush Productions\bin\System\ScpControl.dll" with the one from the archive.
3. Start the Service.
4. Try your knock-off controller.
5. Post the ScpService.log [zip it up first, then can post as an attachment].

I also see the controller being paired multiple times, this means what is being read back from the controller is not the same as what is getting written to it. Nothing I can do about that.

(02-19-2013, 10:35 PM)Scarlet.Crush Wrote: [ -> ]@dead_pixel: if delayed start isn't working it sounds like it's either a problem downloading the loadware or the device itself that has an issue. Loadware for my Atheros device is in System32\Drivers\AtherosBT.bin, might want to verify that there is no issue reading it off disk.

@zoomHYPERIONzoom: the logs are showing that the controller is not far off from connecting, it doesn't seem to be responding to the Service channel initialisation reports. I've attached a zipped ScpControl.dll to which I've added a timeout for these reports which you can try.

1. Stop the Service.
2. Replace "C:\Program Files\Scarlet.Crush Productions\bin\System\ScpControl.dll" with the one from the archive.
3. Start the Service.
4. Try your knock-off controller.
5. Post the ScpService.log [zip it up first, then can post as an attachment].

I also see the controller being paired multiple times, this means what is being read back from the controller is not the same as what is getting written to it. Nothing I can do about that.

I tried the new ScpControl.dll but, alas, I had no success.

Thanks for trying but I've decided to buy some official DS3's in red and white. They're not that much more expensive on eBay. I only lost about $30 bucks on the two knock-off controllers so I'll just chalk it up to the cost of experimentation.

The knock-offs' incompatibility with your DS3 wrapper is not the only reason for dumping them. I've discovered that the thumb sticks are too sensitive as well. They max out at only half their intended range. Not helpful for sensitive controls such as driving games.

Thanks again, I really appreciate the extra effort you put in for me and everyone that's posted here.

Hyperion

I had a question asked to me and I couldn't answer it. So I'll ask here. Can your SCP's 360 emulator work at the same time as a 360 controller, without causing a conflict? I'd assume they would, simply because of the concept of 360 emulator, but I don't know how it really works.

Hey, I'm a complete rookie when it comes to all of this business and I can't seem to get my ps3 controller to work with pcsx2. I installed the the SPCfilterdriver, but when I try and run SPCUser in the 64-bit folder, it says MSVP100.dll is missing from my computer. Can anyone give me a step-by-step guide on how to get this working? I've tried reading through everything, but like I've said I'm not very competent when it comes to stuff like this.
Thanks in advanced!

@MaJoR: yes, you can mix virtual X360 controllers with real wired/wireless X360 controllers without conflict. The LEDs might not match, dependant on order of startup, and limited to 4 controllers total [XInput limitation].

@sekuiden: you need to install the Microsoft VC Runtime. You should already have the Win32 version installed in order to run PCSX2 [32 bit process].

Win32 (x86) - http://www.microsoft.com/en-us/download/...px?id=5555
Win64 (x64) - http://www.microsoft.com/en-us/download/...x?id=14632

Holy crap that was fast. Thanks dude! I have one more question while I'm at it. Does your driver have any support for Dinput? I was using the wired version and remember it having Dinput, I think anyway, and using the bluetooth beta it seems to be xinput only. I'm kind of confused by that... What is your Dinput support?

@MaJoR: DInput is provided by the Common Controller subsystem, same as for a real X360 controller. Open Devices & Printers, right-click on your Xbox 360 Controller for Windows -> Game Controller Settings, this displays DInput settings.