

- #Logitech g710 macro buttons not working in swtor how to
- #Logitech g710 macro buttons not working in swtor software
- #Logitech g710 macro buttons not working in swtor code
One solution for this is to map keys using a software that loads a pre-configured profile into the G600 and maps the pre-configured profile to a config file that the user wants. So what you did on windows was change the value similar to REP_DELAY on Linux which changed the delay.

What the issue above is they want BUTTON_DOWN to map to KEY_LEFTSHIFT↓ and BUTTON_UP to map to KEY_LEFTSHIFT↑ which doesn't seem possible with how the on board controller is written even on windows the issues is present. With out a KEY_DOWN and KEY_UP pair the profile gets corrupted and the key event is pulled from the next register in memory. SO KEY_LEFTSHIFT↓ + KEY_A↕ + KEY_LEFTSHIFT↑ is needed. The problem is REP_PERIOD and REP_DELAY which effects the repeat per cycle.Īlso the fact that the mouse emulates key press stokes with KEY DOWN and KEY_UP Action. Note both of these options will add a few seconds of delay as it will go from kernel -> program -> virtual key press. You will have to compile modify it but It's a place to start.

#Logitech g710 macro buttons not working in swtor code
Would someone mind helping this code noob out and posting the exact code that I can paste into GHub script? This is my own sad attempt:įunction OnEvent(PROFILE_ACTIVATED) -KEY_NUMLOCK KEY_RESERVED -KEY_NUMLOCK endīased comments and some of my testing the built in macro system sends out a repeat of the macro every ~500-1000ms. an existing key." I've messed around with variations on the scripts previously mentioned with no luck.
#Logitech g710 macro buttons not working in swtor how to
Creating the macro makes complete sense but I'm not sure how to "change KEY_RESERVED to. This is my first time scripting but I would really like to implement this workaround so my G600 can have a modifier key. Now use the modifier macro as originally intended I also tried F1, but there were some cases were things like menus were triggered.įind a key that isn't a modifier and won't do anything to your workflow when pressed/held and put it between the press and release of the modifier key in the macro. When the button is being held though I can input another key, like A and I get a select all command. Now when I press that button numlock is of course triggered, but I don't really care as my keyboard doesnt have a numpad. I found the workaround using KEY_RESERVED would not be accepted by the device, however, if you change KEY_RESERVED to instead be an existing key that you never use you can get modifiers like ctrl to work.įor example, I bound the macro ctrl down + numlock (down and up) + ctrl up to a button.
