..:: PCSX2 Forums ::..

Hi! I'm asking for help...
I've two BT controllers from the list but I can't pair it with PS3 controller...
I've followed instructions and installed everything. When I connect PS3 controller, the log file says:
20.10.2013 11:33:51.839 -- Device Arrival [00:1E:3DE:CA:0F]
20.10.2013 11:33:51.842 -- Started Device Instance [USB\VID_054C&PID_0268\6&60C5015&0&1]
20.10.2013 11:33:51.845 ++ Paired DS3 [00:1E:3DE:CA:0F] To BTH Dongle [00:26:83:11:17:A5]
20.10.2013 11:33:51.842 -- USB Device : HID_Worker_Thread Starting

Ok, they paired. Now unplug USB from DS3.

20.10.2013 11:34:23.382 ++ Notify [Removal] [{E2824A09-DBAA-4407-85CA-C8E8FF5F6FFA}] [\\?\USB#VID_054C&PID_0268#6&60C5015&0&1#{E2824A09-DBAA-4407-85CA-C8E8FF5F6FFA}]
20.10.2013 11:34:23.383 -- Device Removal [00:1E:3DE:CA:0F]
20.10.2013 11:34:23.384 -- USB Device : HID_Worker_Thread Exiting
20.10.2013 11:34:34.120 >> HCI_Connection_Request_EV [04]
20.10.2013 11:34:34.123 << HCI_Remote_Name_Request [0419]
20.10.2013 11:34:34.127 >> HCI_Command_Status_EV [0F] [00]
20.10.2013 11:34:34.201 >> HCI_Remote_Name_Request_Complete_EV [07]
20.10.2013 11:34:34.204 -- Remote Name : 00:1E:3DE:CA:0F - PLAYSTATION®3Conteroller-ghic
20.10.2013 11:34:34.207 << HCI_Reject_Connection_Request [040A]
20.10.2013 11:34:34.210 >> HCI_Command_Status_EV [0F] [00]

So while using any of two compatible BT adapters I always get
HCI_Reject_Connection_Request [040A]
Maybe 040A means something useful?
I can't also pair controller using MotioninJoy 0.7.0001 but it easily pairs with MotioninJoy 0.7.0000
Before each try I removed one of BT controllers physically, so there are no conflicts, only one BT controller presents at once
Of course, it works by USB if I don't install BT drivers from the tool, but I want to use wireless connection without MotioninJoy (

Hi guys , i have problem with this driver , looks like i 've installed it , and it's blinking on LED as a first controller,but it's not working in Street Fighter AE, help me please. Already reinstalled it several times.

(10-19-2013, 06:14 PM)Huesoman Wrote: [ -> ]But you should know that even with this hardware ids some reviews are not supported.

Yeah, mine is "USB\VID_0E5E&PID_6622", it's in the list but I'm still close to be sure this is the reason of my problems...

(10-19-2013, 06:14 PM)Huesoman Wrote: [ -> ]Yeah I understand you are a little afraid, it's normal, I was afraid too, but after reading 154 pages of this thread the worst issue I found is that in very few cases the DS3 controller stop working but it has a very easy solution: push the reset button in its back and voila! it will work again, no major issues besides what I just explained.

I'm here again just becose my pad couldn't be paired with my PS3 anymore, but thanks to you I have already solved that issue =P
And of course, I'm ready to try again!

(10-19-2013, 06:14 PM)Huesoman Wrote: [ -> ]I search a lot in this thread and reply to various users, you can check out all my posts,
http://forums.pcsx2.net/search.php?actio...ddf82f0d67

Thanks for this collection! I'm reading them carefully...

(10-19-2013, 06:14 PM)Huesoman Wrote: [ -> ]Make sure to have installed these:
1. Microsoft .NET 4.0
2. Visual C 2010 Runtime.
3. Latest DirectX Runtime.
4. Latest Xbox 360 Controller Drivers available.
5. Genuine Sony DualShock3 or SixAxis Controller(s).
6. Minimum of Bluetooth 2.0 + EDR Dongle (if using Bluetooth).
7. Administrator rights on your PC.

Everything is installed correctly, no doubts...

Now I'm doing a clean installation (again)...

Edit~ I'm not sure about the version of my dongle, it's quite old and probably it's under the 2.0 but i can't find out how to check...
If that's true, it'll be a very big shame =(

Edit~ I found another dungle (Bluetooth 2.1) which appears in the compatible devices list, but after a clean installation it seems it's everything the same... I don't know what to do next...

Does anyone know if its possible to have this Xinput wrapper only install to a single USB slot? I have 2 different bluetooth pieces that I would like to use for different things too, but this wrapper thing likes to install on evey bluetooth piece connected

Guys is it working with SSF4AE game , cause in my case it's not.

Hey, I didn't think this would work, but just manually adding my BT Device ID to the INF file worked. Might be something to try if your controller works with your dongle under MotioninJoy, but isn't recognised by SCP.

\ScpServer\bin\System\BthWinUsb.inf


The ones supplied work for my Sony Vaio VPCF1. I ran the Driver Installer again (Force Install checked) and it snapped right to.

Hey

Sorry if it has been mentioned before but I could not find it via search. Just want to know if Asus BT400 (Bluetooth 4.0, backward compatible) is compatible with Xinput Wrapper and also same question as the previous 2 poster above, is it possible to install the driver for a specific bluetooth dongle instead of installing to all dongles that are connected?

Thanks!

(10-21-2013, 04:48 AM)valkyr1e Wrote: [ -> ]Is it possible to install the driver for a specific bluetooth dongle instead of installing to all dongles that are connected?

Likely not. It looks like SPC just installs to everything in one click. I'd recommend removing one dongle, Installing the driver on the one you leave in place, then plugging the second one back in. Can't try this myself, but you might want to give it a shot.

(10-21-2013, 04:55 AM)TesseractE Wrote: [ -> ]Likely not. It looks like SPC just installs to everything in one click. I'd recommend removing one dongle, Installing the driver on the one you leave in place, then plugging the second one back in. Can't try this myself, but you might want to give it a shot.

Thanks for the info and I might just try that. And also, do you have a clue whether bluetooth 4.0 is compatible?

I am probably going to try the method you specify anyway by adding the hardware IDs manually to the .inf

Thanks!

(10-21-2013, 06:32 AM)valkyr1e Wrote: [ -> ]Thanks for the info and I might just try that. And also, do you have a clue whether bluetooth 4.0 is compatible?

Not a clue, I'm afraid. I don't think any of my BT devices are 4.0

Quote:I am probably going to try the method you specify anyway by adding the hardware IDs manually to the .inf

Thanks!

Sure thing! Don't forget to touch base back here if it works so others can know that it does!