XInput Wrapper for DS3 and Play.com USB Dual DS2 Controller
@Topken: there is no Bluetooth debug in the log, so the Bluetooth driver has not been installed. Most likely reason is your dongles hardware id is not listed in the inf/cat file, or was not plugged in when you ran ScpDriver. Can you post the hardware id of your dongle and I will add it to the inf/cat.

Sponsored links

Ok its a PCI x1 wifi/bluetooth adapter combo that came free witht he Motherboard from gigabyte. I will try to locate the hardware Id considering there are multiple bluetooth entries in the device manager

Here is what the entry Bluetooth USB Module says for Hardware ID

USB\VID_04CA&PID_3006&REV_0001
USB\VID_04CA&PID_3006
@Topken: added your hardware id, update attached.


Attached Files
.7z   ScpServer-0.6.0.93-Bth-Update.7z (Size: 6,73 KB / Downloads: 292)
thanks scarlet now if only I could fix that pcsx2 crash issue when I put the XInput dll in with PCSX2.exe so I can use it with PCSX2

Ok after updating its not working via bluetooth still heres the new log

Code:
1/29/2013 7:42:19 PM.733 ++ C:\Users\Andrew\Downloads\ScpServer-0.6.0.93\ScpServer\bin\ScpService.exe 0.6.0.93
1/29/2013 7:42:19 PM.752 ++ C:\Users\Andrew\Downloads\ScpServer-0.6.0.93\ScpServer\bin\ScpControl.dll 0.6.0.93
1/29/2013 7:42:20 PM.570 ++ Microsoft Windows 7 Home Premium Service Pack 1 (6.1.7601.65536 AMD64)
1/29/2013 7:42:20 PM.699 -- Bluetooth  : L2CAP_Worker_Thread Starting
1/29/2013 7:42:20 PM.702 -- Bluetooth  : HCI_Worker_Thread Starting
1/29/2013 7:42:20 PM.704 << HCI_Reset [0C03]
1/29/2013 7:42:20 PM.708 -- Controller : UDP_Worker_Thread Starting
1/29/2013 7:42:20 PM.725 >> HCI_Command_Complete_EV [0E]
1/29/2013 7:42:20 PM.977 << HCI_Read_BD_ADDR [1009]
1/29/2013 7:42:20 PM.981 >> HCI_Command_Complete_EV [0E]
1/29/2013 7:42:20 PM.984 << HCI_Read_Buffer_Size [1005]
1/29/2013 7:42:20 PM.987 >> HCI_Command_Complete_EV [0E]
1/29/2013 7:42:20 PM.988 -- 03FE, B7, 0008, 0005
1/29/2013 7:42:20 PM.993 << HCI_Read_Local_Version_Info [1001]
1/29/2013 7:42:20 PM.995 >> HCI_Command_Complete_EV [0E]
1/29/2013 7:42:20 PM.997 << HCI_Write_Scan_Enable [0C1A]
1/29/2013 7:43:53 PM.154 ++ Notify [Removal] [{E2824A09-DBAA-4407-85CA-C8E8FF5F6FFA}] [\\?\USB#VID_054C&PID_0268#5&2C82CF20&0&3#{E2824A09-DBAA-4407-85CA-C8E8FF5F6FFA}]
1/29/2013 7:43:53 PM.155 -- Device Removal [60:38:0E:75:F2:3C]
1/29/2013 7:44:37 PM.977 -- Received : Status Request [127.0.0.1:59816]
1/29/2013 7:45:08 PM.938 ++ Notify [Arrival] [{E2824A09-DBAA-4407-85CA-C8E8FF5F6FFA}] [\\?\USB#VID_054C&PID_0268#5&2C82CF20&0&3#{E2824A09-DBAA-4407-85CA-C8E8FF5F6FFA}]
1/29/2013 7:45:08 PM.978 -- Device Arrival [60:38:0E:75:F2:3C]
1/29/2013 7:45:09 PM.144 ++ Paired DS3 [60:38:0E:75:F2:3C] To BTH Dongle [20:68:9D:26:08:06]
1/29/2013 7:45:19 PM.412 ++ Notify [Removal] [{E2824A09-DBAA-4407-85CA-C8E8FF5F6FFA}] [\\?\USB#VID_054C&PID_0268#5&2C82CF20&0&3#{E2824A09-DBAA-4407-85CA-C8E8FF5F6FFA}]
1/29/2013 7:45:19 PM.415 -- Device Removal [60:38:0E:75:F2:3C]
1/29/2013 7:45:24 PM.540 ++ Notify [Arrival] [{E2824A09-DBAA-4407-85CA-C8E8FF5F6FFA}] [\\?\USB#VID_054C&PID_0268#5&2C82CF20&0&3#{E2824A09-DBAA-4407-85CA-C8E8FF5F6FFA}]
1/29/2013 7:45:24 PM.576 -- Device Arrival [60:38:0E:75:F2:3C]
@Topken: so the dongle looks to be active and the DS3 is paired, but doesn't seem to be attempting to connect. Can you post the HCI & LMP versions (visible on ScpMonitor).

Do the LEDs on the DS3 flash when you disconnect it from USB, or press the PS button when not connected via USB?

Can you run this test and post the log - unplug from USB, wait till the LEDs go out, stop and start the service, press the PS button, wait for 30secs, collect the log.

Can you also verify that it can connect to a PS3 via Bluetooth?
Hello,
this looks great, but I can't get it to work.
I'm trying to use a regular DS3 via USB cable, which works fine with the MotionInJoy drivers.
I've extracted the xinput1_3.dll and scpuser.exe. When running scpuser.exe, it seems to recognize the DS3 as the first controller, but it keeps switching between "connected" and "disconnected" in a 1-second interval. It also does not work in games, pcsx2, etc.

I've tried two DS3's, they both work fine on the PS3, and I've tried it on Windows 7 and 8. What am I doing wrong?
The LEDs do flash then they come stay on 1 and the controler works perfectly fine with the PS3

HCI Version is 7.4354 and LMP version is 6.1

Ok after giving it a try today bluetooth is now working fine according to the SCPUser.exe tester. Guess it just needed a fresh install instead of just an upgrade. Now if only I could get it to work with PCSX2 which just crashes when I put the XInput1_3.dll file in the main PCSX2 folder where you normally stick wrappers. Will give it a try with dolphin in a bit and see what happens there.

and now dolphin is crashing when I go to config either the gamecube pad or the wii remote with the same file from the 64bit version in the dolphin main folder.

Ok it works if I run dolphin as an admin even tho its in a folder that does not need admin rights to work from. I will be giving PCSX2 a try as admin and seeing if that works since apparently its needed.
@Topken: you don't need to put the XInput1_3.dll into the PCSX2 or Dolphin folders, the drivers provide native XInput.

If an XInput device is not available, you may need to update the bus driver (see Post #233). You can verify that this is required by right-clicking the PCSX2 or Dolphin executable and selecting "Run as administrator". If an XInput device is now available you require the update.

The XInput1_3.dll(s) provide an extension for pressure sensitive button support - this is only supported via the custom Lilypad provided and Pokopom.
@retux: Your using the Filter Driver from Post #1, correct? You need to install the filter driver. Plug in your DS3 to USB, run System\ScpFilterDriver.exe from the archive, click Install.
(01-31-2013, 12:28 AM)Scarlet.Crush Wrote: @retux: Your using the Filter Driver from Post #1, correct? You need to install the filter driver. Plug in your DS3 to USB, run System\ScpFilterDriver.exe from the archive, click Install.

I don't know how I missed that. Thanks, now it works.




Users browsing this thread: 11 Guest(s)