Holyrood

I do not use ANY of the vanity features in ICUE and have all exes terminated from running except ICUE. running programs while installing graphics drivers?? are you a noob or what? ICUE crashed as nvidia was installing new drivers, latest, this has NEVER happened before in old ICUE, never. so please save your indirect nonsense for someone else. No programs were running. I find your attitude quite funny though.. you are not very clever and clearly cannot read between lines.. but hey you said your part as per usual on this forums the pro vanity software folk direct indirect blame. without providing any solutions. not really that "techy" are you... save it. ICUE is a joke. 100%. go enjoy your RGB Vanity ;) oh and hey, keep up the indirect blame game, sure it is going to work out for you guys ;) One more bug before I go. uplugging and plugging in k55 does indeed occasionally fix the caps, scroll, num lights issue. however more times than not it gives a Firmware error. Yes the software responsible for grabbing the correct firmware (as all devices are up to date) appears to have gotten it wrong, or not, who knows really as the software is trash. bottom line the lights remain off due to ICUE. I have troubleshoot these issues to the death.. there are no fixes for them. Spent the time trying to get them to work correctly. and that is the problem users come here as a last resort then get blamed indirectly like it is their fault... keep up the good work though! bye

they will learn this lesson eventually

^^ this 100%

disable all icue monitoring. use the programs independently, go download cpuid, for example.. all in one nonsense never works out well, clearly, as seen with ICUE ;) all you need to have running is ICUE.exe the software is just absolute trash, everyone knows. corsair still keep pitching their RGB vanity crap. instead of focusing on functionality and when users come to forums with technical stuff like this. its indirectly implied it is our fault... no logic and it basically says they not gonna change a goddam thing because you know vanity is cool now apparently..

installing the latest nvidia drivers crashed ICUE. opened up ICUE only seen glaive and m65 rgb pro as connected devices, ignoring k55 keyboard. I have disabled everything other than ICUE.exe. the other exes were absolutely pointless display adapter etc... while this has helped the performance of the K55 and M65 RGB PRO it has not stopped the M65 RGB PRO left click locking in place like it is stuck in toggle mode. k55 caps lock, num pad and scroll lock lights still stop working. unplugging and plugging the keyboard back in occasionally fixes it if corsair does not say stupid stuff like the k55 firmware is wrong... ??? really... how can ICUE the software responsible for getting the right drivers and firmware get THAT wrong?? rebooting pc always fixes lights issue.... meh to that there is a slight latency with ICUE cant keep up like old ICUE. I really miss the old icue never had any performance issues with it or issues with it in general. absolutely LOVED it! Corsair should have a real good think about making old ICUE compatible with all their new products and releasing it as a advanced version for techies. a real good think! I am not a fan of the direction corsair is taking their products. well made that they are however 100% let down by the vanity software corsair are intent in trending. Im out... vanity over logic. no thank you. im sure you are aware how much of a joke you have become on tech-literate circles online and offline due to your vanity software for your products. I for one no longer recommend you.

Hi I bought K55 and another M56 RGB PRO. I love the mouse and needed cheap keyboard. M65 RGB PRO has the same issue the last 2 I had. in that left click occasionally "locks" down press. resulting in over firing of guns, for example, in games. K55 caps lock, numlock and scroll lock lights stop working once icue is open on startup... firmware is up to date, software is latest. This is an annoyance. the lights function correctly until icue starts up. Old ICUE wont work with these new devices at all. plug them in and they dont work. plugin old M65, started working... the error related to this is a .dll file that is installed as I have all the MS redistributables installed, for work. I have cpuidsdk disabled is it ok to disable these also? Corsair.Service.DisplayAdapter? Corsair.Service I have not been able to find out what these are for exactly.... I am assuming icue is for the actual icue software and functioning of drivers? You guys should really have a good think about making all your products compatible with old icue and releasing that as an advanced option for users...

Does Corsair plan to allow left click button to be remapped to another button, sniper button for example on m65, in the current CUE? I'd like to point out that in CUE v1.16.42 you allowed your users to do this. I have had no problems whatsoever having left button bound to sniper button while using macro on left button and continue to... it has been years now and still i see left button greyed out.... why the decision was made to stop left button being remapped in the first place? This was a unique feature in 1.16.42 why I chose Corsair over Razor...

Also please ditch features being hidden ie Advanced feats. Just declare all feats. i really do not get why dev guys have chosen to "hide" advanced stuff. it is one icon....

First thing I have noticed is I cannot seem to set left click function to sniper button (to free it up for macro), which was very easy and straight forward to do cue v1.+ Cannot set up an autoclick macro at all for left click. I own M65 RGB PRO and GLAIVE. The settings are universal for each within a working/current profile they are not separate. I click dpi change button on M65 it is also changing it on GLAIVE. I change color scheme for GLAIVE it does it for M65. It does not matter which mouse is selected at top. no rainbow lighting option in advanced.. why? The only thing that does not change is custom dpi settings for each. Please address the above. This CUE version seems very much a work still in progress. Downgrading back to Corsair-Utility-Engine-v1.16.42 till v2 is improved.