iCue bugs

[SuperTRev]

Trying to make a mouse sniper macro.  So I put it on the qwerty keyboard tilda key, set it to toggle on/off, but it doesn't toggle the mouse sniper function off until I hit the key twice.

It enables sniper dpi on the first key press but doesn't disable it until two more key presses, instead of one more.  

 

Macroes won't remove themselves from an assigned key when clicking on their icon anymore.  Before if you wanted to disable an existing macro, you click on its assigned button on the keyboard gui, but now it's just stuck.  So when assigning a macro to a key, it's permanent.  I have to delete the macro to get it off the key, and then remake the macro later on if I want it again.  Instead of just clicking on the icon once more to remove it from that assignment.

[c-attack]

On 3/19/2022 at 12:53 AM, SuperTRev said:

Trying to make a mouse sniper macro.  So I put it on the qwerty keyboard tilda key, set it to toggle on/off, but it doesn't toggle the mouse sniper function off until I hit the key twice.

It enables sniper dpi on the first key press but doesn't disable it until two more key presses, instead of one more

I can't replicate this.  Using the mouse, tilde, and Assignment Trigger On/Off (Advanced), it properly snaps on and then off again with a single press of ~.  I can't think of a good reason for it to behave in the manner you described.  What is your KB/mouse model?  Perhaps try the standard repair install from the Windows Apps list.  That is the first thing to try and when CUE peripherals are misbehaving.

 

On 3/19/2022 at 12:53 AM, SuperTRev said:

I have to delete the macro to get it off the key, and then remake the macro later on if I want it again.

Yeah, this needs to be addressed.  I end up having to create/delete macros multiple times just so I can type the character letter in the response when testing -- like I just had to do now for ~.  There are likely many users who want to keep a stack of macros but not keep them all assigned.  

Edited March 21, 2022 by c-attack

[SuperTRev]

Hey, thanks for the reply.

I'm glad it's not just me, that you can't replicate that issue.  That tells me I can have it working somehow.  Having to hold down the key to enable sniper mode is annoying, and pressing the button twice to toggle it off is worse.  I will look into the standard repair you mentioned.

My keyboard is the K95 RGB Platinum.  The mouse is the NightSword RGB.

By the way, I have a new NightSword RGB mouse, because the old one's mouse wheel broke after like 8 months.  Now iCue calls it NightSword RGB (1).  Instead of just being able to forget the old mouse, it needs to put (1) there permanently.  You know, cause Corsair gets a kick out of pissing me off.

 

I did notice the new iCue gui shows an image of the assigned macro.  You can click on that to unassign it from the keyboard.  That's a downgrade from how it worked before, but still doable.

But the new assignments pane on the left is brutal.  Trying to use it is the worst thing I've ever used, for like ten reasons.  At least it's not destroying my macroes by itself now, like a previous iCue version was.

A long time I ago gave up on trying to report things to Corsair, but I had to mention these two recent bugs.

[c-attack]

OK, I was wondering if you had a mouse that did not have a native sniper button (Nightsword or M65) if this would prevent it from working.  Not relevant here, but testing this with my Dark Core SE it worked too.  On the mouse DPI tab I can watch the active DPI mode shift from between sniper and default as I tilde away repeatedly.  

 

Here is how I set it up.  There might be other ways.  On the hidden "selection screen" the mouse Sniper button is selected.  K100 + Nightsword.