Jump to content

cmdshft

Members
  • Posts

    9
  • Joined

Reputation

10 Good
  1. Ah, but that kinda defeats the goal haha. I would like to obviously have them both running at the same time.
  2. Hello. Would like to make a suggestion that since Elgato is owned by Corsair, couldn't iCue be made to pass along fan/pump/temp sensor data to the StreamDeck or at least make them accessible by HWinfo64? I like to monitor my stuff via the StreamDeck so it would be nice to see fan speed and coolant temp as well, instead of having to open up iCue to see.
  3. I went to drain my loop today in order to change up some fittings today, went to refill the loop and noticed that my pump would not run at 100% using my 24-pin jumper, so my loop would not fill up. Every time I flipped the PSU switch, it would run 100% for about 2-3 seconds, then run slow. I had no choice but to boot the system up while slowly filling my res so when iCue loaded, if my pump was still alive, it wouldn't suck in air and overheat anything. My pump came alive again after I set the pump to 100% duty cycle. To test an idea, I left it that way in iCue and rebooted with my jumper. And the pump ran at 100%. So does the CPro run pumps based on the last known config it was set to in iCue? Why does it do this and is there a way to disable this so I can leave it on my normal profile and not need to remember to switch to my 100% profile when I want to drain and refill?
  4. I have a select few sensors displayed on my streamdeck for my CPU, RAM and GPU and would like to monitor my coolant temp via the streamdeck. I have a 2-pin sensor installed on Temp 1 of the Commander Pro and would like to see that via HWiNFO64 so I can add it to my monitoring.
  5. Tbh, you don't really need a flow meter anyway. If you have poor or no flow, your temps will tell you.
  6. https://streamable.com/nxocj This has only been happening on my Vengeance RGB Pro and my LS100 LED strips. I have tried exporting and re-importing the profile, tried remaking the profile from scratch... I have yet to try reinstalling iCUE. Anyone have any other ideas? Here is my profile: https://cdn.discordapp.com/attachments/448544761633177610/678722475541921802/neon_and_teal.cueprofile EDIT: Reinstalling iCUE did not resolve the issue.
  7. Just to be clear, you tried selecting "RGB Strip Light" under one of the NPro lighting channels? I ask, because I was connecting them to my CPro and did not select that on the channel I had them on in iCUE. Thought they were defective or the CPro was bad too... Once I double checked that, I got them working.
  8. Would love to see a way to choose a lighting option to occur on the specific macro key that is being activated and have it stay activated for the duration of the macro and then deactivated when the macro is stopped. Right now, it doesn't seem that there is a viable option, the only way to get a key illuminated is by setting a custom illumination option, hiding it in the lowest layer, then selecting it for a maximum duration of 99 seconds. Deactivating the macro doesn't stop the light after this. Any way to update iCUE/Firmwares to support this?
×
×
  • Create New...