04-03-2014, 09:27 PM
@niqht: yes, the drivers support both DS3 and DS4 controllers connected at the same time.
@UlyssesSKrunk: can you do the following
1. Open an elevated command prompt [Runas Administrator]
2. cd C:\Temp [create C:\Temp first if you don't have it]
3. pnputil -e > pnputil.txt
4. Zip up pnputil.txt and post as an attachment.
@randito34: you have a fake controller [00:26:5C signature], please update to latest update. [will be posting 1.2.2.175 shortly]
@Hiazu: your dongle doesn't support Secure Simple Pairing (SSP), please update to latest update and Disable SSP in options. [will be posting 1.2.2.175 shortly]
@Mikhail0: does your controller support Rumble over BTH when connected to a PS3?
@x_berzerker: after installing just manually install the original drivers back on to your integrated BTH via Device Manager.
@Daytrader: yes, the drivers make your DS3 appear as an X360 controller.
@beachybed: start ScpService from the Service Control Manager. [Control Panel -> Administrative Tools -> Services]
Also check that the Windows Event Log service is running.
@Abcdude: yes, the drivers support both DS3 and DS4 controllers connected at the same time.
@z_JoShua_z: you have a fake controller [00:26:5C signature], please update to latest update. [will be posting 1.2.2.175 shortly]
@kenshinjeff: can you reproduce your issue, then zip up ScpService.log && ScpDriver .log and post as an attachment.
@Enisey: fyi with 1 DS4 connected to my i7-2700K : ScpService uses 0.13%.
@JustinSaneV2: pressing the Reset button on your DS3 does not remove any Pairing which has been configured [the Paired MAC address is stored in non-volatile memory, serial e2prom iirc]. What it does do is remove power from the micro-controller and volatile memory, so that your DS3 starts up cleanly. Most common cause for erratic behaviour of a DS3 is that the firmware/volatile-memory has become corrupted, pressing the Reset button generally cures these issues.
Your issue is caused by the DS3 becoming disconnected from USB. There can be a few causes for this -
1. DS3 has become flaky (as above) - try a pin-hole reset.
2. Dodgy USB cable - verify your cable on another device, try another cable.
3. Dodgy USB Port/Hub - verify with another device, try a different port/hub.
4. Power draw on your USB Hub has exceeded it's capabilities [causes the USB Hub to lock up] - try to move your DS3 to a hub with no other devices attached.
I would hazard a guess that you are experiencing issue 4. Be aware that DS3s can draw a lot of power, especially during Rumble and Charging.
Non-Rev DS3 -> 5V, 500mA
A1 Rev DS3 -> 3.7V, 300mA
SixAxis -> 3.7V, 30mA
X360 Wired -> 5V, 400mA
So a Non-Rev DS3 has the highest potential power draw. Can you try disabling Rumble in options and see if your issues persist.
@Sky-Dragon: I'm not aware of any such adaptors.
@mooyah:
@solarnoise: missing button presses / lag on Bluetooth is caused by dropped BTH packets, this is generally caused by signal interference / range exceeded. Make sure your Dongle is in a front Panel port as far away from other RF devices as possible, try to maintain direct line of sight between Dongle and Controller, don't move out of Range (within ~5m should be no issue on a DS3, ~3m on a DS4).
@Nyx:
@bangarangatang:
see above response to JustinSaneV2.
FYI. The majority of my games collection (barring PCSX2 games) are on Steam, including Dead Souls. I have never experienced an issue using either DS3 or DS4 with the drivers on any Steam game.
@r2rX: the X360 Controller will remain "plugged in" while the service is running. This is to allow for transparent switching between BTH <-> USB, and Idle Disconnect/Reconnect. In ScpMonitor you will see the Pad being put in Reserved mode.
To clear X360 Controllers just restart the service. Or you can set it to Manual and Start and Stop the service as required. Alternatively, you can Disable the service and use ScpServer as required.
@borbran: DS3 controllers are recognised by their Mac address, sounds like your 3rd party controller is not presenting a consistant Mac address. Can you reproduce your issue, then zip up your ScpService.log and post as an attachment.
@UlyssesSKrunk: can you do the following
1. Open an elevated command prompt [Runas Administrator]
2. cd C:\Temp [create C:\Temp first if you don't have it]
3. pnputil -e > pnputil.txt
4. Zip up pnputil.txt and post as an attachment.
@randito34: you have a fake controller [00:26:5C signature], please update to latest update. [will be posting 1.2.2.175 shortly]
@Hiazu: your dongle doesn't support Secure Simple Pairing (SSP), please update to latest update and Disable SSP in options. [will be posting 1.2.2.175 shortly]
@Mikhail0: does your controller support Rumble over BTH when connected to a PS3?
@x_berzerker: after installing just manually install the original drivers back on to your integrated BTH via Device Manager.
@Daytrader: yes, the drivers make your DS3 appear as an X360 controller.
@beachybed: start ScpService from the Service Control Manager. [Control Panel -> Administrative Tools -> Services]
Also check that the Windows Event Log service is running.
@Abcdude: yes, the drivers support both DS3 and DS4 controllers connected at the same time.
@z_JoShua_z: you have a fake controller [00:26:5C signature], please update to latest update. [will be posting 1.2.2.175 shortly]
@kenshinjeff: can you reproduce your issue, then zip up ScpService.log && ScpDriver .log and post as an attachment.
@Enisey: fyi with 1 DS4 connected to my i7-2700K : ScpService uses 0.13%.
@JustinSaneV2: pressing the Reset button on your DS3 does not remove any Pairing which has been configured [the Paired MAC address is stored in non-volatile memory, serial e2prom iirc]. What it does do is remove power from the micro-controller and volatile memory, so that your DS3 starts up cleanly. Most common cause for erratic behaviour of a DS3 is that the firmware/volatile-memory has become corrupted, pressing the Reset button generally cures these issues.
Your issue is caused by the DS3 becoming disconnected from USB. There can be a few causes for this -
1. DS3 has become flaky (as above) - try a pin-hole reset.
2. Dodgy USB cable - verify your cable on another device, try another cable.
3. Dodgy USB Port/Hub - verify with another device, try a different port/hub.
4. Power draw on your USB Hub has exceeded it's capabilities [causes the USB Hub to lock up] - try to move your DS3 to a hub with no other devices attached.
I would hazard a guess that you are experiencing issue 4. Be aware that DS3s can draw a lot of power, especially during Rumble and Charging.
Non-Rev DS3 -> 5V, 500mA
A1 Rev DS3 -> 3.7V, 300mA
SixAxis -> 3.7V, 30mA
X360 Wired -> 5V, 400mA
So a Non-Rev DS3 has the highest potential power draw. Can you try disabling Rumble in options and see if your issues persist.
@Sky-Dragon: I'm not aware of any such adaptors.
@mooyah:
Quote:@mooyah: to get Pressure Sensitive buttons enabled in PCSX2 do the following -
1. Copy <ScpServer>\bin\Win32\LilyPad-Scp-r5875.dll to your <pcsx2>\Plugins directory.
2. Copy <ScpServer>\bin\Win32\XInput1_3.dll to your <pcsx2> directory.
3. Make sure your DS3 is connected and active before starting PCSX2.
4. Configure your Pad plugin as per screenshot in Post #2613.
@solarnoise: missing button presses / lag on Bluetooth is caused by dropped BTH packets, this is generally caused by signal interference / range exceeded. Make sure your Dongle is in a front Panel port as far away from other RF devices as possible, try to maintain direct line of sight between Dongle and Controller, don't move out of Range (within ~5m should be no issue on a DS3, ~3m on a DS4).
@Nyx:
@bangarangatang:
see above response to JustinSaneV2.
FYI. The majority of my games collection (barring PCSX2 games) are on Steam, including Dead Souls. I have never experienced an issue using either DS3 or DS4 with the drivers on any Steam game.
@r2rX: the X360 Controller will remain "plugged in" while the service is running. This is to allow for transparent switching between BTH <-> USB, and Idle Disconnect/Reconnect. In ScpMonitor you will see the Pad being put in Reserved mode.
To clear X360 Controllers just restart the service. Or you can set it to Manual and Start and Stop the service as required. Alternatively, you can Disable the service and use ScpServer as required.
@borbran: DS3 controllers are recognised by their Mac address, sounds like your 3rd party controller is not presenting a consistant Mac address. Can you reproduce your issue, then zip up your ScpService.log and post as an attachment.