57 replies to this topic

[Lexikos]

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.

Other capabilities of the XInput API that this script does not currently support include:

• 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 should be included in recent DirectX run-times.
Usage notes for each function are included in XInput.ahk.

XInput.ahk for AutoHotkey 1.1
This version uses objects, so AutoHotkey 1.1 (AutoHotkey_L) is required.

; Example: Control the vibration motors using the analog triggers of each controller.
XInput_Init()
Loop {
Loop, 4 {
if State := XInput_GetState(A_Index-1) {
LT := State.bLeftTrigger
RT := State.bRightTrigger
XInput_SetState(A_Index-1, LT*257, RT*257)
}
}
Sleep, 100
}

XInput.ahk for AutoHotkey 1.0
This version uses JSON strings, and should work on any version of AutoHotkey. The example below requires json().

; Example: Control the vibration motors using the analog triggers of each controller.
XInput_Init()
Loop {
Loop, 4 {
if XInput_GetState(A_Index-1, State)=0 {
LT := json(State,"bLeftTrigger")
RT := json(State,"bRightTrigger")
XInput_SetState(A_Index-1, LT*257, RT*257)
}
}
Sleep, 100
}

XInput.ahk is basically public domain.

[Frankie]

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

[Lexikos]

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.

[Lexikos]

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

[mtgtopdeck]

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

[Lexikos]

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

[TheLeO]

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 ..

[Lexikos]

I'm not aware of any way.

[Lexikos]

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.

[Lexikos]

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:

; ~ Config:

; Minimum to be considered "pressed", between 1 (0.39%) and 255 (100%).
Threshold = 64

; Keys to bind to triggers.
LT_Key = [
RT_Key = ]

; ~

LastRT := LastLT := 0
XInput_Init()
Loop {
    Loop, 4 {
        if XInput_GetState(A_Index-1, State)=0 {
            LT := json(State,"bLeftTrigger") >= Threshold
            RT := json(State,"bRightTrigger") >= Threshold
            if (LT != LastLT) {
                Send % "{" . LT_Key . (LT ? " Down}" : " Up}")
                LastLT := LT
            }
            if (RT != LastRT) {
                Send % "{" . RT_Key . (RT ? " Down}" : " Up}")
                LastRT := RT
            }
        }
    }
    Sleep, 100
}

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

[Lexikos]

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).