Jump to content
Corsair Community

Scimitar Buttons Unresponsive


zawk
 Share

Recommended Posts

My Scimitar's buttons randomly decide to stop working sometimes. Ever since the latest firmware update, it has been working until today. I turned on my computer and the buttons don't register presses at all. I have already assigned them different values and have restarted my computer several times. I have also reinstalled both, CUE and the firmware several times. Please don't make me regret this mouse purchase more than the Naga.
Link to comment
Share on other sites

Hi

Bought the device today and in The Division the side key's with keystrokes assigned often dosent respond wich is a huge dissapointment. have tested the mice for almost an hour with all ussuall test.... usb ports, reboot, reinstall etc

 

It works fine in documents and chat windows but lag in the game The Division

 

Have compared with keyboard vs mouse and its only the mouse that behave unpredictable..

Link to comment
Share on other sites

  • Corsair Employees

We've seen this issue come up and we can't seem to replicate as to why this occurs. For Scimitar, the side buttons rely on CUE (and the virtual driver it uses for Actions like macros and remaps). If the side buttons aren't working, the only reason I can assume is the driver isn't working.

 

If anyone has this issue constantly happening, the more information you can provide the better. Id like to know the following:

 

1.) OS (and whether you have all of the latest updates)

2.) Is the Corsair Virtual Input Driver working properly under Device Manager?

3.) Are you on latest FW and SW versions?

 

Until we can replicate it fully, it'll be hard to diagnose and. resolve the issue so any additional information will help.

Edited by Corsair James
Link to comment
Share on other sites

I'm in the same boat. (Is that a pun on these forums?)

 

I've been using the mouse and the CUE happily for about two weeks, but now the side buttons have stopped working. I can reassign the buttons function, and I know the CUE is recording the changes, as when I assign a normal function (like mouse wheel click) from the usual "middle click" which in Chrome would open a link in a new tab, to something else like "enter" it no longer opens the link in a new tab, until I go back to a mode that has the standard settings.

 

1) OS is Windows 10 (Recently changed and MAY have been the same time I saw the mouse buttons stop working, not sure)

2) Unfamiliar with where the device manager is in Windows 10, but the mouse main functions (left click, right click, middle click, and scroll wheel) are working.

3) Both FW and SW are the latest versions.

Link to comment
Share on other sites

Been trying all the fixes.. repair cue.. remove driver / reinstall.. different ports.. only worked once after i bought the mice.. never again...

 

 

Windows 10, fully updated.

 

Latest drivers for my system (did it beacuse of issues with scimitar)

 

FW 2.03 BL 0.02 CUE 1.16.42

 

Corsair composite virtual device thingy in DM says its "This device is working properly."

 

Semes there are many with these issues! Please help us.

Link to comment
Share on other sites

I'm in the same boat. 100$ mouse and such a fail.

 

Win 10 fully updated.

 

I've found an temporary solution:

 

1. Uninstall CUE from controll panel(without deleting your settings)

2. Reboot

3. Install CUE.

 

But after next reboot buttons stops working again and i forced to uninstall/reboot/install.

 

And by the way, nice support from Corsair lol.

Edited by Keetsune
Link to comment
Share on other sites

And by the way, nice support from Corsair lol.

 

The forum is not tech support. And they cant fix it if you dont provide any info other then its not working.

 

Have yall checked for bios, chipset updates. Have you tried a different USB port. Have you tried doing a clean install of windows.

Edited by Inheritance
Link to comment
Share on other sites

Hi guys.

 

I've been using my Scimitar without any problem for over 1 month. However for 2 days I'm having middle click problem. When i click, It's not responding. I have to click like 20 times for that. I'm using win 10 pro. And all updates are done on software.

Link to comment
Share on other sites

Hi guys.

 

I've been using my Scimitar without any problem for over 1 month. However for 2 days I'm having middle click problem. When i click, It's not responding. I have to click like 20 times for that. I'm using win 10 pro. And all updates are done on software.

Have you done any Windows 10 updates lately?

 

Try running again the CUE installer and choose the repair option, then restart. Does it help?

Link to comment
Share on other sites

Same issue with me . just got the mouse today and have tried all the posted fixes in the many forums on this.

 

using windows 10 64 bit and my CUE software version is 1.16.42 and my firmware version is 2.03

please help with fixes other than those posted

 

 

log wont attach so here it is

 

[2016-04-13T19:59:06]: UserSessionInfo: locked changed to 0.

[2016-04-13T19:59:06]: UserSessionInfo: connected changed to 1.

[2016-04-13T19:59:06]: UserSessionInfo: local changed to 1.

[2016-04-13T19:59:07]: UserSessionInfo: locked changed to 0.

[2016-04-13T19:59:07]: UserSessionInfo: connected changed to 1.

[2016-04-13T19:59:07]: UserSessionInfo: local changed to 1.

[2016-04-13T19:59:08]: UserSessionInfo: locked changed to 0.

[2016-04-13T19:59:08]: UserSessionInfo: connected changed to 1.

[2016-04-13T19:59:08]: UserSessionInfo: local changed to 1.

[2016-04-13T19:59:08]: Device profile (meta) for device vid=1532 pid=111 not found.

[2016-04-13T19:59:08]: Failed to open device: vid=1b1c pid=1b1e path=\\?\hid#vid_1b1c&pid_1b1e&mi_01&col01#7&2b8b3b8a&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}

[2016-04-13T19:59:08]: Created new device object: Scimitar; ready: 0

[2016-04-13T19:59:08]: Device profile (meta) for device vid=1532 pid=10f not found.

[2016-04-13T19:59:08]: Attached to device object Scimitar: b=1 a=1

[2016-04-13T19:59:08]: Attached to device object Scimitar: b=1 a=1

[2016-04-13T19:59:08]: Device profile (meta) for device vid=46d pid=c232 not found.

[2016-04-13T19:59:08]: Device profile (meta) for device vid=46d pid=c231 not found.

[2016-04-13T19:59:08]: Attached to device object Scimitar: b=1 a=0

[2016-04-13T19:59:08]: Initializing Scimitar...

[2016-04-13T19:59:08]: Failed to open device: vid=1b1c pid=1b1e path=\\?\hid#vid_1b1c&pid_1b1e&mi_00#7&7b3fdc8&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}

[2016-04-13T19:59:08]: Scimitar : trying to force P00 instead of P04

[2016-04-13T19:59:08]: Device profile (meta) for device vid=46d pid=a1f not found.

[2016-04-13T19:59:08]: Device profile (meta) for device vid=1532 pid=10f not found.

[2016-04-13T19:59:08]: Device profile (meta) for device vid=1532 pid=10f not found.

[2016-04-13T19:59:08]: Device profile (meta) for device vid=46d pid=a1f not found.

[2016-04-13T19:59:08]: Device profile (meta) for device vid=1532 pid=10f not found.

[2016-04-13T19:59:08]: Device profile (meta) for device vid=1532 pid=111 not found.

[2016-04-13T19:59:08]: Scimitar : success, continue initialization on P00

[2016-04-13T19:59:10]: Initialized (st=1) Scimitar.

[2016-04-13T19:59:12]: Device insertion processing complete for Scimitar.

[2016-04-13T20:01:34]: UserSessionInfo: locked changed to 0.

[2016-04-13T20:01:34]: UserSessionInfo: connected changed to 1.

[2016-04-13T20:01:34]: UserSessionInfo: local changed to 1.

[2016-04-13T20:02:04]: UserSessionInfo: locked changed to 0.

[2016-04-13T20:02:04]: UserSessionInfo: connected changed to 1.

[2016-04-13T20:02:04]: UserSessionInfo: local changed to 1.

[2016-04-13T20:02:16]: UserSessionInfo: locked changed to 0.

[2016-04-13T20:02:16]: UserSessionInfo: connected changed to 1.

[2016-04-13T20:02:16]: UserSessionInfo: local changed to 1.

[2016-04-13T20:02:57]: UserSessionInfo: locked changed to 0.

[2016-04-13T20:02:57]: UserSessionInfo: connected changed to 1.

[2016-04-13T20:02:57]: UserSessionInfo: local changed to 1.

[2016-04-13T20:03:09]: UserSessionInfo: locked changed to 0.

[2016-04-13T20:03:09]: UserSessionInfo: connected changed to 1.

[2016-04-13T20:03:09]: UserSessionInfo: local changed to 1.

[2016-04-13T20:03:20]: UserSessionInfo: locked changed to 0.

[2016-04-13T20:03:20]: UserSessionInfo: connected changed to 1.

[2016-04-13T20:03:20]: UserSessionInfo: local changed to 1.

[2016-04-13T20:03:42]: UserSessionInfo: locked changed to 0.

[2016-04-13T20:03:42]: UserSessionInfo: connected changed to 1.

[2016-04-13T20:03:42]: UserSessionInfo: local changed to 1.

[2016-04-13T20:03:58]: UserSessionInfo: locked changed to 0.

[2016-04-13T20:03:58]: UserSessionInfo: connected changed to 1.

[2016-04-13T20:03:58]: UserSessionInfo: local changed to 1.

[2016-04-13T20:04:12]: UserSessionInfo: locked changed to 0.

[2016-04-13T20:04:12]: UserSessionInfo: connected changed to 1.

[2016-04-13T20:04:12]: UserSessionInfo: local changed to 1.

[2016-04-13T20:07:12]: SdkController. Requesting working state leave because of transition to Suspended or Shutdown state.

[2016-04-13T20:07:12]: Requesting working state leave because of transition to Suspended or Shutdown state.

[2016-04-13T20:07:12]: Leaving working state.

Link to comment
Share on other sites

Hi guys again.

 

Okay last time I've fixed the problem but I have the same problem now.The thing is, It's completely random. Yesterday I didn't have any problem until night. At night my middle click completely stop working. And today 30 mins ago I didn't have any problem again. But now middle click is completely dead. I don't know what's going on with this mouse ;D

 

Edit: Here we go. It's working again and I haven't done anything to fix it. I don't understand this :D It's probably the best MMO mouse I've ever used but this problem is really annoying...

Edited by badumtss
Link to comment
Share on other sites

  • 2 weeks later...

I found the reason why my side buttons is unresponsive after each reboot:

when damn Viber is in autostart it prevent Corsair Composite Virtual Input Deivces driver to load, after i shutdown Viber i can hear how new device is found and side buttons is start to work lol, then i can launch Viber and everything work fine at that point.

Maybe there is also other programms that can prevent driver to load and that's why ppls have this issue.

Link to comment
Share on other sites

I found the reason why my side buttons is unresponsive after each reboot:

when damn Viber is in autostart it prevent Corsair Composite Virtual Input Deivces driver to load, after i shutdown Viber i can hear how new device is found and side buttons is start to work lol, then i can launch Viber and everything work fine at that point.

Maybe there is also other programms that can prevent driver to load and that's why ppls have this issue.

 

Goddamn it. I also have viber autostarting and had the side buttons issue, but now I have already sent it back and can't try if disabling viber fixes it. But even before you found out about the viber thing, the mouse was recognised from CUE and left, right, middle clicks worked, right?

Link to comment
Share on other sites

  • 2 weeks later...
 Share

×
×
  • Create New...