Jump to content

B0D0

Members
  • Posts

    18
  • Joined

Reputation

10 Good
  1. Could you explain that in more detail?
  2. OK, helps me alot. Thank you very much!
  3. DevBiker, I know that the fans are spinning and I assume that the pump is running, or otherwise the system would shut down within a minute or two. However, when I sign off in my LOCAL machine, I see that the light settings on pump and strips start that rainbow thing, while my (signed-in) custom light setting is static. So if this is different, than the curve for fans and pump will be as well. That means that iCUE is then running a different setting. Which one would that be? Is there something I oversaw that I could make iCUE use under ALL circumstances? Where resides that "separate file" you mentioned? And finally, again, what could be the reason, that iCUE on the REMOTE machine sees non-Corsair devices but idiotically none of its own Corsair devices? In many years of using remote desktop on multiple machines I have never ever seen any system- or application-software that would act differently depending on whether being invoked locally or remotely.
  4. Bump .. Is there no one out there with an answer to my questions? Did Corsair support read this, as they always say they would? Again: While remotely working on the computer in question, I can do ABSOLUTELY EVERYTHING just as if I would be working local. Why the heck does that not apply to iCUE? I would be very happy if someone could help me with this one.
  5. Don't really get that. What do you mean by "interactive console"? When I open iCue on the remote machine (and now only see non-Corsair devices) I am logged in to that console, right? And besides of that: When you sign off on your machine, then there would be no control of pump and fans? The basic question is, what is different in iCue as compared to LINK, where I had no problem of remotely seeing ALL devices, including Corsair's.
  6. Hi. After years of using Link I finally switched to iCue on two of my computers. Now there is a major problem which I never saw with Link, and that is with remote access (Windows RDP). I can see iCue on the remote computer, but iCue does not see its own Corsair devices (neither H115, nor Commander Pro and the fans attached to it). So I see no temps or fan speeds. iCue only shows me the non-Corsair devices like CPU, mainboard, DRAM, graphics card. In non-remote access I can see everything. And what makes it even worse: When you RDP into a computer, the currently signed in user is signed off and the system stays in this state until you sign in again, either directly or remotely. But when iCue cannot see (and control) the pump and fans while a remote user is signed in, it most certainly cannot do so while no user is signed in. Again, this has never ever been a problem with Link. And to clarify: To enter this problem, you do not even have to open iCue while remotely accessing the distant computer. Did you ever run into this problem? Do you have any suggestions for me?
×
×
  • Create New...