XIMCommander 20141219 (LATEST)

[Aiken_Drum]

Quick update for anyone using a joystick and finding they spin in place.  This is just the 1218 version again, really, but with the second analog stick on joysticks disabled.  Everyone should grab this version except people who have a joystick (note: not controller/gamepad/nav, just joysticks) with a second analog stick that they are using.

As always, let's do this before the link:

GIGANTIC CAVEAT

This is not yet production-quality software.  It IS possible for it to leave your system in a mode where inputs are blocked to your desktop/apps, but the XC app is dead and unable to turn the mode off.  This is resolved after a reboot, mind you.  There are two safeguards against this, but still, they might fail.

Just beware that editing sensitive documents should be mutually exclusive with using XIM Commander.  Okay?

ALSO

Please make sure you read through this thread and the documentation in the package.  Okay?

http://cloud.xim4.com/Alpha/XIM4Commander-20141219-Alpha.zip

[abc123]

Quick update for anyone using a joystick and finding they spin in place.  This is just the 1218 version again, really, but with the second analog stick on joysticks disabled.  Everyone should grab this version except people who have a joystick (note: not controller/gamepad/nav, just joysticks) with a second analog stick that they are using.

This has the new documentation for the .ini which i'm happy to see! awesome work Aiken.

So far I can't get this to actually work without locked up my XIM 100%...and requiring an Xbox One reboot to fix it...

Tomorrow i'll debug and report back.

[Aiken_Drum]

@Aiken: AHK isn't being detected on Send...isn't this suppose to be a feature for disabled gamers?

Yes, but XC is effectively a DirectInput game, from AHK's point of view.  You need to write your scripts in the same manner as with pure DI games, which means you have to use sufficient delays and durations.  Also, it's useful to add the {blind} prefix to the output, so that AHK won't diddle with any modifier keys you have held down.

For instance, if I want to auto-teabag someone (XIM TECHNOLOGIES DOES NOT CONDONE TEABAGGING), and if my crouch key is set to 'c', I could use this script to fire it off with F6:

Code: [Select]

F6::
SetKeyDelay,300,50
send {blind}cccccccc
return
Note that the first value in SetKeyDelay is the delay (ms) between keypresses, and the second is the length of the press.  So that script will send eight 'c' presses, 50ms each, 300ms apart, and because of the {blind} modifier, it won't screw me up if I'm using, say, shift for ADS.

The reason why it doesn't work by default is that the delays and durations are tiny by default, but games are often sampling your inputs for an instant every 1/30th of a second, or less, so you have to have the virtual keys held long enough to be seen.

[Od1n]

thanks for that info aiken, i was about to write my capture card ahk script now, your post came just in time to save me some work

[abc123]

@Aiken: AHK isn't being detected on Send...isn't this suppose to be a feature for disabled gamers?

Yes, but XC is effectively a DirectInput game, from AHK's point of view.  You need to write your scripts in the same manner as with pure DI games, which means you have to use sufficient delays and durations.  Also, it's useful to add the {blind} prefix to the output, so that AHK won't diddle with any modifier keys you have held down.

For instance, if I want to auto-teabag someone (XIM TECHNOLOGIES DOES NOT CONDONE TEABAGGING), and if my crouch key is set to 'c', I could use this script to fire it off with F6:

Code: [Select]

F6::
SetKeyDelay,300,50
send {blind}cccccccc
return
Note that the first value in SetKeyDelay is the delay (ms) between keypresses, and the second is the length of the press.  So that script will send eight 'c' presses, 50ms each, 300ms apart, and because of the {blind} modifier, it won't screw me up if I'm using, say, shift for ADS.

The reason why it doesn't work by default is that the delays and durations are tiny by default, but games are often sampling your inputs for an instant every 1/30th of a second, or less, so you have to have the virtual keys held long enough to be seen.

That actually wasn't working for me:

Code: [Select]

Send {s down}
Sleep(30)
Send {s up}

Didn't work for me...I'll mess around some more, I can inject into your process if you'd prefer.

Real Code:

Code: [Select]

~Right::
if (A_PriorHotkey <> "~Right" or A_TimeSincePriorHotkey > 400)
{
    ; Too much time between presses, so this isn't a double-press.
    KeyWait, Right
    return
}
MsgBox "hello"
this will never pop up a message box saying "hello"

[Aiken_Drum]

The "cccccccc" code I pasted was directly from an example script I wrote and tested in Destiny before posting.  It ought to work for you as well.  Is your AHK current?

Also, using your code instead:

Code: [Select]

F6::
Send {s down}
Sleep(30)
Send {s up}
return
Produces a syntax error because Sleep is not supposed to have parens.  This slight modification works for me with my crouch key in Destiny:

Code: [Select]

F6::
Send {c down}
Sleep 30
Send {c up}
return

[abc123]

Yes, my AHK is downloaded today...
Try the below code it requires a double F6 within 400ms, this is directly from the AHK examples.

I can't get it to work however (in XIMCommander) works outside of it.

Code: [Select]

~F6::
if (A_PriorHotkey <> "~F6" or A_TimeSincePriorHotkey > 400)
{
    ; Too much time between presses, so this isn't a double-press.
    KeyWait, F6
    return
}
Send {c down}
Sleep 30
Send {c up}


[matthewrulz]

I'm still getting disconnected randomly.

Here's what my config looks like.

; XIM4 Commander configuration.  Don't add or delete anything.  Just edit the key for now.  Okay?
; See http://msdn.microsoft.com/en-us/library/windows/desktop/ee418641(v=vs.85).aspx for crappy documentation of DIK_* codes.

[Hotkeys]
Cycle=DIK_SYSRQ

[Filter]
Enable=1
; Note that Timeout can be set to 0 to disable the timeout safeguard
Timeout=0

[kyle03]

Make sure your PC doesn't reboot because of windows updates when using this, you end up pointing to the ground and spinning around in circles haha

[ozzie20]

Just some feedback on XC:

1.  When trying to setup/bind keys: Click the button on XM you want to bind, it'll designate Listening, then press PrntScrn to stop feeding into the computer and start feeding into XM.  However, this usually causes multiple signals of PrntScrn to be sent to the XM, causing XM to believe PRNT Scrn is the key you want to bind.  I tried Holding down another key while doing so, and this sometimes works, but I think if priority is given to PRNTSCRN and not say "up arrow", then PRNTSCRN is bound to the PS button instead.  It may be better/easier instead of PRNTSCRN to start listening to have a series of dropdown options for each button to bind instead of a listen and bind series.  IE, what button to bind for "x" button, click and find the key on a dropdown menu.

2.  I'm still getting the Y+ axis turning into Y- axis, but I may be running the previous version, I'll have to double check.  (thrustmaster T1500)

[Hancoque]

By the way, I can't use the pause key. It doesn't work when preset in a game profile and it doesn't work to bind that key to a new button. Pressing the key just doesn't seem to be recognized at all by the XIM software.

[Atlasprime]

"When capture mode is enabled, all inputs are prevented from
being sent to the destop or applications, and are instead converted to XIM4
inputs."

One of the big things I loved about using XIM Commander instead of a KVM was being able to toggle XIM/PC input by pressing ctrl+tab or whatever it was during the XIM3 days. This appears to be prtscr now which is great, but question...

While the XIM3 version of commander was taking in input, I was able to press my Left Control button which is my bind for Team Speak. It sounds like none of these inputs will make it. Is there a way around this to allow that key to go to both the XIM and the PC?

I will give it a shot later, just stuck at work for 8 hours.

[Verkaa]

Cheers Aiken works a treat for me, I do have the occasional random disconnects but I have my PrintScreen bound to one of my Macro keys on my K95 so it is pretty much instantly back into the game anyway.

Cheers for the hard work

Suggestion:
Not sure if it was added to the feature list but turn assist like the Xim Edge had would be an awesome feature (I don't play battlefield or anything anymore, but for the other players that would be a nice feature for them to have)

[abc123]

By the way, I can't use the pause key. It doesn't work when preset in a game profile and it doesn't work to bind that key to a new button. Pressing the key just doesn't seem to be recognized at all by the XIM software.

basically just update the .ini file:

Code: [Select]

; XIM4 Commander configuration.  Don't add or delete anything.  Just edit the key for now.  Okay?
; See http://msdn.microsoft.com/en-us/library/windows/desktop/ee418641(v=vs.85).aspx for crappy documentation of DIK_* codes.

[Hotkeys]
Cycle=DIK_F12

[Filter]
Enable=1
; Note that Timeout can be set to 0 to disable the timeout safeguard
Timeout=0

The above config .ini will make this F12

[Hancoque]

It's not about the cycle key. Currently I use the default print key for that. I meant that I can't use the pause key in XIM Manager while in Commander mode.