17 replies to this topic

[Berserker]

If anyone wants to give the xpadder xbox controller profile I'm working on, try these two:
https://dl.dropbox.c....xpadderprofile
https://dl.dropbox.c...addercontroller

[Berserker]

It turns out that mwo detects the xbox controller as a joystick and thus ignores xpadder's settings in favor of your joystick settings. I've been looking for a way to turn off joystick support via user.cfg or use the 3rd row joystick settings but the analogue detection settings make it so the sticks and triggers are mostly useless and thus not quite enough buttons to make this exercise worthwhile. If anyone has had luck with either of those, would love to hear it.

[evilC]

Autohotkey should work.
As you say, the game may detect the underlying joypad movements, but if these are bound to nothing then that should not matter.
Just be aware that many controls in mwo (eg weapon firing buttons) will not work in MWO using the normal format:
send {1}

you have to use
send {1 down}
sleep, 50
send {1 up}

Bear in mind though that AHK is unable to output analog axes - as long as you just want to map the joypad to keys only, not axes, you should be OK.

[Berserker]

what is autohotkey? What happens is that in other applications for example when I push the left stick it corresponds to pressing W because I programmed that in xpadder. In MWO mercs it behaves as programmed in that third configuration column, and analog sticks are forced to be analog input so you can't for example use them for throttle and the trigger buttons are also similarly obviated.

[evilC]

www.autohotkey.com

It's hard to understand what you want - for example the sentence "analog sticks are forced to be analog input so you can't for example use them for throttle" makes no sense.
What exactly are you trying to do? Map a joypad to mimic keys?

Edited by evilC, 06 January 2013 - 06:10 AM.

[Berserker]

You might have to see it for yourself to understand, meaning plug in a gamepad and see how it behaves. What xpadder and your program both seem intended to do is to let you program a specific button, stick, etc on a gamepad to a specific behavior, be it button press, mouse movement, etc. What MWO does is assume that you want to use any analog stick or analog trigger as a mouse controller. So, in my case I want to use buttons on the controller and have them be key presses but I'd really like one of the sticks to be used for turning and throttle, which as far as I can tell would require up to be "w", down to be "s", left "a", right "d" etc. What the control mapping in the MWO application does with the joystick input when you try to map it in this fashion is set a single command, like throttle up to map to all input from the stick.

As an example if you programmed your autohotkey combinations to work with some sort of gesture on the stick that causes you to throttle up, turn, fire, etc, I'm fairly sure that when you were inside MWO it would ignore them in favor of the settings for that third column in the settings that represent joystick.

I think trying to program support for every device would be tough to justify so the best solution in my opinion would be to have a user.cfg and ultimately GUI option to turn off the joystick recognition so that MWO app wouldn't latch on the controller in that way and would let xpadder or whatever people use to program the buttons and sticks to various recognition settings in their OS would be allowed to work.

Edited by Berserker, 06 January 2013 - 02:48 PM.

[evilC]

Yes, I have seen what you are talking about - you reprogram a joystick using something like AutoHotkey, but the game still recognises the underlying joystick input.
You should be able to unmap the joystick bindings (ie clear column 3) and the game will then only recognise the remapped keyboard input.
The only thing that I can find that does not suffer from this is GlovePIE - if you use the swallow(<input>) command, it does indeed prevent the game from seeing the underlying input.

[Berserker]

Thanks, I think I tried the three column thing but it was 2am when I got that far so I wasn't paying a lot of attention.

I'll check out glovepie if it doesn't work.

[Obeast]

I use an Xbox controller and Xpadder. The easiest workaround for the Joystick keybind in column 3 are to just clear them out by picking the same button for each one. Then when I get to the last one I set the back button to be "thermal" or whatever you prefer and leave that key blank on the Xpadder profile.

[evilC]

Berserker, on 07 January 2013 - 11:30 AM, said:

Thanks, I think I tried the three column thing but it was 2am when I got that far so I wasn't paying a lot of attention.

I'll check out glovepie if it doesn't work.

Don't bother - GlovePIE is basically useless without it controlling a PPJoy virtual controller, and the game does not recognise PPJoy virtual controllers at the moment.

[Berserker]

Thx both of you for the feedback, should enable others to use as well.

[Sid The Kid]

Obeast, on 07 January 2013 - 11:36 AM, said:

I use an Xbox controller and Xpadder. The easiest workaround for the Joystick keybind in column 3 are to just clear them out by picking the same button for each one. Then when I get to the last one I set the back button to be "thermal" or whatever you prefer and leave that key blank on the Xpadder profile.

I think if you could elaborate on this, you would be the hero to a lot of people trying to get this done. How exactly do you set all the joystick buttons to be the same? I am having no luck doing this currently. Thanks!

[Muzakman]

I just plugged in my XBox360 wireless controller (using the wireless adapter thingie) and it worked OOB!!

After picking my jaw up from the floor, I dove in and started testing the config... unfortunately it's a bit trial and error, but I'll respond back when I put together a decent scheme.

[Connor OBradley]

My problem is getting xpadder to actually work in Mechwarrior Online. My xpadder profile works every where outside of the game. Can someone tell me what I am doing wrong?

[Xenik]

Connor OBradley, on 27 February 2013 - 12:36 AM, said:

My problem is getting xpadder to actually work in Mechwarrior Online. My xpadder profile works every where outside of the game. Can someone tell me what I am doing wrong?

This is exactly what is happening to me as well... Its driving me insane trying to find a work around!

[Berserker]

Obeast, on 07 January 2013 - 11:36 AM, said:

I use an Xbox controller and Xpadder. The easiest workaround for the Joystick keybind in column 3 are to just clear them out by picking the same button for each one. Then when I get to the last one I set the back button to be "thermal" or whatever you prefer and leave that key blank on the Xpadder profile.

I've not been able to get it to work, even with the 3rd column suggestions. MWO grabs hold of the controller and won't let XPadder take over.

[Lynx7725]

Wait for tomorrow's patch before you guys do anything too drastic. Between the basic config that PGI has given us here and the upcoming tweaks, we may have enough to work with for the Xbox controller.

[clockwerkninja]

I mapped my xbox controller to xpadder using the above method. Just go into the joystick config and select the bottom most key bond and set it to back. Then continue up the list one at a time setting them to back and clearing the key before. The last key set it to thermal ..Then go map the keys with xpadder .

Working for me now.