05-02-2013, 09:18 PM
@king_dick:
@hugo19941994:
added your hardware ids, see Post #639.
@crap13: just keep doing Uninstall (delete) / Scan, eventually you will get to the default Bluetooth driver.
@Mahrahia: copy bin\Win32\XInput1_3.dll to your PCSX2 directory (this provides the pressure extensions), copy bin\Win32\LilyPad-Scp-r5350.dll to your PCSX2\plugins directory (or Pokopom). Make sure your DS3 is connected and active before starting PCSX2. If your using Lilypad select LilyPad-Scp-r5350.dll as your pad plugin, configure as per screenshot.
@GenericHero: I think the issue is your controller, sounds like it is not a genuine Sony DS3. When a game sends out rumble commands it does so by sending out a series of rumble commands at a high rate to give the effect it requires (usually a ramped effect). It sounds like your controller can't handle the frequency of these rumble commands.
I test the drivers with my non-rev DS3s and Rev A1 DS3s using PCSX2 and Onimusha 2, which is very demanding (20ms between rumble commands) and have never seen the issue you are having. Nobody else has reported it either. You wont see the problem with SCPUser since it is not really possible to move the rumble sliders fast enough manually.
@soyo: haven't come across this myself, can't think of anything specific that could be causing it. Could try re-seating data / power connections, possibly moving the usb card to a different expansion slot.
@DeclanRand: the drivers don't support disabling rumble as this is a standard feature of X360 controllers.
@OminaeYu: nope, you can't blacklist Bluetooth adapters. You could remove hardware ids from the inf file, but this will leave the package as unsigned.
@hugo19941994:
added your hardware ids, see Post #639.
@crap13: just keep doing Uninstall (delete) / Scan, eventually you will get to the default Bluetooth driver.
@Mahrahia: copy bin\Win32\XInput1_3.dll to your PCSX2 directory (this provides the pressure extensions), copy bin\Win32\LilyPad-Scp-r5350.dll to your PCSX2\plugins directory (or Pokopom). Make sure your DS3 is connected and active before starting PCSX2. If your using Lilypad select LilyPad-Scp-r5350.dll as your pad plugin, configure as per screenshot.
@GenericHero: I think the issue is your controller, sounds like it is not a genuine Sony DS3. When a game sends out rumble commands it does so by sending out a series of rumble commands at a high rate to give the effect it requires (usually a ramped effect). It sounds like your controller can't handle the frequency of these rumble commands.
I test the drivers with my non-rev DS3s and Rev A1 DS3s using PCSX2 and Onimusha 2, which is very demanding (20ms between rumble commands) and have never seen the issue you are having. Nobody else has reported it either. You wont see the problem with SCPUser since it is not really possible to move the rumble sliders fast enough manually.
@soyo: haven't come across this myself, can't think of anything specific that could be causing it. Could try re-seating data / power connections, possibly moving the usb card to a different expansion slot.
@DeclanRand: the drivers don't support disabling rumble as this is a standard feature of X360 controllers.
@OminaeYu: nope, you can't blacklist Bluetooth adapters. You could remove hardware ids from the inf file, but this will leave the package as unsigned.
