Jump to content

phdibart

Members
  • Posts

    12
  • Joined

Reputation

10 Good
  1. I updated iCue to ver. 3.37.140 and the DPI settings are now fixed. Thanks!
  2. I have the following Corsair products in iCue. K95 Dark Core (turned off in the screenshot) M65 Pro Vengeance RGB Pro Commander Pro (5 fans and a XC7 attached) Asus mobo integration For some reason, my M65 is only allowing me 3 DPI profiles. In the screenshot below, two of the profiles are grayed out/disabled. When I cycle through the profiles with the button the mouse, it only goes through 3. What gives? I'm on iCue ver. 3.30.97. I'm running the latest M65 firmware, ver. 3.06.
  3. The problem: iCue crashes after about 10 minutes of gaming, displaying the default rainbow lighting profile. I can continue playing my game when this happens, but as soon as I exit to the main menu, my PC quasi locks up. The mouse still moves, but I cannot click on anything. Setup: CPU - Ryzen 2600, no OC RAM - 16GB Vengeance RGB, XMP profile GPU - Liquid Devil RX 5700 XT Mobo - Asus Prime X470-Pro Cooling - Custom CPU/GPU loop. Running 7 LL120s on 1 commander pro (1 port has a splitter). Also running an RGB splitter on 1 of the hub ports. iCue version: 3.30.97, but problem also happens on 3.33.246. When it started: my setup worked flawlessly for several months with 5 fans. I wanted to run a push/pull setup, so I increased the fans to 7. Troubleshooting: Thinking it all started when I added two more fans to the CoPro and that maybe there was too much on the RGB hub, I removed one of the fans from the hub (but not CoPro as I still wanted the fan to spin). I uninstalled Asus AURA. I've reinstalled Windows and even rolled back to a GPU driver version I know worked. Also, since the problem first appeared on iCue version 3.33.246, when I reinstalled Windows last night, I installed iCue 3.30.97 because that version worked, even with the Asus integration, with no issues. EDIT: I removed the splitters on the CoPro and hub and only ran 6 LL120 fans, and the problem still occurs. This is completely reproducible. If I play a game or run Heaven, after about 10 minutes, I get rainbow puke and cannot properly exit the program.
  4. Thanks for the reply. Are there any plans to expand the Corsair products you can control beyond RAM? Like to LL fans?
  5. I noticed an iCue plugin for Aura Sync posted on the Corsair downloads on 6/20/19. I downloaded and installed it, but nothing appears in either Aura or iCue. Is there any documentation for this? By the name, it seems it's a plug in for Aura, not for iCue, but as I said, there are no new options in Aura.
  6. I'm baffled, too...it's doing it again. The same fan, but this time, it won't spin past around 480 RPMs. Any other ideas?
  7. I think I got that port unstuck by doing a reset of the CoPro, because now it's working when I apply my custom curve, a fixed RPM, or a preset curve. The only thing it doesn't work with is a curve based on a fixed percent. But to answer your question, I have 5 fans. See my OP; 3 LL140 and 2 Fractal Design Dynamic X2 GP-12. The Fractal fans are non-PWM.
  8. Dev, yes, that port is set to 4-pin (it's not labeled PWM in iCue). This behavior persists whether I set it to 4-pin or "auto." By the way, the errant port is #4. If I plug this fan into the motherboard, it spins at 1300 RPMs. Any ideas?
  9. I have a Commander Pro with 3 LL140 and 2 non-RGB, non-PWM fans. RGB port 1 has a Corsair RGB hub plugged in. I control all 5 fans with iCue, and the RGB is working fine on the 3 LL fans. However, one of the LL140s will not spin past 667 RPM, no matter the profile. I have tried the 3 preset profiles, a 100%, and a 1,000 RPM profile. It will only respond to a 0 RPM profile and stop spinning. But as soon as I apply another profile, it spins up to 667 and stays there. I originally had it on port 2 of the CoPro and tried switching it to port 6 with the same symptom. I'm running firmware 3.21.7168 and have tried forcing an update of the firmware, per advice I've seen in another thread. I also have updated iCue to 3.16.56. Any help would be appreciated!
  10. Dev, thanks for the reply. I guess I was mistaken about link having this capability. As far as the temperature sensors, I have about 2 inches between the backplate of my GPU and my CPU cooler (as you can see in the attached picture). Where would you say to place a thermal probe? Some ideas I've had: taping it to the GPU backplate, taping it to the underside of the CPU fan housing (so it wouldn't heat up with the heatsink, but rather sample the air around that area), or placing it in such a way that the actual probe is suspended in the air between the CPU cooler and GPU backplate. I realize I have 4 probes, but I also don't want unnecessary cables to manage.
  11. I'm currently running 5 fans off of a commander pro in my PC, and I have different fans running off of different sensors (e.g. CPU temp, GPU temp, etc.). Is it possible to control a fan off of more than 1 sensor so the fans respond to different workloads? For example, say I currently have an intake fan set to run at 100% when the CPU reaches 75C. It would be great to have that fan run at 100% when either the CPU or GPU reach 75C. I recall seeing a post a while back about Link being able to do this, but it doesn't seem that iCue has this capability, unless I'm missing something. Thanks!
×
×
  • Create New...