..:: PCSX2 Forums ::..

I got most of this working fairly easily, except for one part. The controller connects, is shown in SCPMonitor, the profile shows all the pressure sensitive inputs working, and all of that is fine. The problem I'm having is that the supplied Xinput1_3.dll causes PCSX2 (and other things, like SCPUser.exe) to crash. I've downloaded the source and visual studio to try and figure out what I can and it seems that it's having an issue getting the device path (as shown in the attachment). Unfortunately, I don't actually know C++, or anything to do with windows, hid, or anything hardware like this so I don't think I can go much further than this. Any suggestions would be most appreciated.

(It should be noted that the basic xinput functionality works fine, without the scp xinput everything picks up the controller actions fine, but there is no pressure sensitive input.)

Scratch that, with some snooping around the xinput memory and googling some hardware id's I figured out that the first one was the Leap Motion controller. For some reason it was causing problems. Uninstalling the software suite for the device fixed the issue, and now the xinput dll works flawlessly, pressure sensitive inputs and all.

(10-13-2014, 01:54 AM)dudoz0r Wrote: [ -> ]I have a few issues

1. The controller sometimes changes from pad 1 to pad 2 for no reason. Some games no longer recognize it and I lose my custom keybinds in emulators and games. I get 2 Xbox360 controller icons in my Peripherals folder and my SCP monitor indicates that "pad 1" is reserved with the address 00:00:00:00:00:00

2. The controller is only recognized when connected via bluetooth. When connected via USB, it still charges, but the lights either won't come on or just keep blinking. It also works with motionInJoy via USB and I get an Icon in my peripherals folder indicating that the controller is connected.

3. The controller randomly disconnects. I suspect the issue is unrelated to SCPDriver itself since I had the same issue with motionInJoy, but it has never happened when connected to my PS3. It happens both via Bluetooth and USB.

Notes:
I uninstalled the motionInJoy drivers as per the instructions on this page: http://emulation-general.wikia.com/wiki/...structions

Thank you for your help!

I would suggest you uninstall everything and start from scratch. Make sure you uninstalled MotioninJoy correctly, because it re-installs itself if you don't do it in a very specific way. Check out my thread for some more info on how to get everything setup:
http://forums.pcsx2.net/Thread-VIDEO-TUT...CP-drivers

(10-13-2014, 05:01 AM)Theowningone Wrote: [ -> ]Scratch that, with some snooping around the xinput memory and googling some hardware id's I figured out that the first one was the Leap Motion controller. For some reason it was causing problems. Uninstalling the software suite for the device fixed the issue, and now the xinput dll works flawlessly, pressure sensitive inputs and all.

Glad to see that you figured out the problem on your own. Impressive snooping! Quick question though, what pressure sensitive inputs were you looking to use that the regular XInput.dll didn't deliver? I don't know if I just don't play games that require it or I just never noticed but I've never felt the need to use the included XInput1_3.dll file.

(10-10-2014, 04:24 PM)karasuhebi Wrote: [ -> ]Yes, rumble works over Bluetooth.

I doesn't work to me over Bluetooth, it does with cable.
What is wrong?

When you go into the LilyPad settings and click on 'Pad1', do you have rumble turned on? It should be called 'Constant Effect' under the 'PC Control' column and 'Big Motor' (and 'Small Motor') under the 'PS2 Control' column. If those are there, click on one of them (while your DS3 is connected via Bluetooth) and click on the 'Test' button. Does that work?

(10-13-2014, 05:19 AM)karasuhebi Wrote: [ -> ]I would suggest you uninstall everything and start from scratch. Make sure you uninstalled MotioninJoy correctly, because it re-installs itself if you don't do it in a very specific way. Check out my thread for some more info on how to get everything setup:
http://forums.pcsx2.net/Thread-VIDEO-TUT...CP-drivers

Turns out I had an outdated version installed, which was my bad. I did everything you mentionned, but I still cannot get the controller working via USB. At least now the new SCPMonitor lets me switch the slot of my controller, which solves my first issue.

Here's a screenshot of what I get:

The monitor indicates that the controller is plugged in, but I cannot use it at all. If I plug it without having connected it via bluetooth beforehand, it doesn't get detected at all. The DS3 address remains, but I get "reserved" as the status instead

Are you sure you uninstalled the MotioninJoy drivers correctly? You shouldn't be seeing 'PLAYSTATION®3 Controller' anymore. Try following the instructions quoted in the bottom of my post to make sure you did it correctly. MotioninJoy tends to re-install itself if you do it incorrectly.

My guess is that the MotioninJoy drivers are somehow impeding the SCP USB drivers from installing correctly, which is why you can only use your DS3 over Bluetooth.

I've installed everything and the controller was working fine on BT, but the signal would go in and out. I charged the controller and moved my new BT dongle to the front of my HTPC. I then reinstalled everything and the controller worked perfectly all day. The next day I started up the PC again and the signal from the controller gradually degraded until I couldn't use it at all. I did everything I did the day before - took out and reinserted the dongle - reinstalled the wrapper etc. Still just get crappy reception. Unless there is something obvious I'm overlooking, I'm probly going to give up on this.

Hi guys. My controller connect through time with bt dongle and with usb all good. Maybe someone knows how to fix it?

So I have been setting up my retro emulation box(an old laptop connected to a CRT, OS is Windows XP Professional SP3) and I was using my DS3 with the wrappers here as controller. All was well until Windows Update. Since then, they simply will not work. I've tried uninstalling/reinstalling a million times in every different order possible. I've tried manually starting the SCP DS3 service and I get "The service started and then stopped. Some services stop when they have no work to do." I even tried a system restore to before the update and problem, but no luck.

I'm currently using Better DS3 + MiJ but I'd really rather not. Any ideas?