![]() |
#1
|
|||
|
|||
![]()
Hi all,
Here is the trick, RANDOMLY mi keyboard disconnect from the CUE 2. There is no warning no error message so clearly I can't say why this is occuring... If I unplug the kerboard and replug him its ok the device is recognised in cue2. But if i continue to use the keyboard randomly the CUE2 lost him... Moreover there is another bug : the caps led doesn't work. I've saw some threads about that talking that it was when they use steam or the 360 pad controller. ITS NOT MY CASE... I don't use steam and the CAPS led sometime is here sometimes not... CORSAIR : It's getting more and more problematic to have to suffer your lack of implication for resolving our problems. As far as I've seen the caps problem it's now MORE THAN 2 MONTH that the joke goes on... So please stop spitting on the pattrons and start working. Would I recommend corsair products : nope as far as my problem isn't fixed... Sorry 'bout my english i'm not fluent ! |
#2
|
||||
|
||||
![]()
As far as I know the K55 RGB doesn't support CUE. It shouldn't even be able to detect it since there is no chip in it that allows CUE to find it.
Or are you talking about a different keyboard? |
#3
|
|||
|
|||
![]()
CUE does support the K55 RGB after a firmware update.
You'll want to make sure your USB chipset drivers are up to date. Have you tried disabling an USB power saving features in Windows/BIOS? (If available) |
#4
|
|||
|
|||
![]()
@ terabyte : it does since 2.12 CUE2 firmware version
@ Toasted : al my drivers up to date, bios is lagacy usb... And I've shut down USB low consumption policy... But still the same issue... Thats a real shame... |
#5
|
||||
|
||||
![]()
Oh, I wasn't aware about the FW update. Good to know.
I guess Corsair should update the K55 RGB product page to say it supports CUE then ![]() |
![]() |
Thread Tools | Search this Thread |
Display Modes | Rate This Thread |
|
|