Now when setting up my voice comm push-to-talk, rebinding them now associates it with a typically unused input, and ends up being configured as "Unknown" (Mumble), "UNK135" (Discord), or "135" (TeamSpeak).
So now, instead of sending a "Back" command, I'm now sending a F24 keystroke. For my configuration, however, I don't have any obvious functionality assigned to F23 and F24 despite having some functionality with fn-F12 that turns off my keyboard backlighting. Most computers/keyboards only have F1-F12 keys, with perhaps a function key to get another 12 keybinds. Logitech G Hub apparently recongizes F keys, at least on my laptop, up to F24. So, if I was alt-tabbed to a web page while talking, I'm suddenly looking at a very different page, like perhaps my home page. This led to instances where I'd press back to talk, and then whatever window I had active would receive a back command and execute it as applicable. So, the specific problem I was trying to solve was that I use the back and forward buttons on the side of my mouse for push-to-talk keybinds on my various voice communication software while gaming.
0 kommentar(er)
