..:: PCSX2 Forums ::..

(05-17-2015, 12:35 AM)kur1977 Wrote: [ -> ]Hi all!

I have a trouble.

I have a Windows 7 64 bit, DS3 controller, USB\VID_0A12&PID_0001&REV_0101 bluetooth controller (see it in supported controllers list)

Did everything as described in 1st post. (use 1.2.0.160 with the latest 1.2.2.175 update)

All ok with wired connection. But when I disconnect the DS3 from PC - I see in ScpMotinor :



the 00000000 zeros are not change as it while wired connection.
And controller does not working by bluetooth (


ScpService.log

Code:

2015-05-17 01:19:19.033 ++ C:\XInput\ScpService.exe 1.2.2.175
2015-05-17 01:19:19.053 ++ C:\XInput\ScpControl.dll 1.2.2.175
2015-05-17 01:19:19.153 ++ Microsoft Windows 7 Service Pack 1 (6.1.7601.65536 AMD64)
2015-05-17 01:19:19.153 -- Bus Open   : Offset 0
2015-05-17 01:19:19.163 -- Bus Open   : Path \\?\ROOT#SYSTEM#0001#{F679F562-3164-42CE-A4DB-E7DDBE723909}
2015-05-17 01:19:19.243 ## Mapper.Initialize() - Profiles [5] Active [Default] Mappings [0]
2015-05-17 01:19:19.283 -- Controller : UDP_Worker_Thread Starting
2015-05-17 01:19:19.283 -- Bluetooth  : L2CAP_Worker_Thread Starting [82,02]
2015-05-17 01:19:19.293 -- Bluetooth  : HCI_Worker_Thread Starting [81]
2015-05-17 01:19:19.293 << HCI_Reset [0C03]
2015-05-17 01:19:19.303 >> HCI_Disconnection_Complete_EV [05]
2015-05-17 01:19:19.303 >> HCI_Command_Complete_EV [0E] [00] [HCI_Reset]
2015-05-17 01:19:19.553 << HCI_Read_BD_ADDR [1009]
2015-05-17 01:19:19.553 >> HCI_Command_Complete_EV [0E] [00] [HCI_Reset]
2015-05-17 01:19:19.553 >> HCI_Command_Complete_EV [0E] [00] [HCI_Read_BD_ADDR]
2015-05-17 01:19:19.563 << HCI_Read_Buffer_Size [1005]
2015-05-17 01:19:19.563 >> HCI_Command_Complete_EV [0E] [00] [HCI_Read_Buffer_Size]
2015-05-17 01:19:19.563 -- 0179, 10, 000A, 0000
2015-05-17 01:19:19.563 << HCI_Read_Local_Version_Info [1001]
2015-05-17 01:19:19.573 >> HCI_Command_Complete_EV [0E] [00] [HCI_Read_Local_Version_Info]
2015-05-17 01:19:19.573 -- Master 00:1B:10:00:25:AC, HCI_Version 2.0000, LMP_Version 2.0309
2015-05-17 01:19:19.573 << HCI_Write_Scan_Enable [0C1A]
2015-05-17 01:19:19.573 >> HCI_Command_Complete_EV [0E] [00] [HCI_Write_Scan_Enable]
2015-05-17 01:19:34.635 ++ Notify [Arrival] [{E2824A09-DBAA-4407-85CA-C8E8FF5F6FFA}] [\\?\USB#VID_054C&PID_0268#5&16E02094&0&2#{E2824A09-DBAA-4407-85CA-C8E8FF5F6FFA}]
2015-05-17 01:19:34.635 -- DS3 Arrival Event
2015-05-17 01:19:34.685 -- Device Arrival [00:21:4F:7A:E4:0D]
2015-05-17 01:19:34.695 -- Bus Plugin : Serial 1
2015-05-17 01:19:34.695 ++ Plugin Port #1 for [00:21:4F:7A:E4:0D]
2015-05-17 01:19:34.715 -- USB Device : HID_Worker_Thread Starting
2015-05-17 01:19:34.736 -- Started Device Instance [USB\VID_054C&PID_0268\5&16E02094&0&2] Local [00:21:4F:7A:E4:0D] Remote [00:1B:10:00:25:AC]
2015-05-17 01:19:42.087 ++ Notify [Removal] [{E2824A09-DBAA-4407-85CA-C8E8FF5F6FFA}] [\\?\USB#VID_054C&PID_0268#5&16E02094&0&2#{E2824A09-DBAA-4407-85CA-C8E8FF5F6FFA}]
2015-05-17 01:19:42.087 -- Device Removal [00:21:4F:7A:E4:0D]
2015-05-17 01:19:42.090 -- USB Device : HID_Worker_Thread Exiting
2015-05-17 01:19:42.802 >> HCI_Connection_Request_EV [04]
2015-05-17 01:19:42.802 << HCI_Delete_Stored_Link_Key [0C12]
2015-05-17 01:19:42.812 << HCI_Remote_Name_Request [0419]
2015-05-17 01:19:42.822 >> HCI_Command_Complete_EV [0E] [00] [HCI_Delete_Stored_Link_Key]
2015-05-17 01:19:42.822 >> HCI_Command_Status_EV [0F] [00] [HCI_Remote_Name_Request]
2015-05-17 01:19:42.876 >> HCI_Remote_Name_Request_Complete_EV [07]
2015-05-17 01:19:42.876 -- Remote Name : 00:21:4F:7A:E4:0D - PLAYSTATION(R)3 Controller
2015-05-17 01:19:42.886 << HCI_Accept_Connection_Request [0409]
2015-05-17 01:19:42.886 >> HCI_Command_Status_EV [0F] [00] [HCI_Accept_Connection_Request]
2015-05-17 01:19:43.196 >> HCI_Role_Change_EV [12]
2015-05-17 01:19:43.236 >> HCI_Connection_Complete_EV [03]
2015-05-17 01:19:53.243 >> L2CAP_Connection_Request [02] PSM [11]
2015-05-17 01:19:53.253 << L2CAP_Connection_Response [03]
2015-05-17 01:19:53.253 << L2CAP_Configuration_Request [04]
2015-05-17 01:19:53.333 >> L2CAP_Configuration_Request [04]
2015-05-17 01:19:53.343 << L2CAP_Configuration_Response [05]
2015-05-17 01:19:53.393 >> L2CAP_Configuration_Response [05]
2015-05-17 01:19:53.580 >> L2CAP_Connection_Request [02] PSM [13]
2015-05-17 01:19:53.580 << L2CAP_Connection_Response [03]
2015-05-17 01:19:53.580 << L2CAP_Configuration_Request [04]
2015-05-17 01:19:53.660 >> L2CAP_Configuration_Request [04]
2015-05-17 01:19:53.660 << L2CAP_Configuration_Response [05]
2015-05-17 01:19:53.720 >> L2CAP_Configuration_Response [05]
2015-05-17 01:19:53.720 << L2CAP_Connection_Request [02] PSM [01]
2015-05-17 01:19:53.750 >> L2CAP_Connection_Response [03] [01]
2015-05-17 01:19:53.750 >> L2CAP_Connection_Response [03] [00]
2015-05-17 01:19:53.750 << L2CAP_Configuration_Request [04]
2015-05-17 01:19:53.780 >> L2CAP_Configuration_Response [05]
2015-05-17 01:19:53.790 >> L2CAP_Configuration_Request [04]
2015-05-17 01:19:53.790 << L2CAP_Configuration_Response [05]
2015-05-17 01:19:54.020 << L2CAP_Disconnection_Request [06]
2015-05-17 01:19:54.050 >> L2CAP_Disconnection_Response [07]
2015-05-17 01:19:54.050 ++ Plugin Port #1 for [00:21:4F:7A:E4:0D]

Try this:
Right-click on ScpMonitor in Taskbar, select Configuration.
Check the Disable SSP option.

(05-17-2015, 10:07 AM)Oichi Wrote: [ -> ]1. Microsoft .NET 4.0
2. Visual C 2013 Runtime.
3. Latest DirectX Runtime.
4. Latest Xbox 360 Controller Drivers available.
5. Genuine Sony DualShock3 or DualShock4 or SixAxis Controller(s).
6. Minimum of Bluetooth 2.0 + EDR Dongle (if using Bluetooth).
7. Administrator rights on your PC.

I am Disconnected as hell right now from this. Do i HAVE to have a Dongle??

No, unless you want to use it wirelessly.

(05-17-2015, 04:42 PM)redfah Wrote: [ -> ]Hello people!
I really need some help around here!
Recently I have installed Windows 10 on my PC. EVERYTHING works just fine, all the correct drivers are properly installed. My Dualshock 3 controller works just fine connected via cable. However, I cannot get my USB BT Dongle to work. It is recognized on the system Device Manager as a Generic Bluetooth Radio, but whenever I open the SCP Monitor tool, I can only see the Host Address as "Disconnected".

I have a notebook with a Bluetooth card in it. So, in order not to generate conflict, I was oriented not to install the Bluetooth Driver via the SCP Driver installation.
So here is what I did:

4. Check that your normal Bluetooth devices are working correctly.
5. Open Device Manager, disable your Internal Intel BTH device.
6. Plug in your BTH dongle to USB.
7. Use Zadig to install WinUSB on to your BTH Dongle (In this step I had to download a new version of Zadig, because the one in your post was not installing the driver on my Dongle. But I managed to install it successfully, it says "WinUSB v6.1.7600.16385" as the installed driver).
8. Run ScpDriver, uncheck Bluetooth Driver, and check Force Install, click Install.
9. In Device Manager, enable your Internal Intel BTH device.
1. Run ScpMonitor.
2. Right-click on it's icon in Taskbar, select Configuration.
3. Check the Disable SSP option.
4. Click OK.

(Don`t mind the numbers, obviously they are out of order)

Here is the log of the SCP Driver Installation:

Code:

SCP Driver Installer 1.2.2.175 [5/4/2015 12:29:36 AM]

Detected - Microsoft Windows 10 Pro Insider Preview (6.2.9200.0 AMD64)
Selected DEFAULT configuration.

INFO    - ENTER:  DriverPackageInstallW
INFO    - Looking for Model Section [SCProductions.NTamd64]...
INFO    - Installing INF file 'C:\ScpServer\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_21ca245c0e23d7a​5\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:\ScpServer\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_15691982ca5c2​1ae\ds3winusb.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)

Install Succeeded.

-- Install Summary --
Bus Driver
DS3 USB Driver

So guys, I would like to resolve this problem since I am only able to use my controller with the cable.
Feel free if you need any additional information!
And thank you very much in advance!

Fabio D.

Try stopping the service and using ScpServer. It tends to be more useful for debugging. Post some logs from it.

(05-18-2015, 01:06 AM)Sundry92 Wrote: [ -> ]Hello guys! And respect to RayfenWindspear for helping others. I didnt find answer for my question (only things like update, restart, reconnect) so ive decided to post.

My problem is interesting one. All i want is to make my Sixaxis controller work via USB. My Sixaxis controller worked fine with MotionJoy, but I really hate that program so I decided to try this one. Ive installed and done everything in guide on new system (Win 7 x64 sp1). It shows usb ds3 device and xbox 360 controller connected in device manager. Procces "scpservice" also working. But gamepad continue to blink with 4 red lights and buttons dont work.

Then Ive connected my Dualshock 3 controller and...2nd number red light started blinking and buttons worked fine.

So any thoughts? I really need help, DS3 is so heavy to take it on long trip

Post some logs so we can see what is going on.

Hi, I have a ps3 controller (ds3) but my pc already have bluetooth (no dongle). What should I do?

(05-17-2015, 04:17 AM)SageX85 Wrote: [ -> ]Yeah, you can without problem i have it that way

sweet guess this will do - ?

http://www.ebay.com/itm/New-Mini-USB-4-0...1766380509

(05-18-2015, 06:29 PM)Renato Lopes Wrote: [ -> ]Hi, I have a ps3 controller (ds3) but my pc already have bluetooth (no dongle). What should I do?

Using builtin bluetooth has varied results. Is it a laptop? Usually issues arise with the fact that the driver Scp uses isn't able to power on builtin bluetooth properly. You can find a guide to install the driver here. If it stops working after shutting down or sleeping the computer, follow my instructions here.

(05-14-2015, 06:46 PM)RayfenWindspear Wrote: [ -> ]You may have to use the zadig tool to forcefully install the drivers. But first try this. Your install log shows that you first installed before applying the update. Try uninstalling everything, make sure the update is applied, then make sure both controller and dongle are plugged in before doing a reinstall with forced checked.

If that doesn't do it, zadig it. There are instructions for a DS4 on the first post which you can follow but make sure to do every step for a DS3 instead.

EDIT: Oh and I believe that ScpServer won't automatically pair the controller like the service does. There is a button to do so.

Thank you very much.
(re)Installing like you suggested, with patch already applied AND both dongle and controller plugged in, successfully installed a 360 controller.
It didn't paired automatically even with the service running until I rebooted the PC, but now it works too.

d(^_~ )

Has anyone using this with bluetooth had controllers die on them? I have had 2 controllers die in just 2 months, granted they were cheap controllers to begin with.

Also does anyone notice a decrease in battery life using this vs connecting to a PS3/4?

If enough people notice these symptoms, I plan on delving into the code to see if it is perhaps communicating too fast. I don't think I have the proper equipment to run a bluetooth sniffer to compare the traffic to a PS3 though, so finding the issue is likely impossible.

(05-18-2015, 10:07 PM)RayfenWindspear Wrote: [ -> ]Has anyone using this with bluetooth had controllers die on them? I have had 2 controllers die in just 2 months, granted they were cheap controllers to begin with.

Also does anyone notice a decrease in battery life using this vs connecting to a PS3/4?

If enough people notice these symptoms, I plan on delving into the code to see if it is perhaps communicating too fast. I don't think I have the proper equipment to run a bluetooth sniffer to compare the traffic to a PS3 though, so finding the issue is likely impossible.

Yes. My official DS3's loose battery rapidly. About 1 1/2 to 2 hours before the controllers die. (At full charge) However I notice when plugged in to usb the DS3's seems to charge rapidly; meaning they show a full charge in SCP while showing 2/3 bars when plugged in to a PS3 system. My guess is that there is a bug in SCP reading the capacity of the battery. Still no luck with your Panhai fix on my end; this past weekend I did some fooling around again with SCP and noticed the Panhai gamepads were showing up as PS3 controllers in my device manager. Also one of my official DS3's was showing up as a PS GA'EPAD (That's how windows refers to the knockoffs) in my device manager. Rolling back and uninstalling the drivers fixed that issue, however I still cant get the knockoffs to work via bluetooth. I think we might have different controllers. I'm willing to send you one to test, I have two. Thanks for all your help.

(05-19-2015, 05:06 AM)OfAnthony Wrote: [ -> ]Yes. My official DS3's loose battery rapidly. About 1 1/2 to 2 hours before the controllers die. (At full charge) However I notice when plugged in to usb the DS3's seems to charge rapidly; meaning they show a full charge in SCP while showing 2/3 bars when plugged in to a PS3 system. My guess is that there is a bug in SCP reading the capacity of the battery. Still no luck with your Panhai fix on my end; this past weekend I did some fooling around again with SCP and noticed the Panhai gamepads were showing up as PS3 controllers in my device manager. Also one of my official DS3's was showing up as a PS GA'EPAD (That's how windows refers to the knockoffs) in my device manager. Rolling back and uninstalling the drivers fixed that issue, however I still cant get the knockoffs to work via bluetooth. I think we might have different controllers. I'm willing to send you one to test, I have two. Thanks for all your help.

Something that I just learned recently that works for some is to go into the Monitor's configuration menu and check the Disable SSP option. Give that a try. You can get to it by right clicking the tray icon. I am pretty sure that does the same thing the service bypass for the panhai models does, but across the board for all controllers.

(05-18-2015, 10:07 PM)RayfenWindspear Wrote: [ -> ]Has anyone using this with bluetooth had controllers die on them? I have had 2 controllers die in just 2 months, granted they were cheap controllers to begin with.

Also does anyone notice a decrease in battery life using this vs connecting to a PS3/4?

If enough people notice these symptoms, I plan on delving into the code to see if it is perhaps communicating too fast. I don't think I have the proper equipment to run a bluetooth sniffer to compare the traffic to a PS3 though, so finding the issue is likely impossible.

Yeah it does seem to run out of juice much faster than when I'm using it one the console, but it also seems to charge much faster (which normally isn't a good thing since it kills the battery life faster if you charge with a stronger charge than stock). Yeah and I'm still struggling to make the controller work on the laptop. I read on a couple of forums that I have to disable driver signature enforcement, but even after that it still doesn't work. Neither SCPDriver, nor Zadig.

(05-18-2015, 10:07 PM)RayfenWindspear Wrote: [ -> ]Has anyone using this with bluetooth had controllers die on them? I have had 2 controllers die in just 2 months, granted they were cheap controllers to begin with.

Also does anyone notice a decrease in battery life using this vs connecting to a PS3/4?

If enough people notice these symptoms, I plan on delving into the code to see if it is perhaps communicating too fast. I don't think I have the proper equipment to run a bluetooth sniffer to compare the traffic to a PS3 though, so finding the issue is likely impossible.

I didn't notice any difference with the times I used my DS3 on PS3.