search

AntiMicro / antimicro

[NOT maintained anymore] Graphical program used to map keyboard buttons and mouse controls to a gamepad. Useful for playing games with no gamepad support
1.8k stars 201 forks source link

startSet problems #111

Closed toccata10 closed 1 year ago

toccata10 commented 7 years ago

1st: thanks for antimicro: it's terribly usefull ! My situation: I have 2 custom arcade sticks (with 2 zero delay usb encoders). I've created several sets to play different games. Launching antimicro, selecting the correct sets, then launching the game works perfectly. I'd like to script the whole process. So I'm trying to assign the set n°4 to the 2nd stick with this: antimicro --profile /home/jo/AM-Stick-10.joystick.amgp --startSet 4 2 It doesn't work. This: antimicro --profile /home/jo/AM-Stick-10.joystick.amgp --startSet 4 assigns the same set for stick 1 & 2 + when I press a button: only the tab is blinking (in red), not the button itself (it should blink in blue). To have it do something, I have to manually click on a set: then it works fine. antimicro --profile /home/jo/AM-Stick-10.joystick.amgp --startSet 3 --profile-controller 2: it's nearly there: it puts set n°1 on controller 1, and set 3 on controller 2. But: for controller 2, only the tab is blinking in red.

2 questions: 1) is it possible to assign set n°4 on joystick 1 and set n°5 on joystick 2 (for example) with the command line ? 2) the --startSet flag seems to desactivate the usual behaviour. Looked in the debug log, but found nothing useful related to this pb.

jsbackus commented 7 years ago

Hi @toccata10, welcome! Glad you are enjoying antimicro. Also, props for the custom arcade sticks. Build them yourself?

Hmm. Interesting.. Yeah, it sounds like there are issues with specifying the starting set for controller != 1, which would be a bug. It also sounds like we might need to revamp the CLI to make it easier to applying different profiles/sets to different controllers.

I'm marking this as a bug (for the controller != 1 issue) and I've created issue #114 to address the CLI issue.

In the interim, have you considered using different profiles instead of sets? If you aren't switching between sets, then that might be a quick work-around for you.

toccata10 commented 7 years ago

Hi @jsbackus, Thanks for your very quick answer. Back from the christmas lunches, I did a few more tests: I create 2 different profiles (your suggested workaround) and try to apply them to my 1st and 2nd sticks: 1st try: antimicro --profile-controller 1 /home/jo/AM-Stick-10.joystick.amgp & antimicro --profile-controller 2 /home/jo/AM-Stick-USF4.joystick.amgp & Result: AM-Stick-10 for both controller 1 & 2

2nd try: antimicro --profile-controller 1 /home/jo/AM-Stick-Pinball-02.joystick.amgp & killall -15 antimicro antimicro --profile-controller 2 /home/jo/AM-Stick-PCSX2.joystick.amgp & this works ok. It doesn't seem very clean but it works (probably because Settings>General>Autoload last profile is ticked). So, my goal is to use emulationstation to launch my retrogames (buttons mapping is done by retroarch, so it's ok), but also some PlayOnLinux games: GuiltyGear for example, which needs keyboard mapping to work correctly with my sticks.

jsbackus commented 7 years ago

Hi @toccata10, sorry for taking so long to get back to you!

Glad you have a solution that works. Very much a hack. We'll fix it. Thanks!

pktiuk commented 1 year ago

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.