![]() ![]() I play WIRELESSLY most of the time and only playing it wired when my controller has low charge.ĮDIT: Reading your first post, I noticed you have SCP drivers as well. I was using Motion-in-joy drivers (had no problems there except I have to run Better DS3 all the time) and switched to SCP drivers. I'm saying all of these because I've been using a PS3 controller to play MHFU on PPSSPP from the very beginning and I haven't noticed any weird thing happening. OR maybe there are more than 1 controls assigned to the right stick of your controller and they overtake each other, hence, it became "weird."Ī screenshot of your control mapping would be nice. If you really think your drivers aren't at fault, then maybe it's your PS3 controller that's broken. I dunno where you got your drivers but the only reliable ones I know for PS3 controllers are Motioninjoy and SCP. Though I can't remember which version I have.Įdit: Forgot to mention that only the D-pad button with the added Right analog keybinding is the one acting weird, the ones that are using the default mapping continue to work normally. Using the drivers I got from this place: (nvm, not allowed to post links, google: "XInput Wrapper for DS3 and USB Dual DS2 Controller") Tested it for 2 different games (Dissidia 012 and FF Type-0) with the same result/behavior. This issue occurs even if I for example map down right analog to the D-pad up (in addition, not replacement). Sometimes a button press is registered, sometimes not (like 30% chance) and holding the D-pad button never registers as holding it down (like for fast scrolling in game menus). I can map any controller key to anything.īUT if I try to map any of the Right analog (the ones not normally used) to any of the D-pad defaults, this happens Īnalog control is working as it should (holding up for example is like holding the D-pad up), but the D-pad controls get wierd. I'm using a PS3 controller with Xiput drivers. The second video also has some steps for the Wireless controller.Finally a thread with a similar issue to mine (feels related). You might want to check the links at the bottom to understand better some of the steps, however the guys do two things that I combined and made my controller working after 4 tedious hours and numerous dead-end research on the internet. ![]() Go in system preferences and go mess with your XBOX Controller while you'll joy with glee! Once you have done save the changes and drag and drop the file over the automator controller list installer.ġ3. You might want to check the second 'Thanks to' link at the bottom if this is getting confusing.ġ2. Insert in between those tags those number you wrote down earlier instead of those that are in the file. Open the Controller List file with a text editor and you look for Controller or look for other key tag that contains your device name, is irrelevant, but I edited under PDPAfterglow just because I have the Afterglow controller.ġ1. Click on it and in the box below you will see a Product and Vendor ID. If you use an original controller you might see it as vendor specific device. For me under USB High-speed bus, then Hub I had Afterglow gamepad. Connect your controller if you haven't done that yet and check under hardware, and the USB. Go in About This Mac on the menu, click more info and then system report. Download this Controller List Installer.Ĩ. ![]() It probably will say that it failed the installation but it will be installed.Ħ. Download TattieBogle 0.08 and install it. Drag and drop UnTattie file in Terminal and press enter.ĥ. Type again: sudo sh and be sure there is a space after sh.Ĥ. Open Terminal and type: sudo sh and press enter, then insert your password - it will be invisible - and press enter.ģ. If you have installed any version of TattiBogle and didn't work download UnTattie.Ģ. I used a wired Afterglow AX1 on Lion 10.7.3 - added a video on youtube here.ġ. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |