Scimitar problems

Hi! Having the issue, same thing in logs everyone else sees (nothing I can find but those pages and pages of "request timed out" messages). I note: The mouse buttons DO work when this is happening. They're just really, really, slow. It can take about a second of pressing before the press registers, and a release can also take quite a while to register.

 

Set to 500Hz, and it did happen after a while, but I believe it took significantly longer. I'm now at 250Hz and will see what that does. I'm expecting it to take even longer at that point, but I bet it'd still happen if I left things up for a day or so.

 

Note: Can't change settings when the mouse is doing this, because any attempt to change something like polling settings causes the mouse to eventually crash, disconnect, and reconnect as a generic HID device. (Although I think the settings may actually make it to the mouse, for when it next comes up.) When that happens, CUE crashes also, but if I restart cue, it comes up fine... but doesn't see the mouse.

 

CUE 1.12.75, mouse is 1.06/0.02 firmware/bootloader. Problem has existed as long as I've had mouse, never had different software versions.

 

Side note: You know what would be super convenient? A quick way to assign keys on the mouse to "the next key I hit", or just a "set thumb buttons to numeric keypad" button.

 

Also, although this applies more to things like the keyboard, it might be handy to have a way to apply something like a gradient effect to a range of keys. So, doing the gradient over space, not time. (So, say, you make a rainbow gradient, then apply it to "all the keys", and then they just have static lighting that's a smooth gradient, instead of having to manually adjust colors of keys.)

It occurs to me: The rate of those messages appears very close to the rate at which messages would be sent for the "rainbow" color I'd selected for the mouse's lighting. I've set it to all solid colors and will see whether I still see it.

It occurs to me: The rate of those messages appears very close to the rate at which messages would be sent for the "rainbow" color I'd selected for the mouse's lighting. I've set it to all solid colors and will see whether I still see it.

 

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.

For what it's worth, after turning off the lighting I haven't had it crash in over a day. Previously it was requiring me to reseat the USB a few times a day.

I have the exact same issue. I am running the scimitar with a K65. If someone tells me a real easy way to upload log files I will, but I'm not gonna work too hard at it.

Settings > Support > View Logs.

 

It will open up a file explorer window with the log files it has generated. Move them to the desktop then to upload, click 'go advanced' and manage attachments > choose the log from desktop > add.

Really frustrated, after one day with the mouse, none of the side buttons are working an any circumstance. They are remapped to 1234567890-=, and for the first day they were fine. I took the advice to change the lighting profile to a solid color and that didn't help either. Here's the log, I hope it helps. It also kept telling my log was an invalid file, so copy pasted. >.>

 

[2015-11-26T06:00:25]: MacroCommand/Win: Cannot open driver device.

[2015-11-26T06:00:25]: UserSessionInfo: locked changed to 0.

[2015-11-26T06:00:25]: UserSessionInfo: connected changed to 1.

[2015-11-26T06:00:25]: UserSessionInfo: local changed to 1.

[2015-11-26T06:00:25]: UserSessionInfo: locked changed to 0.

[2015-11-26T06:00:25]: UserSessionInfo: connected changed to 1.

[2015-11-26T06:00:25]: UserSessionInfo: local changed to 1.

[2015-11-26T06:00:25]: Device profile (meta) for device vid=1044 pid=7a06 not found.

[2015-11-26T06:00:25]: Device profile (meta) for device vid=1044 pid=7a06 not found.

[2015-11-26T06:00:25]: Failed to open device: vid=1b1c pid=1b1e path=\\?\hid#vid_1b1c&pid_1b1e&mi_00#7&16893e06&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}

[2015-11-26T06:00:25]: Device profile (meta) for device vid=1044 pid=7a06 not found.

[2015-11-26T06:00:25]: Device profile (meta) for device vid=1044 pid=7a06 not found.

[2015-11-26T06:00:25]: Device profile (meta) for device vid=1044 pid=7a06 not found.

[2015-11-26T06:00:25]: Created new device object: Scimitar; ready: 0

[2015-11-26T06:00:25]: Attached to device object Scimitar: b=1 a=0

[2015-11-26T06:00:25]: Initializing Scimitar...

[2015-11-26T06:00:25]: Failed to open device: vid=1b1c pid=1b1e path=\\?\hid#vid_1b1c&pid_1b1e&mi_01&col01#7&29b95a44&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}

[2015-11-26T06:00:28]: Initialized (st=1) Scimitar.

[2015-11-26T06:00:28]: Attached to device object Scimitar: b=0 a=0

[2015-11-26T06:00:30]: Device insertion processing complete for Scimitar.

[2015-11-26T06:08:51]: Device vid=1b1c pid=1b1e is marked 'slow startup'.

[2015-11-26T06:08:51]: Device vid=1b1c pid=1b1e is marked 'slow startup'.

[2015-11-26T06:08:51]: Device vid=1b1c pid=1b1e is marked 'slow startup'.

[2015-11-26T06:08:51]: Device vid=1b1c pid=1b1e is marked 'slow startup'.

[2015-11-26T06:08:51]: Device vid=1b1c pid=1b1e is marked 'slow startup'.

[2015-11-26T06:08:57]: Created new device object: Scimitar; ready: 0

[2015-11-26T06:08:57]: Attached to device object Scimitar: b=1 a=1

[2015-11-26T06:08:57]: Attached to device object Scimitar: b=1 a=0

[2015-11-26T06:08:57]: Initializing Scimitar...

[2015-11-26T06:08:57]: Failed to open device: vid=1b1c pid=1b1e path=\\?\hid#vid_1b1c&pid_1b1e&mi_00#7&16893e06&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}

[2015-11-26T06:08:57]: Failed to open device: vid=1b1c pid=1b1e path=\\?\hid#vid_1b1c&pid_1b1e&mi_01&col01#7&29b95a44&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}

[2015-11-26T06:09:00]: Initialized (st=1) Scimitar.

[2015-11-26T06:09:01]: Device insertion processing complete for Scimitar.

[2015-11-26T06:13:21]: Failed to translate event 'Press key 0'.

[2015-11-26T06:13:22]: Failed to translate event 'Press key 2'.

[2015-11-26T06:13:22]: Failed to translate event 'Press key 0'.

[2015-11-26T06:13:22]: Failed to translate event 'Press key -'.

[2015-11-26T06:13:22]: Failed to translate event 'Press key 0'.

Yep this is still happening for me as well after changing around some of the stuff mentioned in this thread. Any update on this gamebreaking issue? :(

Yep this is still happening for me as well after changing around some of the stuff mentioned in this thread. Any update on this gamebreaking issue? :(

 

Nope. Henry posted on the 24th and i they are most likely all out of the office as it is thanksgiving week.

Edited November 28, 2015 by Inheritance

I'd like to throw in my issue as well. It has been happening exactly the same as everyone else in this thread, including the message in the logs. I'm attaching the most recent log to this post. Also, I'm running CUE 1.12.75, but this has been happening since I received the mouse after pre-ordering.

2015-11-26T14-25-30.txt

I switched to lighting on, but disabled the rainbow color change, and it's been about a day, no crashes. Have now set mouse back to 1ms polling rate, and will see whether it crashes anymore. It did seem that frequency of lockups was sort of linear with polling rate.

 

I am reminded of a bug I encountered once in a Unix system long ago where changing console text color very often would eventually crash, because there was a memory leak.

I am having the same issue as others in this thread: mouse cursor will occasionally stutter and it will not be possible to click anything.

 

I've found that unplugging the mouse and plugging it back in fixes this issue right away, but it was getting annoying to do this each time since it has been occurring frequently.

 

I just uninstalled the CUE yesterday, and so far the issue has not occurred again. Hoping that they come out with a patch for whatever it is that is causing this issue.

I have the exact same issue, lights stop changing/1-12 left and right click stop working and the mouse skips all over, it sucks because I just got this yesterday and I love it but it looks like I'm going back to the G600. >.< Edited December 2, 2015 by CPZ9

There are reports of this issue and we are looking into this, but we were only able to duplicate it on a few systems (not all). Since it's inconsistent and not 100% reproducible, we will need more time to investigate the problem. Thank you for understanding and your patience.

 

I have owned this mouse for over 2 months and have only started to recently experience this problem so maybe my observations can help shed light on this issue. (CUE and firmware are at the latest version.)

 

At the time I started using the mouse, my computer was on Windows 7--the mouse operated perfectly.

One month into owning the mouse, I upgraded to Windows 10 while keeping my current settings--the mouse operated perfectly.

 

Seeing how my computer felt kind of cluttered, I decided to "reset" my Windows 10 via the "Reset this PC"-->"Keep my files" (Removes apps and settings, but keeps your personal files). After doing this, my mouse exhibited this exact same problem for the first time (within the first day of use).

 

I reported this issue to my friend, who also purchased this mouse, and he told me that he gets it all the time. He said the quick fix to this is to simply unplug the USB cable and plug it back in. AND IT WORKED.

 

Although we both owned this mouse for 2 months, my friend has long suffered this problem whereas I am only now facing it. What can explain this difference? He performed a clean install of Windows 10 when he first started using the mouse. I performed a clean install only 2 days ago.

 

As a result, I believe there is something missing (or some setting) from a clean install of Windows 10 that leads to this issue. Whatever my old state of Windows 10 had, it didn't run into this issue. Undergoing a clean install of Windows 10 has introduced me to this problem.

 

[EDIT: Another possible factor: After the clean Windows 10 install, I started using a new Logitech RGB keyboard. I don't think this is the culprit since my friend uses a Corsair keyboard.]

Edited December 3, 2015 by jltaser

As a result, I believe there is something missing (or some setting) from a clean install of Windows 10 that leads to this issue. Whatever my old state of Windows 10 had, it didn't run into this issue. Undergoing a clean install of Windows 10 has introduced me to this problem.

 

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.

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.

 

He might be onto something yeah. I have Windows 10 as well, installed about 2 months ago and my issue with the Scimitar started from the first day I got it.. so it could be a Win10 problem/conflict maybe.

I am also having this issue. The cursor will stutter, and no mouse buttons will work, and I have to unplug-replug it in. I'm still within my 30 day return window and seriously considering returning it...

 

Just now I've gone to Settings -> Device -> Disable Device Lightning to see if that stops the problems. Although I hate not having the lighting, but the mouse dying in the middle of a game is totally unacceptable.

I tried disabling all lighting, and also just using a solid color. Neither of these have worked. By the way I'm on Windows 7 (some people were speculating it was a Windows 10 issue).

I've had the Scimitar for a couple of days now, I haven't noticed any issue like this so far. But I am using Windows 8.1, I'll keep an eye on it. I do plan to upgrade to Win 10 soon too.

I am also having this issue. The cursor will stutter, and no mouse buttons will work, and I have to unplug-replug it in. I'm still within my 30 day return window and seriously considering returning it...

 

Just now I've gone to Settings -> Device -> Disable Device Lightning to see if that stops the problems. Although I hate not having the lighting, but the mouse dying in the middle of a game is totally unacceptable.

Talk about timing, after having posted that I did not have the issue I just had it a few hours later. I was looking at some Amazon tabs in Chrome when it happened in case it can help track the issue.

 

 

I've attached my log.

2015-12-04T12-46-55.zip

Edited December 4, 2015 by terabyte

my mouse after a while seems to stop either responding like the side buttons or it decides to move choppy and i cant click or get any response from the side buttons in game.

 

The only way to fix it is to unplug it and connect it to make it work. Its only seems to happen in game I mostly play guild wars 2.

 

I have got Windows 10 64bit and the latest cue software.

 

mouse firmware 1.06

bootloader 0.02

 

Using rainbow linked colours with my strafe.

 

I have attached copy of log file below, there seems to be quite a few errors showing up even when I boot my machine is that meant to be like that?

 

[2015-12-04T16:28:51]: UserSessionInfo: locked changed to 0.

[2015-12-04T16:28:51]: UserSessionInfo: connected changed to 1.

[2015-12-04T16:28:51]: UserSessionInfo: local changed to 1.

[2015-12-04T16:28:52]: UserSessionInfo: locked changed to 0.

[2015-12-04T16:28:52]: UserSessionInfo: connected changed to 1.

[2015-12-04T16:28:52]: UserSessionInfo: local changed to 1.

[2015-12-04T16:28:52]: Device profile (meta) for device vid=46d pid=c07d not found.

[2015-12-04T16:28:52]: Failed to open device: vid=1b1c pid=1b1e path=\\?\hid#vid_1b1c&pid_1b1e&mi_01&col01#7&273befa&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}

[2015-12-04T16:28:52]: Created new device object: Scimitar; ready: 0

[2015-12-04T16:28:52]: Device profile (meta) for device vid=46d pid=c07d not found.

[2015-12-04T16:28:52]: Created new device object: STRAFE RGB; ready: 0

[2015-12-04T16:28:52]: Attached to device object Scimitar: b=1 a=1

[2015-12-04T16:28:52]: Device profile (meta) for device vid=46d pid=c232 not found.

[2015-12-04T16:28:52]: Device profile (meta) for device vid=46d pid=c231 not found.

[2015-12-04T16:28:52]: Failed to open device: vid=1b1c pid=1b1e path=\\?\hid#vid_1b1c&pid_1b1e&mi_00#7&264afcbc&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}

[2015-12-04T16:28:52]: Device profile (meta) for device vid=46d pid=c07d not found.

[2015-12-04T16:28:52]: Attached to device object Scimitar: b=1 a=0

[2015-12-04T16:28:52]: Device profile (meta) for device vid=46d pid=c07d not found.

[2015-12-04T16:28:52]: Initializing Scimitar...

[2015-12-04T16:28:52]: Failed to open device: vid=1b1c pid=1b20 path=\\?\hid#vid_1b1c&pid_1b20&mi_00#7&c3a2ede&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}

[2015-12-04T16:28:52]: Device profile (meta) for device vid=46d pid=c07d not found.

[2015-12-04T16:28:52]: Failed to open device: vid=1b1c pid=1b20 path=\\?\hid#vid_1b1c&pid_1b20&mi_01&col01#7&30116ca0&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}

[2015-12-04T16:28:52]: Device profile (meta) for device vid=1b1c pid=1c07 not found.

[2015-12-04T16:28:52]: Attached to device object STRAFE RGB: b=1 a=1

[2015-12-04T16:28:52]: Attached to device object STRAFE RGB: b=1 a=0

[2015-12-04T16:28:52]: Initializing STRAFE RGB...

[2015-12-04T16:28:52]: Device profile (meta) for device vid=46d pid=c07d not found.

[2015-12-04T16:28:52]: Initialized (st=1) STRAFE RGB.

[2015-12-04T16:28:52]: Device insertion processing complete for STRAFE RGB.

[2015-12-04T16:28:55]: Initialized (st=1) Scimitar.

[2015-12-04T16:28:56]: Device insertion processing complete for Scimitar.

[2015-12-04T17:34:17]: Mouse LED colors change failed. request timed out for Scimitar

[2015-12-04T22:40:36]: Mouse LED colors change failed.Device : Scimitar,Execution result = 1, result = 0, platform error code = 1167.

[2015-12-04T22:40:36]: Mouse LED colors change failed.Device : Scimitar,Execution result = 1, result = 0, platform error code = 1167.

[2015-12-04T22:40:36]: Mouse LED colors change failed.Device : Scimitar,Execution result = 1, result = 0, platform error code = 1167.

[2015-12-04T22:40:36]: Fail counter for Scimitar reached zero, setting status 2.

[2015-12-04T22:40:36]: Mouse LED colors change failed.Device : Scimitar,Execution result = 1, result = 0, platform error code = 1167.

[2015-12-04T22:40:37]: Device vid=1b1c pid=1b1e is marked 'slow startup'.

[2015-12-04T22:40:37]: Device vid=1b1c pid=1b1e is marked 'slow startup'.

[2015-12-04T22:40:37]: Device vid=1b1c pid=1b1e is marked 'slow startup'.

[2015-12-04T22:40:37]: Device vid=1b1c pid=1b1e is marked 'slow startup'.

[2015-12-04T22:40:37]: Device vid=1b1c pid=1b1e is marked 'slow startup'.

[2015-12-04T22:40:43]: Created new device object: Scimitar; ready: 0

[2015-12-04T22:40:43]: Attached to device object Scimitar: b=1 a=1

[2015-12-04T22:40:43]: Attached to device object Scimitar: b=1 a=0

[2015-12-04T22:40:43]: Initializing Scimitar...

[2015-12-04T22:40:43]: Failed to open device: vid=1b1c pid=1b1e path=\\?\hid#vid_1b1c&pid_1b1e&mi_00#7&264afcbc&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}

[2015-12-04T22:40:43]: Failed to open device: vid=1b1c pid=1b1e path=\\?\hid#vid_1b1c&pid_1b1e&mi_01&col01#7&273befa&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}

[2015-12-04T22:40:45]: Initialized (st=1) Scimitar.

[2015-12-04T22:40:46]: Device insertion processing complete for Scimitar.

Are any of the other people having trouble using the Alienware AlienFX software with their Scimitars? I've been doing some extensive troubleshooting with multiple Scimitars (I received a replacement through Amazon) and it's starting to look like my problem was a compatibility issue between the STRAFE RGB and/or Scimitar lighting schemes and the Alienware software I had installed on my computer that had the "Enable Third Party AlienFX Access" option selected.

 

I've disabled the third party access and haven't had trouble using the Scimitar CUE linked to my STRAFE RGB in over two days. (Before this I had to unplug and re-insert my Scimitar between three and four times a day.)

Some additional information from my end:

 

I'm on Ubuntu 14.04 and am using ckb to manage my lighting and keymap preferences for my Scimitar, running firmware 1.06.

 

When I have ckb running a simple "fade" animation between two colors on the front light / wheel light / logo light, the mouse demonstrates the symptoms described in this thread after some time (between a few hours and a handful of days) - stuttering cursor and non-working mouse buttons. Additionally, after the mouse has been unplugged and replugged, it takes a while for the mouse to reinitialize, and ckb-daemon must be restarted for the mouse to resume side-button functionality.

 

When the mouse enters the non-working state, the logo also turns an anomalous color that changes from incident to incident but is usually some shade of pink or lilac.

 

After disabling the animation, I can operate the mouse with ckb running for multiple weeks of uptime without incident.

 

Possibly there is a rare FW issue with color-change commands that only manifests with low frequency.