Some questions about the program

[usagi2607]

Hi jsbackus,

First of all, thank you for the very useful software. This helps me a lot in customizing my Xbox controller and other Xiput devices.
I got a couple questions while using antimicro:

• RT/LT axis hold & release: I notice that the dead zone slider determines how the (mapped) key is triggered (hold/release). I often find myself not always press or release the trigger in the same way (sometime I press and release the trigger lightly and sometime I do a full pull). When the dead zone is set to minimum, I have to release the trigger all the way in order to do the release. This lead to my problem that sometimes I do a full pull but don't do fully release, then the next pull is not registered (of course because I did not release the trigger correctly). If I increase the dead zone, it leads to other problem that it requires me to pull the trigger further in order to trigger the key.
  So the question is: Is there a way to solve this? Basically, is it possible to configure in such a way that the trigger can handle both of the behaviors "nicely": light pull and strong pull (without the need of full release)? (I thought the "normal" in throttle setting could help but it seems like I misunderstood this option).
• Advanced assignments: Is it possible to custom a button to do 2 actions "Tap&Hold" but the Hold shall cycle through some keys (like turbo mode). For example: Tap will do "R" and Hold will do "E" but keeps repeating "E" (turbo) as long as the button is held. I tried the following but it does not work (maybe I missed something):
  Cycle Reset: 0.50 seconds
  Release 0.01 -> R -> Release 0.49 -> Hold 0.49 -> Cycle -> E
• Xinput recognition: some games detect the xinputs automatically which causes the keys (which were mapped using antimicro) and original xinputs being triggered simultaneously. Maybe it is outside antimicro scope but do you by chance know if it is possible to complete override the xinput keys. Likes, if I press X button which is mapped with E key, then only the E key is sent and not the X button event?

Hopefully you have some time for my questions, I'm very appreciate for all the things you did.

[jsbackus]

Hi @usagi2607! Glad you're enjoying the software! All thanks goes to @Ryochan7 - I'm just one of the folks trying to keep the project alive since he has moved on to other things. I'll try to answer your questions as best I can, though I am still learning the code.

1. I suspect that the answer is no, though I do not know for sure. Are you using using the RT/LT axes for a fairly binary operation? i.e. it is either in "release" or "hold" and not some kind of continuum, such as an analog stick?
2. Interesting! I suspect that the answer is no, though I do not know for sure. It is an interesting idea though... I'll have to look into it.
3. Again, don't know for sure, but I'm pretty confident that the answer is no. I'm not familiar with how AntiMicro is interacting with they keyboard input buffer, but I do not believe we can remove keys from the buffer of another program. Although, I'm surprised we're able to peek at another program's keys, to be honest.... Again, still learning the program. I'll have to look into it.

Again, thanks for your interest and your questions! I'll try to get back to you as soon as I can, but it may be a while. I work on AntiMicro when I can, but I don't have much free time.

[usagi2607]

Hi jsbackus,

Thank you for your answer.

1. Yes, likes a mouse click, an action is registered when the mouse is pressed and won't do anything until it is released.
2. Seems like the turbo option is disabled automatically when the "hold" assignment is present. So, I guess that is why it does not work.
3. That's what I thought too. Though, I was able to use x360ce to disable the xinput by emptying all the controller's buttons, then copy the generated xinput1_3.dll to the program/game directory which supports/recognizes xinput device. And, it seems to work. So, I guess might be antimicro can also have this feature in the future.

Anyways, thank you you guys for a nice program. Hopefully to see more nice updates in the future.

[WAZAAAAA0]

3. Someone already suggested this in the old repository, it's an interesting feature but the main developer probably (can't remember clearly) thought it was kinda intrusive and wasn't sure on how to implement it.
   Pinnacle Game Profiler seems to have a function called "Block game from reading the controller with native support" but unfortunately it's not open source and last time I tried it, it didn't even work.
   http://i.imgur.com/sG3Z9js.png

[jsbackus]

Argh! Just realized that GH doesn't handle ordered lists properly. Sorry for the list of 1's. 👼

Hi @usagi2607,

1. Hmm.. Yes, it sounds like the triggers should actually have a delta threshold instead of an absolute threshold. I've created issue Change trigger threshold to be a delta instead of an absolute #33 to track this as a possible feature in a future release.
2. Yes, I suspect so. Might be worth considering a "hold + turbo" option. I've created issue Add a "hold + turbo" button option #34 to track this as a possible feature in a future release.
3. Interesting! Though I'm not a big fan of replacing DLLs in programs with modified versions, from a project standpoint. Might be an interesting project of its own, though. I agree with @WAZAAAAA0's assessment - very tricky and/or intrusive to do. Cleanest way I can think of is to create an invisible window that keeps the foreground and soaks up all key presses, filters them, and stuffs the modified key presses into the game's input buffer. One day we might consider it, but for the time being I'd say it is beyond the scope of the project. Sorry!

[pktiuk]

AntiMicro is no longer maintained. There were no bigger fixes since 2017.
There is a new recommended version of this app called AntiMicroX.

As a part of cleanup, this issue will be closed and repository will be archived.
If you find this issue relevant also for that new version of application you can create a new issue (or discussion) there (but firstly check it, because many issues of the old app are fixed and there are some new functionalities implemented)
If you will decide to create a new issue for AntiMicroX remember to mention this issue for reference.