XInput Wrapper for DS3 and Play.com USB Dual DS2 Controller
As far as I know, you shouldn't have to do anything special to dolphin, other than setting the controller input configuration in the dolphin program itself. I didn't do anything else, personally. But I'd say give Krossx's suggestion a shot, placing the xinput DLL file in the same directory as dolphin.

Edit: I have attached two images for MikeZilla to look at. First you can look to see what is in my directory for Dolphin for comparison. Second is the controller window. I highlighted the version of Dolphin, the GCPad button (you can edit controller inputs for Wii as well, just Gamecube pad is more like a controller than a wii remote) and the device listed showing up in my settings. Smile


Attached Files Thumbnail(s)
       

Sponsored links

You're probably using the latest alpha versions with native XInput support, which wouldn't require any DLL.

@Scarlet.Crush: Latest Pokopom added the undocumented XInput functions. Might crash with the wrapper for pressure support. Better just include the function in the plugin itself to avoid the usage of the wrapper altogether? Specially considering your latest versions.
[Image: nbKSK.jpg]
(01-27-2013, 07:20 PM)KrossX Wrote: Just try and put it DLL alongside the main EXE, and during input setup select "XInput". That should do the trick I think. Unless using the latest version with native XInput, then just select XInput when mapping the controls.

latest version with native Xinput ? - are you srue we are all on the same page here about what im trying to achieve ?
@KrossX: I'm easy, if you want to avoid using the wrapper feel free to reuse any of the source for it. If you have any questions or need any testing done, just give me a shout.
@Scarlet.Crush:

I went for the easy way, just a wrapper update. XD

Added the new functions, and works fine for X360 controllers. Now the dualshock controllers can report the guide button, but didn't know how to add that. Would end up on wButtons at 0x400.

If this is becoming more like a driver, would it be possible to expose the pressure functions from the driver directly?

@mikezilla2

You're trying to use your DualShock on Dolphin. Then you posted about dropping something into Dolphin's folder. Right?

If using the old version you put the wrapper in there, if not, then you put nothing in there. Then, just select XInput when mapping the controller on Dolphin. And yes, your DualShock controller will be an X360 controller for Dolphin.

Though I dunno why would you need it for Dolphin though, since it can use DInput just fine. O.o


Attached Files
.zip   SCP_Wrapper_32bits.zip (Size: 21,68 KB / Downloads: 215)
[Image: nbKSK.jpg]
Kross mate hold the phone - Diinput ? you refering to keyboard support ? no - my DS3 works in delphin with out a hich - wasint the case a few pages ago but thats all fixed my recent post is regarding that fact that before via USB windows picked up my DS3 as a ps3 controller and so did delphin over usb - not blutooth , the version that scar made for me - is cool but like wise my post details windows thinks im using a 360 controller so there for delphin thinks so to - in doing so it also thinks the buttons are xbox buttons my post was asking for ways that i might fool delphin in to thinking that i am infact using a DS3 ( which i am ) so that the buttons will match up better - i understand how the software works in that yea its faking a 360 controller so yea - pretty much what i said

dropping thinks in folders: just asked if doing so would make a difference
yes, that is how Scarlett's DS3 wrapper works. The thing is, even if Dolphin sees the playstation 3 controller via usb, because there are no actual drivers for it, dolphin should not be able to see any input from the DS3 controller itself, but rather the xbox controller it is emulating. I just checked this with my DS3 connected via usb, and I do not see it in dolphin. It seems to me that around the time you were having the issue, you were asking about removing motioninjoy drivers. It could be that the motioninjoy drivers were still being seen by dolphin, hence why you were able to see the Playstation 3 controller in devices under input. I believe motioninjoy drivers are actual DS3 controller drivers, at least to some extent, which allows motioninjoy to change different modes. The xbox 360 emulation in motioninjoy is a sort of wrapper as well, I think. But anyways, since there isn't any real actual DS3 driver with Scarlett's wrapper, I think that's why you were seeing playstation 3 controller in dolphin before, but not now.

EDIT: When I say Scarlett's Wrapper isn't a driver, I mean I don't think it is a driver in the same way as motioninjoy.

Anyone please feel free to correct me if im wrong. I'm not very technical at this sort of stuff, haha. Its just my assumption. Smile
Ok I managed to get the app that is in alpha to work while my DS3 is plugged in via usb but I am trying to get it to work via bluetooh so I can sit farther away then my usb cable is able to strech. If I am following your instructions correctly your service should auto pair my active bluetooth adapter and DS3 when I plug the DS3 in correct? It shows for a split second in my bluetooth devices window but then vanishes when I plug the cable in so its seeing it then just automatically dissconnecting the DS3 for some reason. I am running windows 7 64bit here like I said it works perfectly fine via usb cable.
@Topken: can you post the ScpService.log file.
Yup here you go Scarlet

Code:
1/29/2013 3:14:59 AM.753 ++ C:\Users\Andrew\Downloads\ScpServer-0.6.0.93\ScpServer\bin\ScpService.exe 0.6.0.93
1/29/2013 3:14:59 AM.761 ++ C:\Users\Andrew\Downloads\ScpServer-0.6.0.93\ScpServer\bin\ScpControl.dll 0.6.0.93
1/29/2013 3:14:59 AM.807 ++ Microsoft Windows 7 Home Premium Service Pack 1 (6.1.7601.65536 AMD64)
1/29/2013 3:14:59 AM.908 -- Controller : UDP_Worker_Thread Starting
1/29/2013 3:15:20 AM.157 ++ Notify [Removal] [{E2824A09-DBAA-4407-85CA-C8E8FF5F6FFA}] [\\?\USB#VID_054C&PID_0268#5&2C82CF20&0&3#{E2824A09-DBAA-4407-85CA-C8E8FF5F6FFA}]
1/29/2013 3:15:20 AM.159 -- Device Removal [60:38:0E:75:F2:3C]
1/29/2013 3:15:25 AM.931 ++ Notify [Arrival] [{E2824A09-DBAA-4407-85CA-C8E8FF5F6FFA}] [\\?\USB#VID_054C&PID_0268#5&2C82CF20&0&3#{E2824A09-DBAA-4407-85CA-C8E8FF5F6FFA}]
1/29/2013 3:15:26 AM.029 -- Device Arrival [60:38:0E:75:F2:3C]
1/29/2013 3:15:30 AM.536 ++ Notify [Removal] [{E2824A09-DBAA-4407-85CA-C8E8FF5F6FFA}] [\\?\USB#VID_054C&PID_0268#5&2C82CF20&0&3#{E2824A09-DBAA-4407-85CA-C8E8FF5F6FFA}]
1/29/2013 3:15:30 AM.538 -- Device Removal [60:38:0E:75:F2:3C]
1/29/2013 3:16:29 AM.755 -- Received : Status Request [127.0.0.1:50766]
1/29/2013 3:17:04 AM.384 ++ Notify [Arrival] [{E2824A09-DBAA-4407-85CA-C8E8FF5F6FFA}] [\\?\USB#VID_054C&PID_0268#5&2C82CF20&0&3#{E2824A09-DBAA-4407-85CA-C8E8FF5F6FFA}]
1/29/2013 3:17:04 AM.411 -- Device Arrival [60:38:0E:75:F2:3C]
1/29/2013 3:17:09 AM.266 ++ Notify [Removal] [{E2824A09-DBAA-4407-85CA-C8E8FF5F6FFA}] [\\?\USB#VID_054C&PID_0268#5&2C82CF20&0&3#{E2824A09-DBAA-4407-85CA-C8E8FF5F6FFA}]
1/29/2013 3:17:09 AM.269 -- Device Removal [60:38:0E:75:F2:3C]
1/29/2013 3:17:11 AM.284 ++ Notify [Arrival] [{E2824A09-DBAA-4407-85CA-C8E8FF5F6FFA}] [\\?\USB#VID_054C&PID_0268#5&2C82CF20&0&3#{E2824A09-DBAA-4407-85CA-C8E8FF5F6FFA}]
1/29/2013 3:17:11 AM.312 -- Device Arrival [60:38:0E:75:F2:3C]
1/29/2013 3:17:19 AM.976 -- Received : Status Request [127.0.0.1:50730]
1/29/2013 3:17:28 AM.808 -- Received : Status Request [127.0.0.1:49467]
1/29/2013 3:18:16 AM.015 ++ Notify [Removal] [{E2824A09-DBAA-4407-85CA-C8E8FF5F6FFA}] [\\?\USB#VID_054C&PID_0268#5&2C82CF20&0&3#{E2824A09-DBAA-4407-85CA-C8E8FF5F6FFA}]
1/29/2013 3:18:16 AM.017 -- Device Removal [60:38:0E:75:F2:3C]
1/29/2013 3:18:22 AM.388 ++ Notify [Arrival] [{E2824A09-DBAA-4407-85CA-C8E8FF5F6FFA}] [\\?\USB#VID_054C&PID_0268#5&2C82CF20&0&3#{E2824A09-DBAA-4407-85CA-C8E8FF5F6FFA}]
1/29/2013 3:18:22 AM.515 -- Device Arrival [60:38:0E:75:F2:3C]
1/29/2013 3:18:36 AM.227 ++ Notify [Removal] [{E2824A09-DBAA-4407-85CA-C8E8FF5F6FFA}] [\\?\USB#VID_054C&PID_0268#5&2C82CF20&0&3#{E2824A09-DBAA-4407-85CA-C8E8FF5F6FFA}]
1/29/2013 3:18:36 AM.230 -- Device Removal [60:38:0E:75:F2:3C]
1/29/2013 3:18:39 AM.189 ++ Notify [Arrival] [{E2824A09-DBAA-4407-85CA-C8E8FF5F6FFA}] [\\?\USB#VID_054C&PID_0268#5&2C82CF20&0&3#{E2824A09-DBAA-4407-85CA-C8E8FF5F6FFA}]
1/29/2013 3:18:39 AM.226 -- Device Arrival [60:38:0E:75:F2:3C]
1/29/2013 3:25:17 AM.407 ++ Notify [Removal] [{E2824A09-DBAA-4407-85CA-C8E8FF5F6FFA}] [\\?\USB#VID_054C&PID_0268#5&2C82CF20&0&3#{E2824A09-DBAA-4407-85CA-C8E8FF5F6FFA}]
1/29/2013 3:25:17 AM.409 -- Device Removal [60:38:0E:75:F2:3C]
1/29/2013 3:25:27 AM.812 ++ Notify [Arrival] [{E2824A09-DBAA-4407-85CA-C8E8FF5F6FFA}] [\\?\USB#VID_054C&PID_0268#5&2C82CF20&0&3#{E2824A09-DBAA-4407-85CA-C8E8FF5F6FFA}]
1/29/2013 3:25:27 AM.851 -- Device Arrival [60:38:0E:75:F2:3C]
1/29/2013 3:25:31 AM.226 ++ Notify [Removal] [{E2824A09-DBAA-4407-85CA-C8E8FF5F6FFA}] [\\?\USB#VID_054C&PID_0268#5&2C82CF20&0&3#{E2824A09-DBAA-4407-85CA-C8E8FF5F6FFA}]
1/29/2013 3:25:31 AM.229 -- Device Removal [60:38:0E:75:F2:3C]
1/29/2013 3:25:36 AM.813 ++ Notify [Arrival] [{E2824A09-DBAA-4407-85CA-C8E8FF5F6FFA}] [\\?\USB#VID_054C&PID_0268#5&2C82CF20&0&3#{E2824A09-DBAA-4407-85CA-C8E8FF5F6FFA}]
1/29/2013 3:25:36 AM.853 -- Device Arrival [60:38:0E:75:F2:3C]
1/29/2013 3:25:37 AM.100 ++ Notify [Removal] [{E2824A09-DBAA-4407-85CA-C8E8FF5F6FFA}] [\\?\USB#VID_054C&PID_0268#5&2C82CF20&0&3#{E2824A09-DBAA-4407-85CA-C8E8FF5F6FFA}]
1/29/2013 3:25:37 AM.102 -- Device Removal [60:38:0E:75:F2:3C]
1/29/2013 3:25:38 AM.013 ++ Notify [Arrival] [{E2824A09-DBAA-4407-85CA-C8E8FF5F6FFA}] [\\?\USB#VID_054C&PID_0268#5&2C82CF20&0&3#{E2824A09-DBAA-4407-85CA-C8E8FF5F6FFA}]
1/29/2013 3:25:38 AM.049 -- Device Arrival [60:38:0E:75:F2:3C]
1/29/2013 3:25:38 AM.578 ++ Notify [Removal] [{E2824A09-DBAA-4407-85CA-C8E8FF5F6FFA}] [\\?\USB#VID_054C&PID_0268#5&2C82CF20&0&3#{E2824A09-DBAA-4407-85CA-C8E8FF5F6FFA}]
1/29/2013 3:25:38 AM.581 -- Device Removal [60:38:0E:75:F2:3C]
1/29/2013 3:26:19 AM.715 ++ Notify [Arrival] [{E2824A09-DBAA-4407-85CA-C8E8FF5F6FFA}] [\\?\USB#VID_054C&PID_0268#5&2C82CF20&0&3#{E2824A09-DBAA-4407-85CA-C8E8FF5F6FFA}]
1/29/2013 3:26:19 AM.754 -- Device Arrival [60:38:0E:75:F2:3C]
1/29/2013 3:27:43 AM.186 -- Received : Status Request [127.0.0.1:65161]
1/29/2013 3:29:50 AM.752 -- Received : Status Request [127.0.0.1:65019]
1/29/2013 3:30:29 AM.992 -- Received : Status Request [127.0.0.1:63930]
1/29/2013 3:31:33 AM.641 -- Received : Status Request [127.0.0.1:64562]
1/29/2013 3:32:31 AM.750 -- Received : Status Request [127.0.0.1:49405]
1/29/2013 3:33:13 AM.859 ++ Notify [Removal] [{E2824A09-DBAA-4407-85CA-C8E8FF5F6FFA}] [\\?\USB#VID_054C&PID_0268#5&2C82CF20&0&3#{E2824A09-DBAA-4407-85CA-C8E8FF5F6FFA}]
1/29/2013 3:33:13 AM.861 -- Device Removal [60:38:0E:75:F2:3C]
1/29/2013 3:33:29 AM.087 ++ Notify [Arrival] [{E2824A09-DBAA-4407-85CA-C8E8FF5F6FFA}] [\\?\USB#VID_054C&PID_0268#5&2C82CF20&0&3#{E2824A09-DBAA-4407-85CA-C8E8FF5F6FFA}]
1/29/2013 3:33:29 AM.124 -- Device Arrival [60:38:0E:75:F2:3C]
1/29/2013 3:34:14 AM.035 ++ Notify [Removal] [{E2824A09-DBAA-4407-85CA-C8E8FF5F6FFA}] [\\?\USB#VID_054C&PID_0268#5&2C82CF20&0&3#{E2824A09-DBAA-4407-85CA-C8E8FF5F6FFA}]
1/29/2013 3:34:14 AM.037 -- Device Removal [60:38:0E:75:F2:3C]

by the way PCSX2 crashes when I try to open your modified lilypad plugin with the XInput1_3.dll from the 32bit folder in the same folder as PCSX2.exe which I would assume is where I need to put the file to get xinput working for the plugin int he first place to get the DS3 working. I can get the DS3 working int he test program you supplied no problem when the DS3 is plugged in via USB cable but the USB cable is to short hence my need for bluetooth.




Users browsing this thread: 25 Guest(s)