ShaithEatery Posted October 19, 2014 Share Posted October 19, 2014 It may very well be me doing something wrong here, but I've played around with several settings in Corsair Utility Engine, read the section of the manual on creating macros and keystrokes, and I've searched for others having similar issues to no avail.... I'm trying to do just some basic key assignments to the G-Keys on my RGB K95, and it seems like the functionality I'm trying to setup is just plain not working. For example, I will create an action under Keystroke to have G1 input Alt-1. Once created and assigned, it will not input the programmed keystrokes at all in any program (manually selected the profile so it is not autoswitching to a different profile or anything). Next, I try to create a macro of hitting alt and 1 at the same time, and still no response in anything. I can, however, assign lighting for that action and it will happen on my keyboard just fine, just not the actual keystroke or macro. I can successfully assign shortcuts to applications and even create a text input that respond and act as normal, but I'm really trying to get a macro or keystroke to work like it should. Any thoughts? Link to comment Share on other sites More sharing options...
ShaithEatery Posted October 19, 2014 Author Share Posted October 19, 2014 Well...um, after a simple restart it seems like it's all working as normal. Not quite sure how to explain it, but I'll take it! Link to comment Share on other sites More sharing options...
StaticVoidMain Posted October 19, 2014 Share Posted October 19, 2014 From what I have observed, and from what people are suggesting, you should expect that because the macros are stored in Windows. I keep asking them if they can move macro execution to the keyboard but it seems it won't be supported. I always had that problem with software-based macro execution - from the early days of membrane gaming keyboards up to this keyboard. With on-board macro execution, never had this problem ever again. Very snappy. It can also be caused by badly written drivers. I have had this problem with the M95 - which also seems to depend on Windows (and I thought it had on-board). Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.