Zirq

Most programs don't recognize F13-24, unfortunately. Your best bet is to assign them obscure combinations (ctrl+shift+y, etc), or something else unused in your program/game, and assign that same combination to the function in your program or game you want it to perform.

Since you've reverted, this doesn't much matter, but might help someone else until it's fixed. Minimizing iCue is the only reasonable option for me due to the fact I have an 115i v2 (among other things) and multiple profiles I hadn't backed up recently enough, however just minimizing did nothing. Going to the settings page of iCue, THEN minimizing drops my 15-18% cpu down to 4-6%.

All good now, super happy! In case anyone has a similar issue (on a newer-ish chipset, I assume the similar issue remains from the older systems), the solution: Support got back to me and suggested I uninstall CUE, then run CCleaner, restart, and then reinstall. I had previously reinstalled CUE, but did not run CCleaner or clean out remnants in the registry by hand. Feeling derpy, as I didn't think of that myself, I did it. My Scimitar now appears to be back to working order (no more random Malfunction status), complete with prompt detection from CUE on boot. Conclusion: CUE got corrupted by a forced shut down of the system, however it presented stronger symptoms of firmware being corrupted on a single device, instead of itself.

Chipset, bios, and windows are all up to date. I also uninstalled and reinstalled CUE since my last post. As far as I'm aware, there's no 3rd party USB controller. Device manager only says Intel USB 3.0, along with the normal generic listings. As it's not expressly stated anywhere I've seen in the manual or website, I'm assuming there isn't. I realized there may be pertinent information I left out previously, too. This occurred immediately after I had to do a hard shutdown on my computer (power button held down) due to a program freezing up my system and not ending, and preventing a simple restart. The next time I turned on my computer, the previously stated happened. The program that froze was trying to create and image a flash drive. I have no idea if that actually somehow caused this, or just a coincidence. I really don't want to drop down to the previous firmware, as I was having trouble with the laggy non responsive cursor (less once I disabled lighting). That would be a hard decision-Wait 5 minutes for the mouse to possibly work each time I boot, or have to unplug/replug in the mouse in the middle of whatever I'm doing, randomly. Hopefully all I need is a hard reset of the mouse.

So, I guess it's not working anymore, as my mouse completely doesn't work now. At all. I turned on my computer, and had no mouse. However, a popup from CUE came up, telling me there was a firmware upgrade available for my Scimitar (though the mouse doesn't exist in CUE). Having zero other options, I said sure (after plugging in a different mouse, as tab, etc, don't work on that dialog box). It's now stuck on 3% updating. It's updating to version 2.01, which, unless a new one just came out in the last day or two, I already had. Logs attached. I've restarted a couple times. Edit: I walked away for five minutes because I was angry. When I came back, CUE sees the mouse, but it's set to malfunction. I have a Z97 chipset motherboard, not the older systems having issues before. Except for an additional hard drive I added, my listed specs are current. Edit 2: I restarted, then walked away again, when the Scimitar didn't show up. Came back 5-10 minutes later, and it's listed as working normally-all buttons work. I put a ticket in with support, but I don't know what that will do, as sometimes it works, sometimes it doesn't, and it shouldn't take 5 minutes to know which it's going to do. I thought this issue was only happening on the 5+ year old systems? Not that that's ok in anyway whatsoever, either. Of course this happened just as support closes for the day, too. 2016-02-23T15-39-59.txt 2016-02-23T16-43-26.txt 2016-02-23T16-45-09.txt

Yeah, so far the laggy and unresponsive clicking has been fixed for me as well, since I received the beta FW and SW. My only issue since then is the macro keys stopped working-the Scimitar disappeared from CUE until I restarted CUE. This has only happened once in the last month, and not at all since the current version of CUE (I think it's a newer version than the beta was? And yes, I submitted the log files when that happened). I don't doubt some people still have issues, but just wanted to share it's not entirely doom and gloom now!

I was having a lot of these issues, but most of them haven't cropped up for me for awhile now. I have no idea if I'm lucky and this is a coincidence, or if it's actually what fixed it. Macro buttons randomly not working until a system restart: I plugged the mouse into USB 3.0. This was mostly luck. It was plugged into usb 2.0 in the back of my PC, but I moved it to the front so I could unplug/replug it easily, due to other issues. This may just have to do with the fact that the two types of USB are also different drivers, more so than the fact it's 3.0, I have no idea. I don't think I've had an issue with macros for 2+ months since I've done that (if I have, it wasn't while playing a game, so I didn't notice). I never had an issue with them being unable to issue keyboard commands, however, so even if this helps, I have no idea if it would help that. For laggyness and choppiness: a solid lighting scheme made the mouse work for longer periods of time for me. I'm currently using the beta firmware and software that's mentioned above, and that's tentatively fixed this entirely for me, as well.

I'm also using the beta firmware and CUE software. So far so good. Previously I was able to cut the issues down to every couple weeks by using solid lighting. I could consistently cause choppiness and buttons not working within 0-24 hours by turning on rainbow or color shift lighting, however. I'm at hour 7 now with no issues, and rainbow lighting on (trying to provoke it).

That specific software and firmware doesn't work for everyone, myself included. But thanks for posting it for the people it does work for.

I don't remember if I tried that when I first got the mouse, and ruled it out, but in general, no I haven't. I'm much more inclined to use an old mouse than an old keyboard if it came to that =x. I'm one of those useless replies this time, sorry!

Yup, unplugging, plugging back in the mouse sometimes fixed the issue, if not, restarting CUE fixed it for some others. I usually have to actually restart my computer to get the macros working again once they quit. But one of those solutions will probably work for you.

I have no idea if you're on to something, but my situation does fit this as well. I've had issues with the Scimitar from almost day 1 of getting it, and I've been running a clean/not upgrade Windows 10 install.

That's actually the conclusion I came to. I think it's done it once, maybe twice, since I changed my Scimitar to a solid, unchanging, color scheme. Much more rare than once every few hours-couple days, at the least.

I haven't had an issue yet with lag or choppiness since switching to a solid, non changing, color scheme on Oct 14. However I've lost macros again (nothing else happened at the same time, this time). I tried changing the polling rate from 1k to 500, and back, and they did not return. Restarting CUE also did not fix it, and neither did unplugging/replugging in the mouse. I had to restart my computer to regain them again. All profiles, including default, loses working macros when this happens, to be clear (shouldn't be an incorrectly assigned profile issue). The log has nothing with Mouse LED colors change failed, this time, so I'm guessing it's an entirely different issue. Should I post any future issues with macros in a different thread? 2015-10-17T19-00-58.log.txt

Something a little different happened this time. No lag or choppiness, but the macro buttons stopped working, and all lighting on the mouse turned off. Don't know if this is related, or an additional issue, but the log contains the same "Mouse LED colors change failed", along with new stuff, so I'm attaching yet another log in this thread. Unplugging the mouse and plugging back in resolved the lighting, but macro buttons do not work at all anymore, even after restarting CUE. Edit: Restarting computer regained use of the macros. 2015-10-14T18-32-52.log.txt