Corsair Employee Corsair Henry Posted February 8, 2016 Corsair Employee Share Posted February 8, 2016 Updated Release Version 1.15.36 February 8th, 2016 Release Notes CUE 1.15.36 is the latest release for our RGB line of peripherals and contains a multitude of changes and enhancements. Fixes Resolved a critical connection issue with Scimitar when lighting is enabled (this fix also requires FW 2.01 for Scimitar).Resolved a rare issue that causes CUE to crash when modifying a selected key under advanced settings.VOID Wireless will no longer automatically turn on sidetone if it has been disabled in CUE.Resolved an issue with DPI LED colors with duplicate files.Resolved a critical connection issue with Scimitar when lighting is enabled. (This fix also requires FW 2.01 for Scimitar).VOID USB and Wireless RGB Headsets now support Active Voice Notifications! To enable this new feature, connect your headset and select the Settings Tab -> Devices Tab:Resolved other minor bugs and issues. Important Note: Please ensure your Scimitar device is updated to FW 2.01 with 1.15.36. Once your Scimitar device is updated, it will no longer be compatible with previous versions of CUE. During a firmware or software update for any Corsair peripheral, CUE may need additional components and time from a Window’s Driver Software Installation to complete the process. If you have to abort at any part of the process, simply reconnect the device and select Update Firmware from the Devices -> Settings Menu, and choose “Force Update from Server” to re-initiate the update. Keyboard Connectivity: Connecting via USB 3.0: Use one connector (the one with the keyboard icon) when connecting via USB 3.0Connecting via USB 2.0: Use both connectors when using USB 2.0. Important Note: Plug in the connector with the two arrows icon first, and the connector with the keyboard icon second.CUE Patch Notes 1.15.36.pdf Link to comment Share on other sites More sharing options...
GTK48 Posted February 9, 2016 Share Posted February 9, 2016 This just does not work on my device Link to comment Share on other sites More sharing options...
Dohregard Posted February 9, 2016 Share Posted February 9, 2016 Just tried to update, said it did not work and to try to force it from server... but the mouse isn't in CUE anymore... Link to comment Share on other sites More sharing options...
GTK48 Posted February 9, 2016 Share Posted February 9, 2016 there is something wrong with this update period. Link to comment Share on other sites More sharing options...
Inheritance Posted February 9, 2016 Share Posted February 9, 2016 Just tried to update, said it did not work and to try to force it from server... but the mouse isn't in CUE anymore... Are you running 1.15.36 Link to comment Share on other sites More sharing options...
jebuchanan Posted February 9, 2016 Share Posted February 9, 2016 Mine updated NP. :) Link to comment Share on other sites More sharing options...
Opi_safag Posted February 9, 2016 Share Posted February 9, 2016 Has the tray icon gone missing for anyone else after the update? CUE is running on my PC, but there's no tray icon anymore.. Link to comment Share on other sites More sharing options...
Inheritance Posted February 9, 2016 Share Posted February 9, 2016 Has the tray icon gone missing for anyone else after the update? CUE is running on my PC, but there's no tray icon anymore.. try restarting your computer it should come back. Link to comment Share on other sites More sharing options...
Rohaus Posted February 9, 2016 Share Posted February 9, 2016 I saw this update pop up yesterday... the first part was the CUE telling me that there was a new firmware... so I updated the firmware to the latest. Then, the software was telling me that it was not working... after some research, I realized that this was because of the firmware and that I needed to be running the latest CUE software. So, I updated that and had no issues with updating. Unfortunately, this is when the issue of lift distance came back to haunt me. No matter what setting I choose, low, medium, or high... it does not matter. Each setting behaves as High setting. I tried to go back to the previous version of software but this is when I realized that I could not go back to previous versions of the CUE software due to running the latest firmware. I have combed through these here forums, the CUE section and the mouse and keyboard section and found very little information specific to my issue of the lift distance. The way I use my mice... and any mouse before the Scimitar... is I like a low DPI, typically 800, and as such I do a lot of picking up of the mouse for positioning... I have done this for years and it is so ingrained in me, I can't play any other way. Anyways, it used to be that I had to have the mouse very close to the surface in order for it to track. This is my preferred way of using any mouse. Now, with the latest CUE update and subsequent firmware update, I am experiencing extreme traction meaning that I can have the mouse pretty high up in the air and it still tracks... this is very bad for me as it causes for inaccurate control over my aim... I tried to get used to it last night... but with the extreme traction, I wound up nauseated... it's like watching a shaky cam video... I spent a couple hours last night trying to resolve this issue by scouring the internet for a firmware download... trying to find an older version of firmware is impossible!!! Even if I could find an older firmware version, I would need to use the latest CUE software to update to the older version and I have a hunch that it wouldn't let me... *sigh* I love this mouse... I had ZERO issues with it prior to doing this update... well, sometimes the RGB lights would go out... but I never lost control of the mouse and my buttons... so I didn't care... Please tell me there is a way to revert back to a previous firmware? Or, better yet, please tell me how to fix the lift distance issue? Again, as it stands right now, no matter what setting I chose, Low, Medium, or High... it does not matter... they are all the same... basically acts as if all the settings are High... Are there people that actually prefer playing with a high lift distance??? Anyways... please help! Link to comment Share on other sites More sharing options...
Inheritance Posted February 9, 2016 Share Posted February 9, 2016 Rohaus to get the old firmware files youll need to contact Corsair Support and see if anyone over there can release the files to you. Link to comment Share on other sites More sharing options...
Inheritance Posted February 10, 2016 Share Posted February 10, 2016 USERS ON Z68 and X58 platforms. If you have a scimitar please hold off on updating to the 2.01 firmware. Link to comment Share on other sites More sharing options...
blademansw Posted February 10, 2016 Share Posted February 10, 2016 I am hoping this update fixes the mouse freezes that I keep getting since obtaining the scimitar a couple of weeks ago. Kill CUE off and everything starts working again. I will report back once I have applied the update! Link to comment Share on other sites More sharing options...
morno Posted February 11, 2016 Share Posted February 11, 2016 still dont fix my installing driver (1/2) freezes. posted a directX thing i have tried to install it with disable all sound things in my system and disabled razer synapse and unplugging my internet and unplugging all usb connectors. im at a loss here. [2016-02-11T19:06:32]: MacroCommand/Win: Cannot open driver device. [2016-02-11T19:06:33]: UserSessionInfo: locked changed to 0. [2016-02-11T19:06:33]: UserSessionInfo: connected changed to 1. [2016-02-11T19:06:33]: UserSessionInfo: local changed to 1. [2016-02-11T19:06:36]: Invalid XML. [2016-02-11T19:06:37]: UserSessionInfo: locked changed to 0. [2016-02-11T19:06:37]: UserSessionInfo: connected changed to 1. [2016-02-11T19:06:37]: UserSessionInfo: local changed to 1. [2016-02-11T19:06:37]: Device profile (meta) for device vid=24c6 pid=5303 not found. [2016-02-11T19:06:37]: Device profile (meta) for device vid=1532 pid=40 not found. [2016-02-11T19:06:37]: Device profile (meta) for device vid=93a pid=2510 not found. [2016-02-11T19:06:37]: Created new device object: STRAFE RGB; ready: 0 [2016-02-11T19:06:37]: Attached to device object STRAFE RGB: b=1 a=1 [2016-02-11T19:06:37]: Device profile (meta) for device vid=1532 pid=40 not found. [2016-02-11T19:06:37]: Device profile (meta) for device vid=1532 pid=40 not found. [2016-02-11T19:06:37]: Device profile (meta) for device vid=1532 pid=40 not found. [2016-02-11T19:06:37]: Attached to device object STRAFE RGB: b=1 a=0 [2016-02-11T19:06:37]: Device profile (meta) for device vid=1532 pid=40 not found. [2016-02-11T19:06:37]: Initializing STRAFE RGB... [2016-02-11T19:06:37]: Device profile (meta) for device vid=1532 pid=40 not found. [2016-02-11T19:06:37]: Device profile (meta) for device vid=1532 pid=40 not found. [2016-02-11T19:06:37]: Failed to open device: vid=1b1c pid=1b20 path=\\?\hid#vid_1b1c&pid_1b20&mi_00#8&2065429b&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030} [2016-02-11T19:06:37]: Failed to open device: vid=1b1c pid=1b20 path=\\?\hid#vid_1b1c&pid_1b20&mi_01&col01#8&d35265d&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030} [2016-02-11T19:06:37]: Initialized (st=1) STRAFE RGB. [2016-02-11T19:06:37]: Device insertion processing complete for STRAFE RGB.DxDiag.txt Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.