Paxon Posted March 17, 2018 Share Posted March 17, 2018 (edited) Hello! After the recent CUE update I've noticed that my action binds just stop working after a few minutes of CUE running. I have my PAUSE/BREAK key bound to cycle through profiles in the profile switcher. It will work fine within the first few minutes of launching CUE, but just stops working after a while for no apparent reason. Restarting CUE will make it work again for a few minutes but the same thing will continue to happen. I'm using a Corsair K70 LUX RGB on Windows 10 64 bit. UPDATE: Hey, hey! Same here. In another thread, it has been determined that using the keyboard's volume wheel, locks down macro keys, profile keys and other binds of the keyboard, along with dpi switching buttons on mice. So, avoid the volume wheel for now in 2.24.35. Stay away from the volume wheel for now until they fix this. Thanks PJH! Edited March 22, 2018 by Paxon Link to comment Share on other sites More sharing options...
ChrisSpencer71 Posted March 17, 2018 Share Posted March 17, 2018 Just upgraded to CUE 2.24.35 this morning and the same thing is happening to me. All of the additional buttons on my M65 and my Scimitar no longer work. Link to comment Share on other sites More sharing options...
PJH Posted March 19, 2018 Share Posted March 19, 2018 Hey, hey! Same here. In another thread, it has been determined that using the keyboard's volume wheel, locks down macro keys, profile keys and other binds of the keyboard, along with dpi switching buttons on mice. So, avoid the volume wheel for now in 2.24.35. Link to comment Share on other sites More sharing options...
odcjones Posted March 19, 2018 Share Posted March 19, 2018 I had the same thing after the latest update. Found a solution on this forum. type %APPDATA% in explorer, find corsair folder and rename corsair folder to corsair.OLD or delete it. Shut down CUE and restart the app. It makes a new corsair folder. My back and forward and DPI buttons are working again. Edit/Delete Message Link to comment Share on other sites More sharing options...
odcjones Posted March 19, 2018 Share Posted March 19, 2018 Hey, hey! Same here. In another thread, it has been determined that using the keyboard's volume wheel, locks down macro keys, profile keys and other binds of the keyboard, along with dpi switching buttons on mice. So, avoid the volume wheel for now in 2.24.35. yes confirmed. Solution mentioned by me earlier still works, but touching volumecontrole and its broken again. Link to comment Share on other sites More sharing options...
Paxon Posted March 19, 2018 Author Share Posted March 19, 2018 Hey, hey! Same here. In another thread, it has been determined that using the keyboard's volume wheel, locks down macro keys, profile keys and other binds of the keyboard, along with dpi switching buttons on mice. So, avoid the volume wheel for now in 2.24.35. Ah, okay thank you very much for this information! Does this include the mute volume button on a K70 or just the volume wheel? Link to comment Share on other sites More sharing options...
SajuukCor Posted March 20, 2018 Share Posted March 20, 2018 Can confirm upgrading to 2.24.35 broke the side buttons on my Scimitar and the Microphone button on my VOID Wireless. Tried uninstalling and reinstalling 2.24.35 but the issues persisted. Had to install 2.23 to get things back up and running correctly. Link to comment Share on other sites More sharing options...
xMacias Posted March 20, 2018 Share Posted March 20, 2018 Ah, okay thank you very much for this information! Does this include the mute volume button on a K70 or just the volume wheel? Just the volume wheel. Link to comment Share on other sites More sharing options...
its_sarco Posted March 20, 2018 Share Posted March 20, 2018 Hey, hey! Same here. In another thread, it has been determined that using the keyboard's volume wheel, locks down macro keys, profile keys and other binds of the keyboard, along with dpi switching buttons on mice. So, avoid the volume wheel for now in 2.24.35. @PJH I am glad I found this thread and reply. I would have never guessed with was the volume knob (i was starting to think it was my headset connecting and disconnecting) and I was getting a little desperate. Next step was about to be passing a large magnet over everything until something changes, lolol. Link to comment Share on other sites More sharing options...
frankekko1990 Posted March 21, 2018 Share Posted March 21, 2018 Hi, I have this problem too, where can I find the 2.23 driver? THANK YOU Link to comment Share on other sites More sharing options...
frankekko1990 Posted March 21, 2018 Share Posted March 21, 2018 I have the same problem when there will be the next driver update? Link to comment Share on other sites More sharing options...
Fezico Posted March 21, 2018 Share Posted March 21, 2018 Yep, my side buttons are not working as well. tried doing a clean reinstall an it temporarily fixed the backward side button and then stopped working again. Link to comment Share on other sites More sharing options...
Senton Posted March 21, 2018 Share Posted March 21, 2018 Same on K95 Platinum.. please fix. Link to comment Share on other sites More sharing options...
Inheritance Posted March 21, 2018 Share Posted March 21, 2018 Hey guys, yes there is a bug in CUE that causes actions to stop working if you adjust the volume with the scroll wheel. Exiting and restarting CUE should fix the issue. Link to comment Share on other sites More sharing options...
Juts Posted March 24, 2018 Share Posted March 24, 2018 Exact same issue with my k95. I touch volume and everything quits working. Can't even adjust brightness. Link to comment Share on other sites More sharing options...
Corsair Employees Corsair CJ Posted March 24, 2018 Corsair Employees Share Posted March 24, 2018 (edited) We're aware of an issue that has appeared in a recent build of CUE that can result in macros and other actions being broken. Here's a build that should resolve this for anyone effected: https://www.dropbox.com/s/9wxvd9t3dlhyvkr/CorsairUtilityEngineSetup_2.24.48_release.msi?dl=0 This is to be considered a beta build since it hasn't gone through our usual validation process. Edited March 25, 2018 by Corsair CJ Link to comment Share on other sites More sharing options...
Recommended Posts