BlackSpectre Posted Friday at 06:01 AM Posted Friday at 06:01 AM I followed @telephone's keybind setup for a gamepad as closely as I could. Most of them seem to work, but I had a lot of trouble with the Right Trigger as a modifer button. Many times it simply would not execute the desired bind and did nothing. Sometimes switching the key name's order in the bind string helped, but now JOY8 (Right Trigger) appears to be stuck executing only "powexec_altslot 5", and it will not do anything else. It will even execute that command by only pressing JOY8 by itelf, and this is after I bound it with "nop". I bounds all 4 modifer buttons with "nop" beacuse they would start executing a command I used for a chord/modifier bind. It's wacky. I've tried unbinding and rebinding, resetting all keybinds, reloading in the keybinds, typing the keybinds manually, restarting the game... and no dice. I can remove the bind, but when I re-bind it the same thing happens. The whole gamepad binding system seems prone to conflicts with itself. I have been writing up a page on game controllers at the wiki, and here are the binds I'm using User:BlackSpectre/Testthis3 - Unofficial Homecoming Wiki . The page isn't finsihed because I've had to stop after I ran into this problem. Black Spectre - A Dark Defender's Home on the Web • The Advanced Bind Guide • The Masters of BAF: A Guide for Leaders and Players • The Wiki List of Slash Commands
UltraAlt Posted Friday at 07:14 AM Posted Friday at 07:14 AM (edited) 1 hour ago, BlackSpectre said: gamepad This link includes the walk-in to the file that can be imported for use of my setup with the Logitech F310 Edited Friday at 07:35 AM by UltraAlt If someone posts a reply quoting me and I don't reply, they may be on ignore. (It seems I'm involved with so much at this point that I may not be able to easily retrieve access to all the notifications) Some players know that I have them on ignore and are likely to make posts knowing that is the case. But the fact that I have them on ignore won't stop some of them from bullying and harassing people, because some of them love to do it. There is a group that have banded together to target forum posters they don't like. They think that this behavior is acceptable. Ignore (in the forums) and /ignore (in-game) are tools to improve your gaming experience. Don't feel bad about using them.
UltraAlt Posted Friday at 07:20 AM Posted Friday at 07:20 AM (edited) 1 hour ago, BlackSpectre said: on game controllers at the wiki I see. You are addressing x-box controllers. This link goes into: Images of my controller button setup for the Logitech F310 Resolving game controller issues with the Logitech F310 and then my tray setup. The whole thread is a walk-through of setting up the Logitech F310 and a couple of modifications of my tray setups. It allows for the Logitech F310 to trigger all 10 buttons in the active tray (six click-attack powers per tray, with macros in each tray to flip between tray 1 and tray 2 and trigger healing insps, fast travel [click left stick], and slow travel [click right stick]) as well a buttons for click on the blue hand, target near, target next, auto run, jump. The stick directions are set for moving and adjusting camera angle. Edited Friday at 07:35 AM by UltraAlt 1 If someone posts a reply quoting me and I don't reply, they may be on ignore. (It seems I'm involved with so much at this point that I may not be able to easily retrieve access to all the notifications) Some players know that I have them on ignore and are likely to make posts knowing that is the case. But the fact that I have them on ignore won't stop some of them from bullying and harassing people, because some of them love to do it. There is a group that have banded together to target forum posters they don't like. They think that this behavior is acceptable. Ignore (in the forums) and /ignore (in-game) are tools to improve your gaming experience. Don't feel bad about using them.
RoselineHill Posted Friday at 07:36 AM Posted Friday at 07:36 AM Navigating gamepad keybinds can feel like playing a frustrating snake game, especially when the Right Trigger goes rogue. I'm experiencing similar binding issues, where certain commands refuse to cooperate. Even after unbinding and rebinding, the problem persists, making me wonder if there's an underlying conflict within the system itself.
UltraAlt Posted Friday at 07:40 AM Posted Friday at 07:40 AM (edited) 1 hour ago, BlackSpectre said: I have been writing up a page on game controllers at the wiki, and here are the binds I'm using User:BlackSpectre/Testthis3 - Unofficial Homecoming Wiki . The page isn't finsihed because I've had to stop after I ran into this problem. after I posted all of this I saw that you had put a link to my thread in guides at the bottom of the page - thanks. I tried using the X-input with the Logitech F10, but that had issues. The Logitech F310 can be configured so that the game thinks it is keyboard and that seems to get around the weirdness issues of using X-input. Edited Friday at 07:48 AM by UltraAlt 1 If someone posts a reply quoting me and I don't reply, they may be on ignore. (It seems I'm involved with so much at this point that I may not be able to easily retrieve access to all the notifications) Some players know that I have them on ignore and are likely to make posts knowing that is the case. But the fact that I have them on ignore won't stop some of them from bullying and harassing people, because some of them love to do it. There is a group that have banded together to target forum posters they don't like. They think that this behavior is acceptable. Ignore (in the forums) and /ignore (in-game) are tools to improve your gaming experience. Don't feel bad about using them.
UltraAlt Posted Friday at 07:43 AM Posted Friday at 07:43 AM 4 minutes ago, RoselineHill said: Navigating gamepad keybinds can feel like playing a frustrating snake game, especially when the Right Trigger goes rogue. I'm experiencing similar binding issues, where certain commands refuse to cooperate. Even after unbinding and rebinding, the problem persists, making me wonder if there's an underlying conflict within the system itself. I find that sometimes the Logitech controller goes wonky and I have to alt-tab out of game, swirl the sticks, push the buttons, and then alt-tab back into the game. This hasn't happened to me for a good while, but it happened to me enough in previous years that found doing the above would resolve it. If someone posts a reply quoting me and I don't reply, they may be on ignore. (It seems I'm involved with so much at this point that I may not be able to easily retrieve access to all the notifications) Some players know that I have them on ignore and are likely to make posts knowing that is the case. But the fact that I have them on ignore won't stop some of them from bullying and harassing people, because some of them love to do it. There is a group that have banded together to target forum posters they don't like. They think that this behavior is acceptable. Ignore (in the forums) and /ignore (in-game) are tools to improve your gaming experience. Don't feel bad about using them.
BlackSpectre Posted Friday at 11:18 PM Author Posted Friday at 11:18 PM (edited) 15 hours ago, RoselineHill said: Navigating gamepad keybinds can feel like playing a frustrating snake game, especially when the Right Trigger goes rogue. I'm experiencing similar binding issues, where certain commands refuse to cooperate. Even after unbinding and rebinding, the problem persists, making me wonder if there's an underlying conflict within the system itself. I'm pretty sure that's true. I mean, after binding 2 buttons using this bind JOY3+JOY8 "powexec_altslot 5", why would "powexec_altslot 5" activate when only JOY8 is pressed??? Why would "nop" have to be bound to the other modifier keys to stop them from doing similar things? Why would we have to Alt-Tab out of the game and then back in to stop the gamepad from running amok? There's definitely something wrong. I'm not sure which Microsoft API Homecoming is using, but if it's not the newer GameInput API (instead of XInput), that might have something to do with it? The new (2021) GameInput has a lot more features and capabilities than XInput had, and according to Microsoft it's also 30% less input latency and resource usage. They've had 4 years to iron out the bugs, so it might be time to take the plunge if Homecoming hasn't yet. Edited Friday at 11:29 PM by BlackSpectre Black Spectre - A Dark Defender's Home on the Web • The Advanced Bind Guide • The Masters of BAF: A Guide for Leaders and Players • The Wiki List of Slash Commands
BlackSpectre Posted Friday at 11:42 PM Author Posted Friday at 11:42 PM (edited) 16 hours ago, UltraAlt said: after I posted all of this I saw that you had put a link to my thread in guides at the bottom of the page - thanks. I tried using the X-input with the Logitech F10, but that had issues. The Logitech F310 can be configured so that the game thinks it is keyboard and that seems to get around the weirdness issues of using X-input. That shouldn’t happen if the game was coded correctly for XInput. Looks like the Xbox 360 was not a supported device back in 2012. If the Wiki is correct, the right stick didn't even work. So it looks like Homecoming did make some improvements. The right stick now works at least, and homecoming introduced modifier keys as well. The thing is... the way Homecoming has introduced modifier keys looks like a bit of a hack to me. I noticed that a bind like this <code>JOY3+JOY8 "powexec_altslot 5"</code> is translated into <code>JOYMOD1+JOY3 "powexec_slot 5"</code> in keybinds.txt. So with the help of the modifier key slash commands, the game is translating the key names of the buttons into different key names depending on if they were defined as modifier keys or not. I'm not sure if the translation is being done on the fly every time a button is pressed, or if the keys were translated at the time of binding and that's it. I hope the latter. Honestly, I think the standard keys used for modifiers (left and right triggers and left and right bumpers) should be considered modifiers at the start, using the buttons' memory addresses, rather than a key name. Then if a player wishes to bind only the single modifier button, that can be done with a key name... but I don't want to go on talking about things I know very little about. I understand this suggestion would prevent players from using any other buttons as modifier keys, but I'd rather deal with that limitation than having the system be unstable. Other weird things I noticed... one time Joy7 appeared twice in keybinds.txt. One bound with the "NOP" command that I created, and the other with a command that I had been used in a modifier/chord bind. When I used /unbind on Joy7, it removed the extra command, but kept the bind with "NOP" on it in keybinds.txt At one time, JOY12 would not appear in keybinds.txt using /bindloadfile, but it did appear when using /showbindallfile. I reset all binds, loaded in the gamepad binds again, and then it showed up in keybinds.txt. So intermittent signs of instability. It's weird. Edited yesterday at 01:06 AM by BlackSpectre Black Spectre - A Dark Defender's Home on the Web • The Advanced Bind Guide • The Masters of BAF: A Guide for Leaders and Players • The Wiki List of Slash Commands
BlackSpectre Posted yesterday at 01:24 AM Author Posted yesterday at 01:24 AM (edited) UPDATE: Today I reset all of my binds using /unbindall. Then I used /bindsave and after the only thing left in keybinds.txt was "KeyProfile Classic" and "UnbindAll". Then I used /bindloadfile to load in the gamepad.txt file below. Then I used /bindsave to save the new binds to keybinds.txt. Now when I press the Right Trigger (JOY8), it executes the 8th power slot in the Alt tray slot (i.e., powexec_altslot 8 ) whenever I press the button. I did NOT bind that command to JOY8. I bound "NOP" to that button. However, looking at keybinds.txt, I find the following bind: JOY8 "powexec_altslot 8" I did NOT create that bind, the system did all by itself. In addition, all of the binds using Powexec_AltSlot are MISSING from keybinds.txt and do not function in game. The system deleted them. JOYPAD_LEFT+JOY8 "powexec_altslot 1" JOYPAD_UP+JOY8 "powexec_altslot 2" JOYPAD_DOWN+JOY8 "powexec_altslot 3" JOYPAD_RIGHT+JOY8 "powexec_altslot 4" JOY3+JOY8 "powexec_altslot 5" JOY4+JOY8 "powexec_altslot 6" JOY1+JOY8 "powexec_altslot 7" JOY2+JOY8 "powexec_altslot 8" This behavior is CONSISTENT. I've now reset my character's binds and reloaded in my gamepad.txt several times... same result. GAMEPAD.txt Spoiler JOY1 "+up" JOY2 "powexec_abort" JOY3 "powexecname athletic run" JOY4 "interact" JOY5 "nop" JOY6 "nop" JOY7 "nop" JOY8 "nop" JOY9 "camturn" JOY10 "face" JOY11 "menu" JOY12 "map" JOYPAD_UP "target_enemy_next" JOYPAD_DOWN "target_enemy_near" JOYPAD_LEFT "target_custom_prev teammate" JOYPAD_RIGHT "target_custom_next teammate" JOYSTICK1_UP "+forward" JOYSTICK1_DOWN "+backward" JOYSTICK1_LEFT "+left" JOYSTICK1_RIGHT "+right" JOYSTICK2_RIGHT "+turnright" JOYSTICK2_LEFT "+turnleft" JOYSTICK2_DOWN "+lookdown" JOYSTICK2_UP "+lookup" JOY6+JOYPAD_LEFT "inspexec_slot 1" JOY6+JOYPAD_UP "inspexec_slot 2" JOY6+JOYPAD_DOWN "inspexec_slot 3" JOY6+JOYPAD_RIGHT "inspexec_slot 4" JOY6+JOY12 "inspexec_slot 5" JOY7+JOY5 "Prev_Tray" JOY7+JOY6 "Next_Tray" JOY7+JOYPAD_LEFT "powexec_slot 1" JOY7+JOYPAD_UP "powexec_slot 2" JOY7+JOYPAD_DOWN "powexec_slot 3" JOY7+JOYPAD_RIGHT "powexec_slot 4" JOY7+JOY3 "powexec_slot 5" JOY7+JOY4 "powexec_slot 6" JOY7+JOY1 "powexec_slot 7" JOY7+JOY2 "powexec_slot 8" JOY5+JOY8 "Prev_Tray_Alt" JOY6+JOY8 "Next_Tray_Alt" JOYPAD_LEFT+JOY8 "powexec_altslot 1" JOYPAD_UP+JOY8 "powexec_altslot 2" JOYPAD_DOWN+JOY8 "powexec_altslot 3" JOYPAD_RIGHT+JOY8 "powexec_altslot 4" JOY3+JOY8 "powexec_altslot 5" JOY4+JOY8 "powexec_altslot 6" JOY1+JOY8 "powexec_altslot 7" JOY2+JOY8 "powexec_altslot 8" JOY5+JOYPAD_LEFT "say $battlecry $$ emote attack" JOY5+JOYPAD_UP "local <color white><bgcolor red>RUN!" JOY5+JOYPAD_DOWN "say <color black><bgcolor #22aa22>Ready! $$ emote thumbsup" JOY5+JOYPAD_RIGHT "local <color black><bgcolor #aaaa22>HELP! $$ emote whistle" KEYBINDS.TXT Spoiler KeyProfile Classic UnbindAll JOY1 "+up" JOY2 "powexec_abort" JOY3 "powexecname athletic run" JOY4 "interact" JOY5 "nop" JOY6 "nop" JOY7 "nop" JOY8 "powexec_altslot 8" JOY9 "camturn" JOY10 "face" JOY11 "menu" JOY12 "map" JOYPAD_UP "target_enemy_next" JOYPAD_DOWN "target_enemy_near" JOYPAD_LEFT "target_custom_prev teammate" JOYPAD_RIGHT "target_custom_next teammate" JOYSTICK1_UP "+forward" JOYSTICK1_DOWN "+backward" JOYSTICK1_LEFT "+left" JOYSTICK1_RIGHT "+right" JOYSTICK2_RIGHT "+turnright" JOYSTICK2_LEFT "+turnleft" JOYSTICK2_DOWN "+lookdown" JOYSTICK2_UP "+lookup" EXTRAMOD2+JOYPAD_LEFT "inspexec_slot 1" EXTRAMOD2+JOYPAD_UP "inspexec_slot 2" EXTRAMOD2+JOYPAD_DOWN "inspexec_slot 3" EXTRAMOD2+JOYPAD_RIGHT "inspexec_slot 4" EXTRAMOD2+JOY12 "inspexec_slot 5" JOYMOD1+JOY5 "Prev_Tray" JOYMOD1+JOY6 "Next_Tray" JOYMOD1+JOYPAD_LEFT "powexec_slot 1" JOYMOD1+JOYPAD_UP "powexec_slot 2" JOYMOD1+JOYPAD_DOWN "powexec_slot 3" JOYMOD1+JOYPAD_RIGHT "powexec_slot 4" JOYMOD1+JOY3 "powexec_slot 5" JOYMOD1+JOY4 "powexec_slot 6" JOYMOD1+JOY1 "powexec_slot 7" JOYMOD1+JOY2 "powexec_slot 8" EXTRAMOD1+JOY8 "Prev_Tray_Alt" EXTRAMOD2+JOY8 "Next_Tray_Alt" EXTRAMOD1+JOYPAD_LEFT "say $battlecry $$ emote attack" EXTRAMOD1+JOYPAD_UP "local <color white><bgcolor red>RUN!" EXTRAMOD1+JOYPAD_DOWN "say <color black><bgcolor #22aa22>Ready! $$ emote thumbsup" EXTRAMOD1+JOYPAD_RIGHT "local <color black><bgcolor #aaaa22>HELP! $$ emote whistle" Edited yesterday at 07:44 AM by BlackSpectre Black Spectre - A Dark Defender's Home on the Web • The Advanced Bind Guide • The Masters of BAF: A Guide for Leaders and Players • The Wiki List of Slash Commands
BlackSpectre Posted yesterday at 02:39 AM Author Posted yesterday at 02:39 AM (edited) UPDATE#2 I switched the order of the modifer button and the regular button in the bindfile so that the modifier button comes first. So instead of "JOY3+JOY8 ", I loaded in "JOY8+JOY3", and most of those binds showed up in keybinds.txt. However, JOY8+JOYPAD_DOWN "powexec_altslot 4" is missing. Or rather its equivalent, JOYMOD2+JOYPAD_DOWN "powexec_altslot 4" is missing. In addition, now this bind showed up out of nowhere in keybinds.txt: JOY8 "4"" Note: The 3 quotation marks are not a typo. It's in keybinds.txt just as you see it. It looks like, for some weird reason, +JOYPAD_DOWN "powexec_altslot was deleted by the system from JOY8+JOYPAD_DOWN "powexec_altslot 4", and the 2 parts that were not removed where put together to form JOY8 "4"". That would be my guess anyway. And this is now CONSISTENT. Edited yesterday at 03:48 AM by BlackSpectre Black Spectre - A Dark Defender's Home on the Web • The Advanced Bind Guide • The Masters of BAF: A Guide for Leaders and Players • The Wiki List of Slash Commands
BlackSpectre Posted yesterday at 03:24 AM Author Posted yesterday at 03:24 AM (edited) Also, if these binds are loaded in they will NOT function at all (but at least they show up in keybinds.txt): JOY8+JOY5 "Prev_Tray_Alt" JOY8+JOY6 "Next_Tray_Alt" but if you switch the key names around, then they work. Like so: JOY5+JOY8 "Prev_Tray_Alt" JOY6+JOY8 "Next_Tray_Alt" You might think that the rule of thumb is that modifier buttons must come first in the bind string before any other key names, but the above contratdicts that notion. We can't even infer this rule: "Modifier button names must come first in the bind string. However, if a trigger (joymod) and bumper (extramod2) are used together, the bumper (extramod) must come first in the bind string." Why? Because these binds contradict that rule and yet work just fine: JOY7+JOY5 "Prev_Tray" JOY8+JOY6 "Next_Tray" Maybe there's another rule that might work? Maybe. Edited yesterday at 03:33 AM by BlackSpectre Black Spectre - A Dark Defender's Home on the Web • The Advanced Bind Guide • The Masters of BAF: A Guide for Leaders and Players • The Wiki List of Slash Commands
BlackSpectre Posted yesterday at 04:03 AM Author Posted yesterday at 04:03 AM (edited) UPDATE#3 So... thinking about bind string conflicts and how the strings can be truncated when 2 binds are executed very quickly, it occured to me that maybe if a single modifier button is bound first, it might come into conflict with a modifier/chord button. In my gamepad.txt file, I have all of the modifier/chord buttons at the bottom of the file. Assuming they load in after the binds at the top of the file, I decided to test that and put all of the modifier/chord binds at the top. THAT WORKED! Kinda. Now all the binds show up correctly in keybinds.txt (although JOY8 "nop" oddly shows up in the middle of the text instead of with the other modifier NOP binds, which indicates to me that something is still wrong). The only problem now is that modifier/chord binds that include the Right Trigger (JOY8) and the D-Pad or Face buttons don't work at all! None of my modifier/chord binds using JOY8 work except for the 2 that use the Extra modifier buttons (i.e., bumpers). KEYBINDS.TXT Spoiler KeyProfile Classic UnbindAll EXTRAMOD2+JOYPAD_LEFT "inspexec_slot 1" EXTRAMOD2+JOYPAD_UP "inspexec_slot 2" EXTRAMOD2+JOYPAD_DOWN "inspexec_slot 3" EXTRAMOD2+JOYPAD_RIGHT "inspexec_slot 4" EXTRAMOD2+JOY12 "inspexec_slot 5" JOYMOD1+JOY5 "Prev_Tray" JOYMOD1+JOY6 "Next_Tray" JOYMOD1+JOYPAD_LEFT "powexec_slot 1" JOYMOD1+JOYPAD_UP "powexec_slot 2" JOYMOD1+JOYPAD_DOWN "powexec_slot 3" JOYMOD1+JOYPAD_RIGHT "powexec_slot 4" JOYMOD1+JOY3 "powexec_slot 5" JOYMOD1+JOY4 "powexec_slot 6" JOYMOD1+JOY1 "powexec_slot 7" JOYMOD1+JOY2 "powexec_slot 8" EXTRAMOD1+JOY8 "Prev_Tray_Alt" EXTRAMOD2+JOY8 "Next_Tray_Alt" JOYMOD2+JOYPAD_LEFT "powexec_altslot 1" JOYMOD2+JOYPAD_UP "powexec_altslot 2" JOYMOD2+JOYPAD_DOWN "powexec_altslot 3" JOY8 "nop" JOYMOD2+JOY3 "powexec_altslot 5" JOYMOD2+JOY4 "powexec_altslot 6" JOYMOD2+JOY1 "powexec_altslot 7" JOYMOD2+JOY2 "powexec_altslot 8" EXTRAMOD1+JOYPAD_LEFT "say $battlecry $$ emote attack" EXTRAMOD1+JOYPAD_UP "local <color white><bgcolor red>RUN!" EXTRAMOD1+JOYPAD_DOWN "say <color black><bgcolor #22aa22>Ready! $$ emote thumbsup" EXTRAMOD1+JOYPAD_RIGHT "local <color black><bgcolor #aaaa22>HELP! $$ emote whistle" JOY1 "+up" JOY2 "powexec_abort" JOY3 "powexecname athletic run" JOY4 "interact" JOY5 "nop" JOY6 "nop" JOY7 "nop" JOY9 "camturn" JOY10 "face" JOY11 "menu" JOY12 "map" JOYPAD_UP "target_enemy_next" JOYPAD_DOWN "target_enemy_near" JOYPAD_LEFT "target_custom_prev teammate" JOYPAD_RIGHT "target_custom_next teammate" JOYSTICK1_UP "+forward" JOYSTICK1_DOWN "+backward" JOYSTICK1_LEFT "+left" JOYSTICK1_RIGHT "+right" JOYSTICK2_RIGHT "+turnright" JOYSTICK2_LEFT "+turnleft" JOYSTICK2_DOWN "+lookdown" JOYSTICK2_UP "+lookup" Edited yesterday at 12:20 PM by BlackSpectre Black Spectre - A Dark Defender's Home on the Web • The Advanced Bind Guide • The Masters of BAF: A Guide for Leaders and Players • The Wiki List of Slash Commands
BlackSpectre Posted yesterday at 07:36 AM Author Posted yesterday at 07:36 AM (edited) Next I tried putting the Right Trigger AFTER any other button names in the binds, but then none of them appeared in keybinds.txt except for JOY5+JOY8 "Prev_Tray_Alt" and JOY6+JOY8 "Next_Tray_Alt" . I also tried swapping the modifier buttons around with /controller_modifiers 8 7, and although the Right Trigger now worked, the Left Trigger stopped functioning. So it seems like a problem with the /controller_modifiers command. Ok. The Left Trigger is simply not working as a modifier key. DPadLeft+Rtrigger behaves as if only Rtrigger was bound. I tried these settings: /controller_modifiers 7 7 /extra_modifiers joy5 joy6 joy8 to see if I could get the Right Trigger to work as an Extra Modifier button, but that didn't work either. So then I tried a different combination. /controller_modifiers 5 7 /extra_modifiers joy6 joy8 This allowed both triggers to work, but now the Left Bumper didn't work. Ok. The problem is definitely the /controller_modifiers command. What if we got rid of /controller_modifiers completely, and just used /extra_modifiers for both triggers and bumpers? So I tried: /controller_modifiers 21 22 /extra_modifiers joy5 joy6 joy7 joy8 IT WORKED!!!!!! ALL BINDS AND BUTTONS ARE WORKING CORRECTLY!!!!! EUREKA!!! Holy crud, this was a real headache! I set the /controller_modifiers to JOY21 and JOY22 because I've never seen any weird key or button name for those pop up when testing in the game's Options--> Keymapping tab, and it's best to get the controller modifiers out of the way just in case they cause trouble in the future. Additionally, the buttons on an XBox Wireless Controller only go up to JOY12. However, I have seen JOY24 and JOY25 pop up in the Keymapping tab over the years. Just FYI. ******************************************************************************************************************************************************** So to sum up how I got the gamepad binds to work on my Xbox Wireless Controller... 1) Reset all keybinds (/unbindall). Then use /bindsave to overwrite keybinds.txt. This is to clear keybinds.txt of any button names that have been previously tagged as modifier buttons (i.e., JOYMOD or EXTRAMOD). We don't want those loading in from somewhere to accidentally mess things up. Alternately, you can go through keybinds.txt yourself (located in C:\Games\Homecoming\Setup\Live\ ) and delete all modifier binds you find, then save the file. 2) Set /control_modifiers to use buttons that will actually never be pressed/used (such as Joy21 and Joy22). For example, /controller_modifiers 21 22. 3) Use /extra_modifiers to assign all triggers and bumpers as modifier buttons. For example, /extra_modifiers joy5 joy6 joy7 joy8. 4) Place any modifier key/button first at the beginning of a bind string, before any other key/button names when using modifier/chord binds (i.e., ModifierButton+ButtonName). 5) Place all modifier/chord binds at the top of any bindfile being loaded into the game (before any single button binds). Edited yesterday at 10:48 AM by BlackSpectre Black Spectre - A Dark Defender's Home on the Web • The Advanced Bind Guide • The Masters of BAF: A Guide for Leaders and Players • The Wiki List of Slash Commands
BlackSpectre Posted yesterday at 10:20 AM Author Posted yesterday at 10:20 AM (edited) The patch notes for Issue 27 Page 1 (November 2020) state: Quote The up-to-four 'Extra Modifiers' are just additional inputs (either keys or buttons) that can be treated as modifiers when no other modifier is pressed. So for example, you could do /extra_modifiers LBumper RBumper to make the bumpers modifiers on your XInput gamepad. You could then use (for example) LBumper+Joy1 as a /bind (but also still be able to use LTrigger+LBumper as a separate bind). This does not appear to be the case. The above seems to be saying that a bind such as EXTRAMOD1+EXTRAMOD3 would not work... but it does. Or perhaps it's saying JOYMOD1+JOYMOD2 won't work... which might make sense if they're talking about conflicts with virtual mouse mode, but there's no indication of that. Looks like the XInput API was added to Homecoming in 2020. The new GameInput API was released in 2021. Just throwing it out there, but this might be the cause of some of the problems. That said, the whole gamepad system seems to be a bit unstable, necessitating restarting the game when it goes awry. Things like the mouse cursor dissapearing or zooming in and out not working while in virtual mouse mode, extra modifier buttons not working until the left analog stick is moved, etc. Edited yesterday at 11:11 AM by BlackSpectre Black Spectre - A Dark Defender's Home on the Web • The Advanced Bind Guide • The Masters of BAF: A Guide for Leaders and Players • The Wiki List of Slash Commands
BlackSpectre Posted yesterday at 11:30 AM Author Posted yesterday at 11:30 AM (edited) On 9/5/2025 at 12:20 AM, UltraAlt said: It allows for the Logitech F310 to trigger all 10 buttons in the active tray (six click-attack powers per tray, with macros in each tray to flip between tray 1 and tray 2 and trigger healing insps, fast travel [click left stick], and slow travel [click right stick]) as well a buttons for click on the blue hand, target near, target next, auto run, jump. The stick directions are set for moving and adjusting camera angle. Now that I've re-created @Telephone's gamepad binds, I see what you mean. Their gamepad binds can only activate power slots 1-8 and inspiration columns 1-4. It's a huge limitation not being able to use power slots 9 or 0, or inspriation column 5. I'm now gong to take a much closer look at your binds, UA. I might not recommend @Telephone's binds at the wiki afterall. I need a set of gamepad binds that work for as much of the game as possible as a starting point for players. Quote I tried using the X-input with the Logitech F10, but that had issues. The Logitech F310 can be configured so that the game thinks it is keyboard and that seems to get around the weirdness issues of using X-input. Honestly, I think that a controller whose buttons emulate keyboard keys might be the better way to go right now. I bet there's some software that could do it. OK, I'll start looking for it... UPDATE: Wow, that was fast! I already found some apps that will turn gamepad buttons into keyboard buttons: For Xbox controllers only: Xbox Accessories app (free) For all controllers: AntiMicroX (free) DS4Windows (free) JoyToKey (paid) reWASD (paid) There's some that can supposedly be used on a Mac too: Enjoyable (free) Gamepad Mapper (paid) Joystick Mapper (paid) AntiMicroX (free) I haven't tried any of them so I can't recommend any of them. Double check whether or not the app supports your specific gamepad. Edited yesterday at 12:10 PM by BlackSpectre OMG! So many typos! All the time!!! LOL Black Spectre - A Dark Defender's Home on the Web • The Advanced Bind Guide • The Masters of BAF: A Guide for Leaders and Players • The Wiki List of Slash Commands
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now