PS3 PS3XPAD v0.6 - Now Supporting (Wired) Xbox One & DualShock 4 Controllers

Here comes an impressive new update to the ps3Xpad plugin for PS3 CFW users, this plugin created by developer OsirisX comes with some new features with the release of version 0.6. Now Support has been added for XBOX ONE and DualShock 4 wired controllers. The developer has also added an Improved driver [break]sss[/break] for the DualShock 4 Controller over the official Sony one as noted in the developer's official release notes.

​

It is possible to remap six axis motion to different keys. I may make a release with this functionality at a later time.


ps3Xpad 0.6 Changes:

Added Xbox One (wired) controller and Playstation DualShock 4 (wired) controller support. Only wired connection for now, might add wireless support later on. The DualShock 4 controller driver enables rumble and six axis support. It also increases compatibility of some games over the official driver. There is no trackpad support in this release but may possibly be added later.


Note: DS4 six axis sensors were about 4 times more sensitive than DS3s. I had to reduce it's sensitivity to make PS3 games compatible with the six axis. Also DS4 controller PID/VIDs are not hardcoded. You will need to have them in xpad_devices.txt. This gives the option to switch between official and unofficial driver when using the xpad plugin.


The install procedure is the same as my previous release
ps3xpad_0.6.zip

Download: ps3xpad_0.6.zip

Source: PS3hax.net
​

 

[MENTION=46]haxxxen[/MENTION]

This just became my new favorite plugin!! Now I have my DS4 with 4.21.2 something I had dreamed about as I have been orn swapping from 4.21.2 Rebug REX Cobra 7.10 (unoffical but has some neat mods even the offical doesn't like the PSP save game fix implemented into a button combo) to Rebug 4.70.1 to make use of my DS4 as it is simply the best pad ever made. Its all I use for PSTV as well. Anyhow I had asked haxxxen if this was possible and he didn't think so without some heavy firmware modding. Why 4.21 you might ask yourself and it's simple. Its the first, last and only 4.xx CFW that properly supports the CU3 cheat dongle (yes I still dongle it up and the only DRM device I support as I don't use it online and it isn't a piracy circumvention dongle with DRM and I have no issues with them trying to protect their work. And yes I buy my games as we all know I have no data to pirate even if I wanted to do so, anywho) as I don't use RTM and Atremis has a way to go IMO while this just works and works quite well.

 

The next big thing this plugin could do it keyboard + mouse support

 

The next big thing this plugin could do it keyboard + mouse support

I would say X360 guitar, xbox controller 'S' and if blutooth is possible then wiiu pro controller

 

INCREDIBLE!

Keep up the good work!

 

Wireless DS4 and I'm set. But a nice long microUSB cable isnt that bad for now.

 

I would say X360 guitar, xbox controller 'S' and if blutooth is possible then wiiu pro controller

bluetooth is what the ps3 uses, so bluetooth controllers like pro controller r doable without a receiver.

 

bluetooth is what the ps3 uses, so bluetooth controllers like pro controller r doable without a receiver.

Yes, I know PS3 uses bluetooth but I think this plugin can only make use of USB devices and can't use the PS3 bluetooth module.

 

The plugin may consider a name change as it's supporting more controllers. It's nice to see this plugin evolve.. Nice work from the developer ..

 

Yes, I know PS3 uses bluetooth but I think this plugin can only make use of USB devices and can't use the PS3 bluetooth module.

it should be able to use them without a usb device. any device that doesn't use bluetooth, such as the 360 controller, cannot be operated without a receiver. it's technically impossible since the system doesn't contain the required hardware.

 

it should be able to use them without a usb device. any device that doesn't use bluetooth, such as the 360 controller, cannot be operated without a receiver. it's technically impossible since the system doesn't contain the required hardware.

the plugin doesn't touch any PS3 related bluetooth functions. maybe add a USB bluetooth dongle and pair with that?

 

Maybe someone could be interested in continue this experiment...

http://aldostools.org/temp/test/wmpad/main.c

I tried to integrate part of the code of ps3xpad into webMAN MOD to make it accept button commands (/pad.ps3?CROSS) via http server (like Movian does)...
Unfortunately I couldn't get it to work properly and I don't know what I'm doing wrong...

The related code is tagged as "VIRTUAL_PAD". Credits to OsirisX for the source code of ps3xpad.

 

the plugin doesn't touch any PS3 related bluetooth functions. maybe add a USB bluetooth dongle and pair with that?

This will probably be my second approach if I cannot get the internal bluetooth to work. Unfortunately there's not much documentation for it and seems $ony keeps its bluetooth stack locked down. Only HID compliant devices such as mouse and keyboards are allowed to connect through. It looks like syscalls 578 through 599 have to do with the bluetooth module but there's not much description for them according to ps3devwiki. I will have to reverse them myself to get other devices to connect. Most likely one of the syscalls is to register a device by PID/VID and another to register it's callback routines.

Maybe someone could be interested in continue this experiment...

http://aldostools.org/temp/test/wmpad/main.c

I tried to integrate part of the code of ps3xpad into webMAN MOD to make it accept button commands (/pad.ps3?CROSS) via http server (like Movian does)...
Unfortunately I couldn't get it to work properly and I don't know what I'm doing wrong...

The related code is tagged as "VIRTUAL_PAD". Credits to OsirisX for the source code of ps3xpad.

You're close. Right now you have it sending analog values for each button (0xFF or 0x00). I think most PS3 application respond only to digital values.

data.button[CELL_PAD_BTN_OFFSET_DIGITAL2] |= CELL_PAD_CTRL_CROSS; // cross button pressed
data.button[CELL_PAD_BTN_OFFSET_DIGITAL2] &= ~CELL_PAD_CTRL_CROSS; // cross button released

Button presses are mapped to DIGITAL2 offset while dpad presses map to DIGITAL1.

 

You're close. Right now you have it sending analog values for each button (0xFF or 0x00). I think most PS3 application respond only to digital values.

data.button[CELL_PAD_BTN_OFFSET_DIGITAL2] |= CELL_PAD_CTRL_CROSS; // cross button pressed
data.button[CELL_PAD_BTN_OFFSET_DIGITAL2] &= ~CELL_PAD_CTRL_CROSS; // cross button released

Button presses are mapped to DIGITAL2 offset while dpad presses map to DIGITAL1.

Thank you for your tips... I've added the flags to DIGITAL1 and DIGITAL2, but it still didn't work

Here is the updated src: http://aldostools.org/temp/test/wmpad/main.c

I tested it sending only digital values, digital+analog and with various delays between press/release (50ms, 250ms, 0.5s, 1s)

I have noticed that if xy values for analog sticks are initialized with 0, the XMB scrolls up.

 

[MENTION=89]aldostools[/MENTION] there is a very easy way to do what you want to do, You just have to poke in the lv2. Unfortunatly, I forgot details like offset and value for each. I found them with the one of the first sprx : a LV2viewer on the XMB release with prxloader (i forgot the name of the sprx).
(I'm telling you this but perhaps psxpad is working like this... I didn't take a look on it. ;p)

I wanted to do a soft to do some macro but I abandoned this project...

 

Thank you for your tips... I've added the flags to DIGITAL1 and DIGITAL2, but it still didn't work

Here is the updated src: http://aldostools.org/temp/test/wmpad/main.c

I tested it sending only digital values, digital+analog and with various delays between press/release (50ms, 250ms, 0.5s, 1s)

I have noticed that if xy values for analog sticks are initialized with 0, the XMB scrolls up.

Not exactly sure why button presses are not working. As for the x and y values, analog sticks are initialized to the middle coordinate (0x80, 0x80). (0x00, 0x00) points to top left. Up would be (0x80, 0x00) , left (0x00, 0x80), down (0x80, 0xff), and right (0xff, 0x80).

 

[MENTION=89]aldostools[/MENTION] there is a very easy way to do what you want to do, You just have to poke in the lv2. Unfortunatly, I forgot details like offset and value for each. I found them with the one of the first sprx : a LV2viewer on the XMB release with prxloader (i forgot the name of the sprx).
(I'm telling you this but perhaps psxpad is working like this... I didn't take a look on it. ;p)

I wanted to do a soft to do some macro but I abandoned this project...

Basically I wanted to adapt the Movian Remote so it can be used with XMB, IRISMAN, multiMAN, etc... but I guess I'll have to abandon this idea too.

 

When plugin loaded and i go into PSone/PS2 card manager system freezes when i quit of them.

Sent from my I9300 using Tapatalk

 

Basically I wanted to adapt the Movian Remote so it can be used with XMB, IRISMAN, multiMAN, etc... but I guess I'll have to abandon this idea too.

Why abandon? I was without a ps3 for a week so couldn't test the remote feature. Your version seems to work for the most part besides the ps button being registered everytime. I think strstr finds "ps" in "pad.ps3". I changed it to psbtn to make the variable more unique. I aslo added in the analog sticks and changed the delay to 70ms since analog movements weren't being registered quick enough. This was tested on Rebug 4.75 with cobra enabled.

main.c

When plugin loaded and i go into PSone/PS2 card manager system freezes when i quit of them.

Can you explain which card manager you're referring to? Is it freezing when you quit card manager from XMB or are you using the ingame card manager.

 

Can you explain which card manager you're referring to? Is it freezing when you quit card manager from XMB or are you using the ingame card manager.

In XMB manager, i can post log from target manager if you need.



Sent from my I9300 using Tapatalk