Jump to content
Corsair Community

Scimitar - Random Side Keys not work after reboots with new CUE (2.20.72)


Saucermote
 Share

Recommended Posts

I updated the CUE software to the newest version a few days ago hoping it would fix some issues I'm having with my scroll wheel (looks like that may be hardware related unfortunately).

 

Anyway, after each time I start windows (Windows 7 SP1 x64), some of the buttons I have assigned to the side buttons on my Scimitar mouse don't work. The one I notice immediately is the one I have assigned to minimize all (Windows Key + M). I can fix this by opening up the CUE software and just quickly opening the default profile and clicking through each of the actions once.

 

This also happens for some of the other profiles I have, and they are all pretty much direct 1:1 keybinds that don't work, like hitting button 11 for the letter "i" in a game I play.

 

Profile switching works fine, and most of the buttons work fine, but certain buttons just don't get recognized until I go into CUE and click through all the actions one by one each time I reboot.

 

Again, this didn't happen until the latest CUE software update (2.20.72).

It isn't the same side buttons either.My mouse has the latest firmware available.

 

If I could figure out this, and why my scroll wheel sometimes randomly scrolls in the wrong direction, I'd be a happy camper, but that is a very new problem and probably the subject of another post or support ticket. I've had the mouse since it came out, so the odds of a hardware problem on that one increase a bit.

Link to comment
Share on other sites

Right after installing the new update, on first run, the same keys didn't work until I clicked through the actions one by one again. Something is fishy here.

 

One of them is just "Windows Key + M" Bound to Key 7, and the other is the "I" key bound to key 11, in separate programs. There are probably others, but those are the ones I use enough that I notice them.

Link to comment
Share on other sites

It should be running as admin on my machine, but for the sake of argument, I've run it as admin explicitly, and it didn't help.

 

Here is the error from the log file.

 

2017-12-22T18:31:17 W cue.actions: Scoped command is empty, cannot execute action

 

Again this goes away if I open the actions section and just click through them one at a time each time I reboot/load up CUE, so it has the commands/info it needs, it just isn't loading it.

Edited by Saucermote
Link to comment
Share on other sites

  • 8 months later...
 Share

×
×
  • Create New...