Multiple macros cancel each other out

[Mortac]

So I've been using a Corsair keyboard and a mouse from another manufacturer. I've been using one macro toggle that repeats constantly on the keyboard, and a separate one on my mouse that repeats while I hold down the right mouse button.

 

So I figured to make it easier for myself, I'll replace the mouse from the other manufacturer so I'll have everything consolidated into iQUE.

 

Well, now that both my devices are Corsair, I've noticed that it's no longer possible to have 2 macros running simultaneously. They'll cancel each other out. Literally making my new device completely useless to me (and it will be returned unless this is fixable).

 

I was searching old threads and the only official reply I could find was from a couple of years ago where someone said that this is a limitation within the OS/Windows. I don't believe that one bit. How come it was working perfectly fine when I had two separate devices? How hard can it be to program proper input from different macros? I mean, other manufacturers can do this, so provenly it IS possible. There is even free software out there made by single people that can create several macros running repeatedly through any mouse/keyboard on the market, and yet Corsair, a world-wide billion dollar company can't do this? If Corsair keeps stating that then it's merely due to lack of knowledge, and not lack of possibility.

 

Please resolve this! I will be returning my new Corsair mouse and unless this is resolved I'll be switching to a different manufacturer entirely in the future that I know already supports the use of multiple macros running simultaneously.

[c-attack]

This is a glitch in v3.33 where other KB/mouse input interrupts held down or repeating macros. There has been a steady stream of threads for the last month. Fortunately 3.34 is now out and should resolve it. You can update from within the app or wait for them to post the download file on the Corsair site later today.

[Mortac]

I am already currently using iCUE 3.34.161 and a K70 keyboard and Harpoon Wireless mouse. Everything is updated. Using two separate macros does not work because one macro will interrupt the other. If this was supposed to be fixed, it isn't.

[c-attack]

You'll have to be more specific about what you are tying to do. The list of possible macro events is near endless. I am able to execute a long string from the keyboard, inject a short one from the mouse (hold), and the keyboard macro finishes. It may be specific to the type of action. On thing you can't do is simultaneous hold inputs.

[Mortac]

Two macros.

 

Keyboard: Press F8 to start a toggle-macro that presses 'w' once every 5 seconds, repeating endlessly.

 

Mouse: Hold right-click to "play while pressed" a macro that holds shift and left-clicks once, then releases shift and holds right-click for 2 seconds, repeating for as long as the button is held down.

 

If I start any of these macros, the other will be interrupted and stop until reactivated.

[c-attack]

I can't get this to work either. The toggle/endless repeat seems to override other functions. This is different than the bug in 3.33 where any key input interrupted the macro. I was able to do slightly better when setting up the F8=W as trigger on press. In that configuration the mouse input will still occur, but it seems continuous repeat actions/key presses can't be happening simultaneously no matter which way I try to set it up.

 

It's not clear to me if the toggle function is supposed to suppress the other macro or if this is an unintended effect of the prior issue. I will flag this for their software team to look at. Perhaps someone else who uses multiple repeating macros regularly can offer more insight into recent history, but I don't think the simultaneous repeats have been possible in CUE 3. You should still be able to make other input without derailing a repeating macro.

[Mortac]

Thanks! Like I said in the first post, I did some further research into this and read in an old thread that someone from Corsair said this was due to some sort of OS/Windows limitation. No way that's the case since I know other manufacturers support this, as well as 3rd party freeware out there can also accomplish this. This excuse doesn't hold. It's merely a question of how you approach the problem and resolve it. Certainly there are ways to make it work. And when I buy expensive hardware like this, and there are even heavily macro-oriented devices available, one would expect to be able to run more than one macro of this kind.