..:: PCSX2 Forums ::..

@ SC: it worked! After installing X360 Controller Accessories and reinstalling scp, plugged it in and ran just fine, no BSODs. Thanks!

@Scarlet.Crush: you should not disable native mode checkbox when no controllers found – this way it stays disabled until PCSX2 restart even if controllers are connected after that.
On the other hand, if i remove disabling it still doesn't detect connected later controllers without restart of PCSX2.

Scarlet.Crush:
Thanks for the tip to push that pair button on my Eee 901, that did the trick
I also noticed that on my v2.0 BT dongle that "pair" button is grayed out.
The Eee 901 radio device ID is "USB\VID_0B05&PID_B700&REV_0241", in case you want to add it.

@rama: cool, will add your hardware id for next release, which will move from prototype to alpha (since all major features are now in place with the custom Lilypad posted).

Awesome
I went and bought a new dongle and had no problems with that btw.
BT connection is working fine and I can use the pad with xbox360 controller emulator.
Unfortunately that doesn't support rumble though..

@rama: your using x360ce? there should be no need to use it, the Virtual Bus provides emulation to a native XInput level.

Popokom doesn't see it then (it works with 360ce).
Do I have to use Lilypad Scp (r5350) mod? If so, it only sees a "DX Controller (XBOX 360 for Windows)".
I have all input methods ticked.

(01-14-2013, 08:07 AM)Scarlet.Crush Wrote: [ -> ]@rama: unfortunately your dongle is BT 1.2. The first digit only of the HCI Version specifies the BT version and is coded (the rest is encoding formats). See here for the Bluetooth SIG numbering assignments.

I typo'd the version requirement for DS3s, it should be BT 2.0 + EDR. So you would need a dongle with HCI Version 3.xxxx or above.

Your dongle is doing all the connection setup correctly, it just doesn't understand the stream of reports coming from the DS3.

What's so squirrely about needing a dongle with an HCI version greater than or equal to 3.xxxx? My Bluetooth dongle was configured correctly and works fine in PCSX2 via usb and bluetooth and the HCI version is 1.3164. Forgive me if this was covered already I went back 8 pages and couldn't find an answer.

@rama: there are 2 usage patterns, make sure your DS3 is connected (via BTH or USB) before running PCSX2.

1. Native XInput
- Lilypad : use the default Lilypad that comes with PCSX2, check only XInput. Configure your pad.
- Pokopom : should run without any configuration

2. Pressure sensitive buttons via XInput Extensions
- Both : copy bin\Win32\XInput1_3.dll to your PCSX2 folder.
- Lilypad : use the Lilypad-Scp-r5350.dll, check only DualShock 3 native mode. Configure your pad. [see Post #177]
- Pokopom : should run without any configuration.

Win 8 : the System XInput1_3.dll seems to require Administrator rights, so start PCSX2 by right clicking and "Run as Administrator". Alternatively, create a shortcut for it and change it's properties Compatibility->Privilege level->Run this program as an administrator.

@OminaeYu: DS3s use EDR for it's report stream, if your dongle does not support EDR you will not get any reports from it. It's likely your dongle is just incorrectly reporting it's HCI Version.

First, I have to say, thank-you so much Scarlet, I can finally use a Dualshock 3 controller on my laptop without that garbage MotioninJoy crap!

However, I downloaded the XInput-Wrapper-SCP-2.2.1.88.7z file, extracted it, and I installed the Dualshock 3 drivers from the SCPFilterDriver file. When I go into an emulator and try to configure the buttons, all of the buttons work except for the D-Pad, L1 and L2 buttons; it made me very sad.

Is there something else I must download to make the D-Pad, L1 and L2 buttons work? I thought I only had to download the driver installer; I wanted drivers to be able to use my Dualshock 3 in any game I played.