Jump to content

A_Fnord

Members
  • Posts

    10
  • Joined

Reputation

10 Good
  1. Well that's one of the issues with 3.19, but the whole "system hog" bit, where Icue just gobbles up system resources is nothing new, and 3.19 seems to be worse yet. But the system hog issue, when icue claims a lot of cpu-power has been around since at least version 3.3. In 3.16 icue would gladly just claim the first CPU core and sit on it, constantly using all its power, while eating 500mb+ of RAM.
  2. The issues experienced with the latest version of iCUE are not exactly new though. They seem to be more frequent in the latest version, but many of the issues I've seen reported here are old issues. So while no, it might not be misleading, I do think there's a deeper rooted problem here than a bad release, something that they really should have looked into a long time ago.
  3. As someone who mostly uses it to turn things off, I have far more dislikes than likes: Buggy For some reason it claims my first processor core after running for a while, causing my system to lag Loves to eat RAM. Not uncommon for it to take up about 500-600mb Lacks a simple "lights off" button
  4. I've got a weird problem. Right now I have a Corsair Harpoon RGP 0030, and when I opened iCUE a while back, I got a notification about there being a firmware update for it. So I updated the firmware. Now the two side buttons won't work unless I have iCUE running, and iCUE itself gobbles up system resources like it owned the place (it's not uncommon to see it take up 50% of my processor power for no apparent reason, and Corsair services will gladly eat 600mb of RAM). I don't have any other corsair products than this mouse, there's nothing else iCUE should be interacting with. *edit* Seems like iCUE basically claims the first core, Core 0, as its own once it's been running for a while. Not what this thread is about, it's about the side buttons, but reading the forum, I see that plenty of other people are reporting a similar issue, so something is fishy about iCUE.
  5. The SDK in this case seems to be something that works with certain games and software, and allows them to send information to your RGB devices. Basically the game can tell your keyboard to start shining blue to signify that you're on the blue team, or light up certain parts of the keyboard and so on. I don't use it, so I don't know the details. I don't know about earlier versions, but at least on the latest version of iCUE you can disable it by going into settings->ICUE SETTINGS->GENERAL->Uncheck "Enable SDK". Your problem sounds quite different from mine though.
  6. Just an update, in case anyone finds this in the future, and finds this useful: Ever since I turned off the SDK, iCUE has been behaving well. It takes a reasonable amount of system resources.
  7. I don't have Wallpaper engine. And I don't know what apps use the SDK. The processes I had running (apart from the ones related to windows) were: Steam Nvidia suite Avira antivirus (and some related processes) Google Chrome I can try turning the SDK on again and see if iCUE becomes a system hog again *edit* As soon as I turn it on again, CPU use goes up. So now we at least know that the issue is in some way related to the SDK, even if we don't know why.
  8. I think I found the issue actually. When I unticked the "enable SDK" option, iCUE suddenly went from what you see above to 0.2% CPU, 131mb RAM & 6% GPU, when it's my active window. Still more ram than I'm comfortable with though. So that SDK is a real resource hog
  9. Sure thing. It's not exactly the best system out there, and is in dire need of an upgrade soon, but it "works" (even in modern games I get acceptable 30+ fps) Intel Q9450 CPU 8GB Ram GTX 960 2gb Running an up to date Windows 10 Pro No sound card (other than the built in one) or any other external things, and no other RGB devices. I read that some wireless headphones could cause issues with iCUE when trying to look things up, and I don't have one of those either. I have tried uninstalling and re-installing iCUE, and it temporarily fixes the issue, but then after an hour or so it's back to using a lot of resources.
  10. Hi there iCUE is causing me quite some issues. I'm only using a single Corsair device, a Harpoon RGB gaming mouse, and the only thing I'm currently using iCUE for is turning off the darn LED in it. I found references to iCUE potentially using a lot of CPU if you had flashy RAM. What's it even doing with my GPU? Corsair.service is also using about 15% of my CPU. Oh, if it's relevant, the version I have installed is 3.16.56, which seems to be the latest one. If there's no good fix for the program (really, I don't feel like having a simple program for controlling my mouse take up this much resources...) is it possible to turn off the LED in my mouse without having the program running? In a previous mouse I had (not Corsair) I had to open it and remove the LED, but I don't think I can do it with this mouse without completely ruining it. (And just a pre-emptive thing, in case someone wants to be a smart-donkey and asks why i got a mouse with an LED in the first place: It's surprisingly hard to find a mouse which has the right placement of the side buttons for me, let alone one without an LED)
×
×
  • Create New...