ryguy36 Posted September 17, 2020 Share Posted September 17, 2020 I've got IroncClaw RGB mouse. My two side buttons are mapped to Volume Up and Down. As of the 3.33.246 update, pressing and holding the buttons no longer applies more the longer I hold them. When I press and hold the buttons, it only adjusts the volume by 2, instead of iterations of 2 the longer I hold it. I didn't see this change in the patch notes and this is the only change to my computer I've done lately. Aside from reverting to an old version, is there something else I can do? Thanks Link to comment Share on other sites More sharing options...
jaypullups Posted September 17, 2020 Share Posted September 17, 2020 Did you revert to an old version or find a fix? Link to comment Share on other sites More sharing options...
c-attack Posted September 17, 2020 Share Posted September 17, 2020 The “hold key interrupt” is a bug in 3.33. A fix is coming, but you’ll have to wait for 3.34 in a few weeks or roll back to 3.32 for an immediate solution. Since profiles and settings are not backward compatible, rolling back does mean setting up iCUE like a new install, reimporting profiles, etc. Link to comment Share on other sites More sharing options...
ryguy36 Posted September 17, 2020 Author Share Posted September 17, 2020 The “hold key interrupt” is a bug in 3.33. A fix is coming, but you’ll have to wait for 3.34 in a few weeks or roll back to 3.32 for an immediate solution. Since profiles and settings are not backward compatible, rolling back does mean setting up iCUE like a new install, reimporting profiles, etc. Thank you for that update. Do you have a source of where it's identified as a bug ? I don't mind waiting a few weeks. Thanks again Link to comment Share on other sites More sharing options...
c-attack Posted September 17, 2020 Share Posted September 17, 2020 There are some other users discussing the problem in the thread below. That's the only thing I can share. https://forum.corsair.com/v3/showthread.php?t=199751 Link to comment Share on other sites More sharing options...
badalice Posted November 2, 2020 Share Posted November 2, 2020 It's 34 version and still the problem exists. Link to comment Share on other sites More sharing options...
indyjones83 Posted June 5, 2021 Share Posted June 5, 2021 4.11.274, almost 10 month have passed and still the problem persists. I'll roll back again.. Link to comment Share on other sites More sharing options...
Thysell Posted June 5, 2021 Share Posted June 5, 2021 I went back to version 3.31 to fix the issue. Corsair is aware of the issue, but we're approaching a year without a fix. :sigh!: Link to comment Share on other sites More sharing options...
computerchkn Posted February 13 Share Posted February 13 This issue was reported 2 months ago and they still haven't fixed it. I just bought a Ironclaw and I'm shocked this isn't an option to have. I think I'll switch back to my logitech Link to comment Share on other sites More sharing options...
wyrsek Posted March 26 Share Posted March 26 So, as best I can tell, there's still no resolution for this. Anyone know of a fix outside of "find an older version of the software and use that instead"? Link to comment Share on other sites More sharing options...
HumbleSage Posted April 22 Share Posted April 22 Here we are.... April 22, 2022. Still no fix for something that should have been resolved in a minor build ages ago. Unbelievable. I mean utter silence on this issue from Corsair. Sticking with 3.33 until it's resolved. Think I'm going to have to stop buying Corsair products if they can't even fix (or at the very least EXPLAIN) this issue. Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now