Hi guys. My strafe rgb every now and then doesn't show up in the cue 2.0 software. When this happens the light effects don't run and I get a red ! show in the task bar. I have to un plug and plug back in for it to sort itself out. I'm running the latest cue and firmware. Any ideas?
Corsair RBG Owners Club
- Thread starter Kipz
- Start date
You can get any WASD key cap set that follows Cherry MX keycap compatibility, it will fit.
Associate
Owner of the M65 RGB mouse and in my personal opinion find it to be the best gaming mouse.
Soldato
So over the last month or so I've joined the RGB club with the VOID SE RGB wireless, M65 PRO RGB and the K70 LUX RGB.
The VOID is great, it's my first wireless headset and not having wires is pretty liberating. The battery life is decent and the earcups are very comfy, I also don't get the pain on the top of my head after using it for prolonged periods (unlike my old pair). The RGB side of it is pretty gimmicky; I have it turned off to save battery.
The mouse is similar to my old M40, but obviously higher quality. The FPS button on the side is proving to be quite handy, and the 5 levels of DPI work well. Again, the RGB side of it is a little pointless as 90% of the time your hand is over it, but it's a nice feature.
The K70 LUX is my first mech keyboard, and it's bloody lovely to use. I've come from a K30 and the difference in quality is immense, it just feels so solid and well put together. Obviously the main selling point are the actual keys, and my Reds feel so nice to type on, and when gaming.
The only gripe I have with it is that right now the advanced lighting and detection in CUE is working very erratically. I got it on Friday and after a bit fiddling about and manually re-downloading CUE (as the built in updater doesn't work), it was working, but when it felt like it. Downloaded the latest firmware v2.05. When set to position 1 on the back CUE says 'malfunction' and all I get is standard static lighting. Setting it to 2 seems to sort it, and I downloaded a couple of profiles which work well. Saturday it works fine, but Sunday it borks again - all switch positions. Tried to force firmware update but it gets stuck at 3%. No dice, so I raised a support ticket with Corsair. Monday and yesterday it's fine in position 2.
It's a great bit of kit but i'm not the first person who has had issues with Corsair keyboards playing silly buggers, and it seems it's because of CUE.
The VOID is great, it's my first wireless headset and not having wires is pretty liberating. The battery life is decent and the earcups are very comfy, I also don't get the pain on the top of my head after using it for prolonged periods (unlike my old pair). The RGB side of it is pretty gimmicky; I have it turned off to save battery.
The mouse is similar to my old M40, but obviously higher quality. The FPS button on the side is proving to be quite handy, and the 5 levels of DPI work well. Again, the RGB side of it is a little pointless as 90% of the time your hand is over it, but it's a nice feature.
The K70 LUX is my first mech keyboard, and it's bloody lovely to use. I've come from a K30 and the difference in quality is immense, it just feels so solid and well put together. Obviously the main selling point are the actual keys, and my Reds feel so nice to type on, and when gaming.
The only gripe I have with it is that right now the advanced lighting and detection in CUE is working very erratically. I got it on Friday and after a bit fiddling about and manually re-downloading CUE (as the built in updater doesn't work), it was working, but when it felt like it. Downloaded the latest firmware v2.05. When set to position 1 on the back CUE says 'malfunction' and all I get is standard static lighting. Setting it to 2 seems to sort it, and I downloaded a couple of profiles which work well. Saturday it works fine, but Sunday it borks again - all switch positions. Tried to force firmware update but it gets stuck at 3%. No dice, so I raised a support ticket with Corsair. Monday and yesterday it's fine in position 2.
It's a great bit of kit but i'm not the first person who has had issues with Corsair keyboards playing silly buggers, and it seems it's because of CUE.
Associate
This is strange, sorry to hear it. How often do you have to unplug and plug back in your STRAFE before it starts working again? Does it also happen during cold boot?
Hi its always from cold boot. Once I've unplugged it and plugged it back in its fine till the next cold boot but not every boot. Its random, does it every now and then. I've rma'd it but still waiting for you to confirm you've received it even no it says its been delivered yesterday.
Associate
Post your ticket # and I'll look into it myself and find out what the status is
#6898327 Thanks
Soldato
So Brian at Corsair got back to me, and suggested a soft reset for my keyboard. That didn't work, as it was still intermittently working, and then the next day it would say 'malfunction' in CUE. I relayed this info in the ticket and he gave me a step by step solution on clearing the firmware from the KB itself and sent me the latest version (2.05) to upload into it.
I did tried this - so I deleted the firmware file and copied the new one to it, but when i unplugged the KB and put it back in again it's like it's still stuck in recovery mode or something, the 'CRP DISABLD' drive keeps appearing in 'My PC' and neither Windows or CUE will recognise it. I tried this several times but no dice. I got back to Corsair and they have suggested I try it on another PC, so I have taken it into work today and have tried to do what he suggested. When I plug it in the recovery drive appears in Windows, but when I try and delete the current 'firmware' file, it says I do not have permissions 'as Everyone' needs to give my user account access (I have tried with an admin and also PC administrator account). Now I think this is because of our work PC images being locked down so I haven't given up hope, I'll just need to try and plug it into a friends PC to see if it does the same thing.
I am crossing everything that over the weekend I am able to sort this, but if not I'm without a keyboard. Not quite what I'd expect to happen considering I spent the best part of £130, that I have a hunch an older version of CUE (not the one i'm using atm) caused. At least I will be able to get a straight replacement if it's not able to be fixed.
I did tried this - so I deleted the firmware file and copied the new one to it, but when i unplugged the KB and put it back in again it's like it's still stuck in recovery mode or something, the 'CRP DISABLD' drive keeps appearing in 'My PC' and neither Windows or CUE will recognise it. I tried this several times but no dice. I got back to Corsair and they have suggested I try it on another PC, so I have taken it into work today and have tried to do what he suggested. When I plug it in the recovery drive appears in Windows, but when I try and delete the current 'firmware' file, it says I do not have permissions 'as Everyone' needs to give my user account access (I have tried with an admin and also PC administrator account). Now I think this is because of our work PC images being locked down so I haven't given up hope, I'll just need to try and plug it into a friends PC to see if it does the same thing.
I am crossing everything that over the weekend I am able to sort this, but if not I'm without a keyboard. Not quite what I'd expect to happen considering I spent the best part of £130, that I have a hunch an older version of CUE (not the one i'm using atm) caused. At least I will be able to get a straight replacement if it's not able to be fixed.
Associate
#6898327 Thanks
According to our customer service your replacement was already delivered? Have you received it?
Yes it has now been delivered. The RMA status is updated too slow or not updated at all. I received the new keyboard on Friday but I only got the email saying it's been shipped yesterday. It also wasn't updated saying that you had received it either.
Associate
Thanks for the update. Regarding the delayed ticket update, that must have been an issue on the backend of our RMA system. I'll share this info wtih our RMA team so that they are aware. Thanks for bringing this up.
Maybe its a software fault?
Associate
Do you mind posting a screen of the error window? Perhaps try the KB on a different system and see if you get the same behavior. It's worth a shot to see if this issue is system dependent.
Soldato
Looking to finally move on from my trusty Sidewinder X4. Can't decide between the K70 LUX or the Rapidfire model. I'm more of a gamer so assume rapid fire would be the better option?
Soldato
I got my replacement K70 LUX RGB from Amazon, and it's working fine now. I get the odd 'malfunction' red triangle and the RGB lighting stops working, but closing and reopening CUE sorts it. I know it's getting better, but it's far off being a reliable bit of software.
Here you go, the icon in the lower right corner and the keyboard is missing in cue 2.0. It works ok but is lit up in a solid red not the usual colours i have it set to.
Soldato
If you press the cog I think it will show up but you won't be able to change the settings (it'll be greyed out).
When I got my K70 LUX replacement it started doing the same thing as the previous one, but when I switched the polling switch to the '2' position it sorted it, not sure if that's something you have tried? As I mentioned before sometimes the colours will set back to red all over instead of my proper profile - closing and opening CUE sorts it. Have you updated to the latest version of it?
When I got my K70 LUX replacement it started doing the same thing as the previous one, but when I switched the polling switch to the '2' position it sorted it, not sure if that's something you have tried? As I mentioned before sometimes the colours will set back to red all over instead of my proper profile - closing and opening CUE sorts it. Have you updated to the latest version of it?