2012-01-30, 10:38 AM
So while Maple'd been down all night, I'd been diligently trying to find a nicer workaround for this. I have found one for those who have a PS3 controller!
You need to be using MotionJoy as the driver for your controller. (This may be the only PS3 driver available, I'm not sure, but it's the only thing I ever see in Google.)
1. Open up the MotionJoy DS3 Tool.
2. Choose Playstation 3 mode and click ==> Options.
You'll be presented with a list of button numbers, and what button they correspond to on the controller (example: Button 1: Triangle).
3. Disable the button you use to jump and another button you won't press at the same time by selecting "None" from the drop-down menu. (I used Button 1 and Button 3, leaving Triangle and Cross unmapped to any buttons).
4. Scroll down past the rest of the buttons until you get to the axes. Map the two buttons you disabled above to Axis z+ and Axis z-. Click save changes. These two buttons are now triggers.
5. Click back to "Profiles" and click Enable. You can click the Game Controller Panel button and run a test to verify your buttons are registering as the z axis and not actual buttons.
6. In Xpadder, go into controller settings. Select triggers, and click detect. Press one of your trigger buttons for left, the other for right. (I don't think it really matters which is which?) Press OK. You can now map keys to the triggers just like you do for all of your other buttons - map one as your jump key, and the other as whatever you had it before.
If you use Joy2Key, you need to check the box in the Others tab that says "Use Axes other than X and Y." For me, the z axis was Axis3 in Joy2Key.
Some other notes:
If both triggers are pressed at the same time, they cancel each other out -- this is why I recommend using two buttons you know you won't press at the same time.
Also, I am able to completely exit out of the MotionJoy DS3 tool and my buttons still read as triggers in Xpadder, but only until I restart my computer. After a restart, I need to reload MotionJoy and click Enable for Playstation 3 mode for the buttons to be triggers again, but I haven't needed to reconfigure anything in the options.
You need to be using MotionJoy as the driver for your controller. (This may be the only PS3 driver available, I'm not sure, but it's the only thing I ever see in Google.)
1. Open up the MotionJoy DS3 Tool.
2. Choose Playstation 3 mode and click ==> Options.
You'll be presented with a list of button numbers, and what button they correspond to on the controller (example: Button 1: Triangle).
3. Disable the button you use to jump and another button you won't press at the same time by selecting "None" from the drop-down menu. (I used Button 1 and Button 3, leaving Triangle and Cross unmapped to any buttons).
4. Scroll down past the rest of the buttons until you get to the axes. Map the two buttons you disabled above to Axis z+ and Axis z-. Click save changes. These two buttons are now triggers.
5. Click back to "Profiles" and click Enable. You can click the Game Controller Panel button and run a test to verify your buttons are registering as the z axis and not actual buttons.
6. In Xpadder, go into controller settings. Select triggers, and click detect. Press one of your trigger buttons for left, the other for right. (I don't think it really matters which is which?) Press OK. You can now map keys to the triggers just like you do for all of your other buttons - map one as your jump key, and the other as whatever you had it before.
If you use Joy2Key, you need to check the box in the Others tab that says "Use Axes other than X and Y." For me, the z axis was Axis3 in Joy2Key.
Some other notes:
If both triggers are pressed at the same time, they cancel each other out -- this is why I recommend using two buttons you know you won't press at the same time.
Also, I am able to completely exit out of the MotionJoy DS3 tool and my buttons still read as triggers in Xpadder, but only until I restart my computer. After a restart, I need to reload MotionJoy and click Enable for Playstation 3 mode for the buttons to be triggers again, but I haven't needed to reconfigure anything in the options.