AutoHotkey Community

XInput
XInput.ahk wraps a few key functions of XInput, a.k.a. the Microsoft Common Controller API. It provides the following capabilities not otherwise accessible to scripts:

• The official drivers report to Windows one axis for both analog triggers, making it impossible to detect when both triggers are pulled at once. XInput allows one to retrieve the state of each analog trigger individually.
• Set level of controller vibration - left and right motor speeds.

Future versions may provide additional functionality:

• Detect input on attached messenger kits (mini keyboards which can be attached to a controller).
• Retrieve battery levels of wireless controllers.
• Access the audio input/output of a given controller's headset.

Required: xinput1_3.dll

This seems to be the current version of XInput, included in recent DirectX run-times.

Optional: Compliant JSON deserialized A/IO parser

Simplifies parsing "structures" returned by XInput_GetState and XInput_GetCapabilities. (Required for the example script.)

XInput.ahk
Covered by Lexikos' default copyright license.

Example: Control the vibration motors using the analog triggers of each controller.

Im getting a wireless adapter for the XBox 360 controller sometime soon. Is there any reason it won't work with wireless?

_________________
aboutscript ⍟ apps ⍟ scripts
Any code ⇈ above ⇈ requires AutoHotkey_L to run

I originally tested the script with one wireless controller. After your post, I also connected a wired controller - the script worked correctly with both controllers connected. It's easy to identify the index of a controller as it directly relates to the lit quadrant on the guide button.

hi, is there anybody still working on it? would love to have the abbility to connect a xbox 360 controller wth my pc and use the chatpad and output sound to headset

I doubt it. I don't own a chatpad.

There is a community of xbox users that might find this very useful.
If you get the time could you post about this script on the forums at xim360.com?
thank you

I'm not familiar with that community, where or what to post. Perhaps you'd better do it?

Thank you so much for this, I've been trying to figure out how to make xinput work with ahk for quite a while.

BTW, is there anyway to determine if the user presses the big "X" button on the controller? (or taps it)//

thanks again, I'll be testing it ..

_________________
::
I Have Spoken
::

I'm not aware of any way.

For some reason, this doesn't work for me. Running the xinput.ahk file with the dll in the same directory. It just shows the tray icon for a split second then quits with no error message. What's up?

XInput.ahk doesn't do anything on its own; it's a library of functions for use in other scripts such as the example in my first post.

Ah, thanks for that. Sorry for bumping a pretty old post. Anyway, my original intention was to somehow find a way to overcome the current limitation of the 360 driver to detect when both triggers are pressed at once.

Looks like it isn't actually a limitation considering Xinput can actually detect when both triggers are pressed. There's a game that I wanna play that has moves where you have to press both triggers at once. I can download a 3rd party driver, but that would affect games that detect Xinput devices (GRiD, GTA4) and I prefer to still have that.

What's the simplest way I can do that? I'm thinking of maybe scripting something like joy2key, where it maps the controller input to the keyboard, hopefully being able to detect both triggers pressed at once. Then passing that onto the game. Problem is, I don't know anything about AutoHotKey scripting. I can learn, though. Anyway, is there an easier way you can think of other than this?

That limitation is the main reason I wrote XInput.ahk. If the game supports mixing keyboard and game controller input, you may use this to remap just the triggers:

If you need to remap other buttons/axes, the methods outlined here may be sufficient.

I play NBA 2K for PC with xbox 360 Wireless contoller. The isomotion on the game is executed if the two triggers are pressed simultaneously, which because of the one axis doesnt do nothing actually.
Well I sense this could be a solution for it, but tried to run the script after I installe AutoHotkey but nothing changes.

Is there something I need to do in order to make it work, change something in the script, add some values or..? I'm just regular PC user and haven't been working with these kind of stuff till now.

PS. I have the xinput1_3.dll, I've searched for it.

Thank u guys, ur help would be very appreciated.

Obviously, the script can't make the game recognize the two triggers as separate axes. It only translates the triggers into two keys: [ and ]. You need to either bind these keys to something in your game, or change the keys in the script (simply replace the [ and/or ] characters).