However in that time period a Russian Scene site had found someone else's re-implementation (they forget to mention that) and patched worked together a toolset that looked like the real thing but it was hardly bguerville's original toolset nor did it offered the safety/quality or feature set of the real release. So instead of making various updates, one to support 4.89 and one for v1.2 new feature's it made sense for the project to have one testing session and release in a single update for 4.89 but that meant it a bit of delay for the deployment since proper testing needed to be conducted with v1.2 features. Now back to the official toolset update, behind the scene's prior to the 4.89 update the v1.2 update was near deployment. Now for those experienced CFW user's they knew they should wait and NOT UPDATE when a new firmware update goes live as those user's simply just waited for Evilnat's 4.89 Cobra CFW to be released. There are two ways of doing this but I will show one way.įollowing the firmware update of 4.89 the scene was awaiting an update to bguerville's PS3 Toolset so that CFW capable console who may of updated to 4.89 (or jailbreaking for the first time) can run the exploit and once again and be able to install CFW from 4.89. You only need to do this the first time you connect the controller to the bluetooth adapter. It should work for most generic adapters although I have only tested with one adapter.įirst we need to set the internal bluetooth address of the controller. Also note the bluetooth driver is based on the USB host shield for Arduino. This is for connecting the controller in custom mode with a BT adapter.
I will try making a more comprehensive guide to connecting a DualShock 4 controller later but here's a rough sketch. I recommend configuring the XPAD plugin through the VSH menu before starting a game and using the button combinations during the game. The In-Game menu only works for a handful of games anyway (games with low memory). These are also the requirements for the In-Game menu. The requirements for using native mode is you need CFW with DEX kernel and your game Eboots must be converted to debug. I only recommend using native mode if you want to connect your controller wirelessly and do not have a BT adapter. Native mode allows connecting official controllers using the internal BT module and give it the features of the XPAD plugin such as remapping. Custom mode still supports official PS controllers but will need a separate usb Bluetooth adapter to connect them wirelessly. This mode is needed for Xbox controllers but is not needed for official PS controllers. Custom mode is simply my implementation of the usb controller pad driver. I will first explain the difference between custom and native modes. The main focus of this release are the additions of two different modes (custom and native), the VSH/In-Game menu, and wireless support for DualShock 4 controllers. Added disconnect/reset all ports option.
Added auto game detection and attach to game proc.Added user configurable controller delay which sets response time of controller.Added user configurable settings file (xpad_settings.txt).Added game compatibility modes (fixes GTAV & RDR).Added wireless DS3/DS4 support (needs usb BT adapter).Added custom and native driver input mode.Fixed the remapping issues where the controller seemed buggy when it was enabled.Also I will be away from my main computer for the holidays and wanted to push a release before I left. I intended on adding a couple more features into this release but would have added more delay.
0 kommentar(er)
