XInput Wrapper for DS3 and Play.com USB Dual DS2 Controller

[Scarlet.Crush]

@Zolcillonca:

Code:

public enum Ds3Battery : byte { None = 0x00, Dieing = 0x01, Low = 0x02, Medium = 0x03, High = 0x04, Full = 0x05, Charging = 0xEE, Charged = 0xEF };

Your controller shows 241 (decimal) => 0xF1.

I highly doubt that any firmware localisation would change an enumeration constant.

When a genuine DS3 shows strange behaviour it is usually fixed by a pinhole reset. Do you feel a slight click when you press the reset button?

@WatchEmFall: the main changes between 103 and 136/139 was the addition of Secure Simple Pairing (SSP) to support DS4s. Your dongle is failing one of the setup calls for SSP, so upgrade to 139 then go into configuration and check the "Disable SSP" option [this reverts the behaviour to be the same as 103]

@PB84: genuine Sony DS3s have no issues with Rumble over BTH.

@hellbringer616:
@ultimategrayfox:

you can use a dongle which is not directly supported in the list by using Zadig to install WinUSB on it. See Post #1851

@DirtyShady: DS3/DS4 on the same dongle [I'm sitting at my games machine with 1 DS4 on BTH, 1 DS4 on USB, 1 DS3 on BTH, 1 DS3 on USB - all working correctly].

To use a DS4 on BTH your Dongle must support Secure Simple Pairing (SSP).

@Reznik Akime: I think you have missed out installing one of the prereqs -

3. Latest DirectX Runtime.

1. Remove any dll you have manually placed in Windows\System32.
2. Download and Save the DirectX Runtime from - http://www.microsoft.com/en-us/download/...px?id=8109
3. Move the directx_Jun2010_redist.exe file from your Downloads directory to a temp directory [eg C:\Temp]
4. Run the exe, it is a self-extracting archive.
5. Go to the directory that you extracted it to and run DXSETUP.exe.
6. After it has completed run Windows Update.
7. Reboot.
8. Run ScpUser.exe from the ScpServer\bin\Win32 directory.
9. Click Advanced, click Extensions - verify that you see variable pressure on Circle, Triangle, Cross and Square.
10. Report back - if everything is good can continue to PCSX2 configuration.

@Sky-Dragon: I think your Dongle should be OK, try a pin-hole reset on your DS3.

The dongle is also responding correctly to all the setup calls for Secure Simple Pairing, so should work with DS4.

- I had a Trust dongle which worked well until I tried to move it from a front-panel port to a USB Hub port, it fell apart when I pulled it out >.<

[Sky-Dragon]

@Sky-Dragon: I think your Dongle should be OK, try a pin-hole reset on your DS3.

The dongle is also responding correctly to all the setup calls for Secure Simple Pairing, so should work with DS4.

- I had a Trust dongle which worked well until I tried to move it from a front-panel port to a USB Hub port, it fell apart when I pulled it out >.<

Thanks again for the help! And I'm sorry about your Trust Dongle, I hate when stuff like this happens :/

Also I'm glad the Secure Simple Pairing seems fine, like said my DS4 works like a charm though even now after a pinhole reset my White DS3 won't connect over BTH.

Just to be sure I also tried my second DS3 that came with my PS3 and it wouldn't connect over BTH aswell with the Trust Dongle, I even disabled Secure Simple Pairing to test if that was the issue with the DS3s and no dice

On my old Hama Dongle both of my DS3 worked flawlessly but as mentioned before the DS4 can't work with it due to the lack of Secure Simple Pairing :/

Would it be possible to use both dongles at the same time? Or atleast, lets say I have both dongles plugged in, could I disable one depending if I want to use a DS3 or DS4? Thanks in advance for any additional help!

EDIT: If I plug in my old dongle at the same time with my new one the old one is recognized fine in the device manager but it doesn't blink so I guess it conflicts with the new one :/

[Scarlet.Crush]

@Sky-Dragon: you can't use both dongles at the same time, but you could switch between them with a bit of faffing around.

Using DS4, switch to DS3 -
1. Disable SSP in Configuration.
2. Stop the Service.
3. In Device Manager - Disable the Trust Dongle, Enable the Hama Dongle.
4. Start the Service.

Using DS3, switch to DS4 -
1. Enable SSP in Configuration.
2. Stop the Service.
3. In Device Manager - Disable the Hama Dongle, Enable the Trust Dongle.
4. Start the Service.

It's a bit weird that your DS3s don't work with the Trust dongle though ...

The Service only uses the first active dongle that it finds - so if both are active, only the first is used, the other is ignored. Hence the Disable/Enable steps.

[Reznik Akime]

@Zolcillonca:

Code:

public enum Ds3Battery : byte { None = 0x00, Dieing = 0x01, Low = 0x02, Medium = 0x03, High = 0x04, Full = 0x05, Charging = 0xEE, Charged = 0xEF };

Your controller shows 241 (decimal) => 0xF1.

I highly doubt that any firmware localisation would change an enumeration constant.

When a genuine DS3 shows strange behaviour it is usually fixed by a pinhole reset. Do you feel a slight click when you press the reset button?

@WatchEmFall: the main changes between 103 and 136/139 was the addition of Secure Simple Pairing (SSP) to support DS4s. Your dongle is failing one of the setup calls for SSP, so upgrade to 139 then go into configuration and check the "Disable SSP" option [this reverts the behaviour to be the same as 103]

@PB84: genuine Sony DS3s have no issues with Rumble over BTH.

@hellbringer616:
@ultimategrayfox:

you can use a dongle which is not directly supported in the list by using Zadig to install WinUSB on it. See Post #1851

@DirtyShady: DS3/DS4 on the same dongle [I'm sitting at my games machine with 1 DS4 on BTH, 1 DS4 on USB, 1 DS3 on BTH, 1 DS3 on USB - all working correctly].

To use a DS4 on BTH your Dongle must support Secure Simple Pairing (SSP).

@Reznik Akime: I think you have missed out installing one of the prereqs -


1. Remove any dll you have manually placed in Windows\System32.
2. Download and Save the DirectX Runtime from - http://www.microsoft.com/en-us/download/...px?id=8109
3. Move the directx_Jun2010_redist.exe file from your Downloads directory to a temp directory [eg C:\Temp]
4. Run the exe, it is a self-extracting archive.
5. Go to the directory that you extracted it to and run DXSETUP.exe.
6. After it has completed run Windows Update.
7. Reboot.
8. Run ScpUser.exe from the ScpServer\bin\Win32 directory.
9. Click Advanced, click Extensions - verify that you see variable pressure on Circle, Triangle, Cross and Square.
10. Report back - if everything is good can continue to PCSX2 configuration.

@Sky-Dragon: I think your Dongle should be OK, try a pin-hole reset on your DS3.

The dongle is also responding correctly to all the setup calls for Secure Simple Pairing, so should work with DS4.

- I had a Trust dongle which worked well until I tried to move it from a front-panel port to a USB Hub port, it fell apart when I pulled it out >.<

Did the steps you listed and I'm afraid it didn't work. SCPuser's extension reports nothing but N/A across the board, but the controller is detected and working flawlessly otherwise. Even tried a pinhole reset for ten seconds. :\ Is there any kind of config or device info I can give you that will help?

[Sky-Dragon]

@Sky-Dragon: you can't use both dongles at the same time, but you could switch between them with a bit of faffing around.

Using DS4, switch to DS3 -
1. Disable SSP in Configuration.
2. Stop the Service.
3. In Device Manager - Disable the Trust Dongle, Enable the Hama Dongle.
4. Start the Service.

Using DS3, switch to DS4 -
1. Enable SSP in Configuration.
2. Stop the Service.
3. In Device Manager - Disable the Hama Dongle, Enable the Trust Dongle.
4. Start the Service.

It's a bit weird that your DS3s don't work with the Trust dongle though ...

The Service only uses the first active dongle that it finds - so if both are active, only the first is used, the other is ignored. Hence the Disable/Enable steps.

Ah okay thanks for the detailed steps, that doesn't sound like too much
trouble given that I would only switch to the DS3s while friends come over for multiplayer gaming or if my PS4 is in use. I will give my PC a good reboot tomorrow and redo everything to make sure nothing messes with the DS3's but I think I can live with the situation like this

Otherwise I can still always return the dongle for a Belkin or similar one I will see! Out of curiosity, assuming I have a dongle that works with DS3's and DS4's, is it possible to use both types of controllers simultaneously?

[Scarlet.Crush]

@Sky-Dragon: yeah, I'm running DS3s & DS4s simultaneously on both my games machine & HTPC.

@Reznik Akime: was your DS3 connected before you ran ScpUser, and the XInput1_3.dll from the package in the same directory as ScpUser? [inadvertently done a Move instead of Copy at some point?].

Can you do the following -
1. Run ScpMonitor.
2. Verify your DS3 is displayed in Pad 1.
3. Open Configuration - Verify that "Disable Native Feed" is not checked.
4. Run ScpUser and check the Extensions - ensure only 1 copy is running.
5. Open a command prompt and run : netstat -abn > netstat.log
6. Zip up ScpService.log, ScpDriver.log, ScpControl.xml and netstat.log and post as an attachment.

[DatPratt]

Hi SC,

Great code work and good ideas

It works fine for me as long as I am connected with USB...when installing with SCPDriver it does not install the Bluetooth Driver and I have not been successful finding workarounds to manually pair it. Other programs like Motioninjoy also do not detect my bluetooth adapter.

PS: Whenever I tried to install the driver on (what I think was) the port for the bluetooth adapter in Motioninjoy there was an error, something I have not experienced on other computers.

Running Windows 8
Adapter: Intel Dual-Band Wireless N-7260

Thanks in advance

[Scarlet.Crush]

@DatPratt: it's not a Bluetooth Adapter, it's WiFi.

[DatPratt]

@DatPratt: it's not a Bluetooth Adapter, it's WiFi.

True....I wasn't clear on that lol...

However, it does have Bluetooth capabilities. I do have bluetooth drivers installed for it.

It may be listed as a different device but I think it runs on the same chip. Heres the info from Intel

[Scarlet.Crush]

@DatPratt: ok, so it's an "Intel Dual-Band Wireless N-7260 Plus Bluetooth".

Select the Details tab, select Hardware Ids from the drop down.

Run Zadig, as described in Post #1851. In Step 8 select the device that matches the Hardware Id on the Details tab.