Jump to content

EliDirkx

Members
  • Posts

    10
  • Joined

Everything posted by EliDirkx

  1. ...and now after a reboot, it refuses to recognise the side buttons AND the DPI up/down buttons but still recognises the actual mouse. WHAT?
  2. Very curious. I did as you did and went back to 3.38 and now my Scimitar's recognised again without a hitch.
  3. Additional note: for some reason the up/down buttons ACTUALLY switch DPI/performance profiles despite iCUE not detecting the Scimitar Pro RGB mouse.
  4. Been using this gaming mouse since 2017 and for some reason now it's not being detected at all, disabling me from using the number buttons which I use as shortcuts all the time. Curiously, the K55 keyboard I've bought in January is detected without problems. I'm uninstalling iCUE now and gonna try to reinstall it to see if it clears up the issue. ...and it didn't. Anyone got any tips?
  5. Ahh, found the issue. I reinstalled my Dropbox as of late and as such some folders were linked through symbolic links. I deleted that specific folder and then started anew, and now my profile issue is fixed! Thanks for your assistance.
  6. Sadly, that doesn't seem to have made a difference. After an installation repair it's still resetting and, indeed, clearing the left side panel of previous profiles.
  7. Since the last iCUE update I did, using my Scimitar Pro RGB I got back in 2017, it seems that iCUE resets itself each time it starts back up. It's not saving any of my profiles, I have to manually load them from their folder each time because they don't even show up in the list. What's going on, is this some sort of a glitch?
  8. So this is something I've had happen to me once before, but while I've assigned my Corsair Scimitar Pro RGB's number keys to specific number and symbol keys, sometimes when I boot my system up it doesn't fail to see the mouse as being connected but it does fail to recognise the use of these number keys for some reason. Plugging it back out and in doesn't make a difference when it comes to that, nor does restarting the software, just a hard reboot will do the job. Is this a firmware issue with the mouse, an issue with the current version of iCUE or what? This didn't really happen often before, so I'm kind of wondering what's the deal with this. Thanks for your time.
×
×
  • Create New...