Jump to content

sausje

Members
  • Posts

    13
  • Joined

Reputation

10 Good
  1. Yep same here. Cannot play the Halo MCC Insider build this weekend because of it.. One big ****-up this release.. And that for a company that makes MILLIONS.. You should be ashamed.
  2. I'm sorry for digging up this old topic, but after searching for this issue, this was the only one I could find. Same thing started happening to me as of today. I usually have a solid blue light setup when during gaming, one of my fans started showing red. After swapping colors and testing, I couldn't find the issue. Reboot, reflashing of firmware, etc, nothing seemed to fix the color from being shown incorrect. Then I saw on a secondary fan, that 1 LED of it was slightly flickering. So I started thinking that it might be the cause. And behold, after testing, I found out that 1 LED from another fan, completely messed up the other fan in the loop that came after it. As shown and described here: [ame] [/ame] So I guess my only option is to take out that fan, send it back and get a replacement?
  3. Go to the correct lightning channel in the app and go to the "hardware lighting" tab and change it there to what you want. By default it's indeed rainbow, but you can (finally, since it's recent) change it.
  4. I'm back with the same issue, on 6.02 It was fixed for months and now suddenly after updating, the same issue is back, even with the exact same settings. However, my standpoint has changed. HWINFO64 is a FREE program and iCUE comes with something I paid (in total) hundreds of euro's for. So I expect you guys to provide a fix for this and make sure it's not happening anymore. As someone that paid for your product a hefty price (vs other brands), I'm now making a demand to fix this issue. I NEED HWINFO64 for certain readings, unless you can provide the exact same functionality within iCUE, I will need to use it and you'll have to find a way to make both programs work nicely with each other. Edit: it wasn't the same settings, it turned out it did reset and I completely forgot the "CorsairLink and Asetek Support" setting in the "safety" tab. Still, I stand by my point. It's Corsair their task to make both work nicely, as Corsair is a paid product, whereas the other is free.
  5. Maybe an idea for the software to notify you when it detects such a driver? So people don't have to guess what's causing it? Although, people that google the issue should fall on this topic now.
  6. After updating HWinfo (and turning off persistent driver and a reboot) the issue is suddenly gone. I cannot reproduce it anymore. At least, I could try reverting all settings but honestly, it's working now and I don't really want to mess around with it. But I presume it was the persistent driver option, as that's the only change that happened today (and a version update of hwinfo).
  7. Yeah I saw that when googling the issue, that's when I disabled it. Running version 5.90-3550. Persistent driver turned off (meaning the driver shouldn't be installed when the program isn't running), and ofc the "CorsairLink and Asetek Support" turned off. What logs would you need, if it contains any sensitive info, I would rather not post it online for everyone to see though.
  8. Yes, I've got HWinfo sensors running, though I have disabled the option "CorsairLink and Asetek Support". Because I presumed that it might be the issue. I've also got RTSS, although I couldn't find anything that could be interfering. I also think CAM software does some monitoring (needed for my NZXT Kraken, don't like the huge Corsair branding on yours sorry!), and so does my AI Suite 3 from my ASUS mb software. But I've tried turning them all off and it would still happen. The odd thing that I've noticed is that when booting the PC, windows gives a notification sound that a device is connected. Then shortly after a device disconnect sound and suddenly you see the fan colors go the correct color.
  9. Hello everyone, So I recently got myself the 500D RGB SE case. With that, I got myself 2 more 140LL and 3 more 120LL fans. Now it all works fine and ok-ish, until I try and do stuff related to fan speeds. Somehow my commander just keeps disappearing in iCUE, though only the fan speed part. I've checked all cables a couple of times and this didn't happen when I finish building it about 1.5 weeks ago. It just randomly started happening. Here's a short video displaying the issue: [ame] [/ame] On the latest software with the latest firmware. Attached is a "pro" drawing of how it's all setup inside my case. Thanks in advance!
×
×
  • Create New...