Thread Rating:
  • 54 Vote(s) - 4.76 Average
  • 1
  • 2
  • 3
  • 4
  • 5
XInput Wrapper for DS3 and Play.com USB Dual DS2 Controller
(08-09-2015, 02:40 AM)Dorque Wrote: That can't be it, unless you've been mucking around somewhere. That is same as the VID and PID of the official wired Xbox 360 Controller that I have.
[Image: jvUgokx.png]
Well I did try getting it to work with Zadig.exe, using Dualshock3.cfg and trying things that way, so that may have something to do with it. Found the listing specific to my piece of hardware, though, it does match up with your adapter.
Reply

Sponsored links

(08-09-2015, 03:07 AM)asmcint Wrote: Well I did try getting it to work with Zadig.exe, using Dualshock3.cfg and trying things that way, so that may have something to do with it. Found the listing specific to my piece of hardware, though, it does match up with your adapter.

I guess you can give the xinput1_3.dll files a try. Can't guarantee anything, but the files are here: https://github.com/Dorque/ScpServer/rele...10_VID0001

Just place the right one in your game directory (32 bit or 64 bit). I believe most games are 32 bit. You can test your controllers by opening SCPUser.exe first.
Reply
(08-09-2015, 03:18 AM)Dorque Wrote: I guess you can give the xinput1_3.dll files a try. Can't guarantee anything, but the files are here: https://github.com/Dorque/ScpServer/rele...10_VID0001

Just place the right one in your game directory (32 bit or 64 bit). I believe most games are 32 bit. You can test your controllers by opening SCPUser.exe first.

Tried using with Shadow of Mordor(64 bit game, thus used 64 bit version). SCPUser.exe threw an error saying that MSVCP120.dll is missing from my computer, and Shadow of Mordor, as usual, did not recognize any input from my device. Tried using with Fable Anniversary(32 bit game, thus used 32 bit version), and had a bit more success. The same error was thrown both on launching SCPUser.exe and on launching the game itself. When this error occurs the program throwing it does not launch correctly/at all.
Reply
(08-09-2015, 01:14 AM)xeo84 Wrote: Anybody has the problem that it works fine over bluetooth, but it stops working when plugging the usb cable?

I've an original DS3 and I followed all the instructions, I can use it over bluetooth with no issues, but when the battery dies and I plug the usb cable it stops working.
After plugging the cable, the SCP monitor display "charging" for few seconds, then the number stops and a device with all 00 as mac address jump in and everything stops.

Any help?


I'm actually having the opposite problem. I've read through the majority of this thread and tried the new control from post 1864 but still no go.

My USB works fine but when I disconnected from the cable  it shows reserved for a moment like it should but ultimately gets stuck at BTH 00000000 None.

I think the hardware ID for my BT adapter is VID_0CF3&PID_3002, it's an ASUS adapter. This one worked with MotionInJoy but there's no doubt SCP is way better.
The other BTH DS3 Device ID is VID_0A12&PID_0001 but I think that's my controller.

@Nefarius Thanks a bunch for taking this over, I really hope you can keep improving this great tool. I just saw the updated version you put out for Windows 10 so my question is have you added more bluetooth adapter support like I saw SC do earlier in the thread? Or was what he added only to get it working when you install the driver and my adapter is just no good for how this communicates with the controller?
Reply
(08-09-2015, 03:32 AM)asmcint Wrote: Tried using with Shadow of Mordor(64 bit game, thus used 64 bit version). SCPUser.exe threw an error saying that MSVCP120.dll is missing from my computer, and Shadow of Mordor, as usual, did not recognize any input from my device. Tried using with Fable Anniversary(32 bit game, thus used 32 bit version), and had a bit more success. The same error was thrown both on launching SCPUser.exe and on launching the game itself. When this error occurs the program throwing it does not launch correctly/at all.

Ah right, you need those required stuff on the first post.

Copy and paste:
Quote:Requirements
1. Microsoft .NET 4.0
2. Visual C 2013 Runtime.
3. Latest DirectX Runtime.
4. Latest Xbox 360 Controller Drivers available.
5. Genuine Sony DualShock3 or DualShock4 or SixAxis Controller(s).
6. Minimum of Bluetooth 2.0 + EDR Dongle (if using Bluetooth).
7. Administrator rights on your PC.

Go download Visual C++ 2013 Runtime here: https://www.microsoft.com/en-us/download...x?id=40784
Xbox 360 Drivers are here: https://www.microsoft.com/hardware/en-us...or-windows
If these links don't work you can always Google for them as well.
Reply
(08-09-2015, 03:36 AM)Dorque Wrote: Ah right, you need those required stuff on the first post.

Copy and paste:

Go download Visual C++ 2013 Runtime here: https://www.microsoft.com/en-us/download...x?id=40784
Xbox 360 Drivers are here: https://www.microsoft.com/hardware/en-us...or-windows
If these links don't work you can always Google for them as well.

Okay, turns out I specifically was missing Visual C++ Runtime, had a bunch of older versions but not 2013. So now that's working, but my device is unrecognized, likely due to my previous driver tampering. So the next question is, how do I undo the tampering I performed with zadig.exe?
Reply
(08-09-2015, 03:59 AM)asmcint Wrote: Okay, turns out I specifically was missing Visual C++ Runtime, had a bunch of older versions but not 2013. So now that's working, but my device is unrecognized, likely due to my previous driver tampering. So the next question is, how do I undo the tampering I performed with zadig.exe?

Haha I can't help you there.

Edit: I did find a source that says all you need to do is delete that device in device manager.
https://github.com/pbatard/libwdi/issues/8
Reply
Hey, Nefarius, since you've taken over and the thread is stupidly long, why not move to a new one?
Reply
(08-08-2015, 09:57 PM)Nefarius Wrote: Oooops, my bad! I added the missing files to the Repository, please pull the latest changes.

To build ScpUser you also need an environment variable WindowsSDK which points to the installation folder of the Windows SDK like so:

[Image: 08-08-_2015_21-54-59.png]

Thank you, definitely got a lot farther.  Both ScpUser.sln and ScpServer.sln build now.  When I try to run ScpDriver.exe I get these messages in the installer window:

8/8/2015 10:06:28 PM [INFO] - SCP Driver Installer 1.4.5698.37870 [08/08/2015 22:06:28]

8/8/2015 10:06:29 PM [INFO] - Microsoft Windows 8.1 (6.2.9200.0 AMD64) detected
8/8/2015 10:06:29 PM [INFO] - Selected Win81 configuration
8/8/2015 10:06:38 PM [INFO] - ENTER:  DriverPackageInstallW
8/8/2015 10:06:38 PM [ERROR] - Could not open file C:\Users\fdavison\Downloads\ScpServer-master\bin\System\ScpVBus.inf.
8/8/2015 10:06:38 PM [INFO] - RETURN: DriverPackageInstallW  (0x3)
8/8/2015 10:06:38 PM [INFO] - ENTER:  DriverPackageInstallW
8/8/2015 10:06:38 PM [ERROR] - Could not open file C:\Users\fdavison\Downloads\ScpServer-master\bin\System\Ds3WinUsb.inf.
8/8/2015 10:06:38 PM [INFO] - RETURN: DriverPackageInstallW  (0x3)
8/8/2015 10:06:38 PM [INFO] - Install Succeeded.
8/8/2015 10:06:38 PM [INFO] - -- Install Summary --

...and those inf files are missing from the folder I'm testing in. 
I also noticed that in my bin folder I am missing the sub-directories: System and Win64 and have an extra one: DIFxAPI.

Fred
Reply
(08-09-2015, 01:20 AM)haximusprime Wrote: [Image: IpHNlbc.png]


Nefarious, thank you so much for working through this issue with me. I will be sure to donate in the future to keep this project alive. short question: I am interested in turning off DS4 front LED after it is properly connected (during play). But it looks to not be implemented yet? "Disable LED" is for DS3
[Image: NvBJhcv.png]

Glad to hear it's working now Laugh

Yes, disabling the light bar isn't implemented yet. Putting it on the To-Do list.

(08-09-2015, 03:35 AM)AdamBritt Wrote: I'm actually having the opposite problem. I've read through the majority of this thread and tried the new control from post 1864 but still no go.

My USB works fine but when I disconnected from the cable  it shows reserved for a moment like it should but ultimately gets stuck at BTH 00000000 None.

I think the hardware ID for my BT adapter is VID_0CF3&PID_3002, it's an ASUS adapter. This one worked with MotionInJoy but there's no doubt SCP is way better.
The other BTH DS3 Device ID is VID_0A12&PID_0001 but I think that's my controller.

@Nefarius Thanks a bunch for taking this over, I really hope you can keep improving this great tool. I just saw the updated version you put out for Windows 10 so my question is have you added more bluetooth adapter support like I saw SC do earlier in the thread? Or was what he added only to get it working when you install the driver and my adapter is just no good for how this communicates with the controller?

Take a peek into ScpControl.ini, I designed it to dynamically extend the devices used for DS communication. Don't hesitate to ask me if you need help with it's content.

(08-09-2015, 04:52 AM)Computermaster Wrote: Hey, Nefarius, since you've taken over and the thread is stupidly long, why not move to a new one?

Yeah, looks like a good idea, I'll prepare one Wacko
Reply




Users browsing this thread: 16 Guest(s)