![]() ![]() This includes referral links, including Amazon! Product links are fine affiliate or referral links that benefit you are not. Rule 3 - No buying/selling/trading in this subreddit. 2.3 - Off-topic posts or comments concerning religion, politics, or drama.2.2 - Low effort content such as obvious reposts, or photos of unrelated products not relevant to CORSAIR or PC Gaming. ![]() Any comment that is overly negative, and provides nothing useful in terms of discussion or critique, is considered "bashing". 2.1 - Posts or comments that are considered "Bashing" of users, or the hardware or software they use.Rule 2 - The following will be removed at moderator discretion: Remember, you can always submit a ticket through our online portal. Any other customer support posts will be removed. Rule 1 - Tech/customer support questions are only allowed in.With this, it's not about as much as the amount of devices used but instead the bandwidth these devices require.Īnd with that, you can use USB 3.0 -> USB 2.0 cable, getting internal USB 2.0 header out of internal USB 3. And from other people's experience, i've seen it to be MoBo issue. With your personal experience, you've had it with USB hub. With my personal experience, i've had it with iCUE. That is difficult to troubleshoot since it could be iCUE issue, hardware issue (USB hub) or MoBo issue (where MoBo can't keep both connected at all times). But there are plenty of PCI-E -> internal USB 3.0 cards,Īnd with that, you can use USB 3.0 -> USB 2.0 cable, getting internal USB 2.0 header out of internal USB 3.0 header, Looked around a bit and couldn't find PCI-E -> internal USB 2.0 card. With this, you can have dedicated internal USB 2.0 headers for all of your devices. Though, what you could do, is buying PCI-E -> internal USB 2.0 card. However, if you were to split the internal USB 2.0 header, to add another device, the load, which used to be 100% by Commander Pro alone, is now expanded to 150% (if given that your AIO requires only half the bandwidth of one internal USB 2.0 header). If it would be connected alone to the MoBo, it would work just fine. Razer products are the worst when it comes to the RGB control and NZXT CAM also has some issues, albeit the least of the bunch (i also have NZXT CAM).Ĭlick to expand.With this, it's not about as much as the amount of devices used but instead the bandwidth these devices require.įor example: Commander Pro has loads of features with it and it would be logical to assume that it requires the full bandwidth of one USB 2.0 header. Asus Aura is also plagued with all kinds of issues. So, i had to roll back to the older version and with older version iCUE detects my mouse without issues again.įor info, it's not only Corsair who has issues with their RGB software. When i updated to the latest one, iCUE, flat-out, did not detect my Corsair SABRE RGB mouse, no matter what i did or try. Though, you could contact Corsair Support about it as well but i doubt that they can help you much.ītw, i'm currently running iCUE 3.37.140, despite the latest being 4.11.274. Oh, you could try using other USB slots as well, e.g the ones at the MoBo back I/O. You can roll back iCUE version one or two times but other than that, there's not much you can do. And only thing that has changed during that time, is the iCUE versions.Īs far as solving it goes, well, it doesn't look good. Only in the last year or two, the disconnect issue has come apparent. Also, sometimes, at boot up, my mouse isn't registered and i have to physically re-connect the USB.Ībout 5 years back, when i bought my Corsair peripherals, i didn't have any issue with them. Now, on Win10, headset automatically connects again but it is still annoying. When i was running Win7, only fix, to get it back to connected, was full reboot. I too have full set of Corsair peripherals (KB, mouse, mouse pad, headset, headset stand all RGB) and out of them all, my headset is #1 device that disconnects most often. It's the iCUE issue, rather than hardware issue. ![]()
0 Comments
Leave a Reply. |