Jump to content

fludd

Members
  • Posts

    5
  • Joined

Everything posted by fludd

  1. For what it's worth, I attached a screenshot from process explorer to better understand what causes the high cpu usage for the iCUE application. Maybe it helps with debugging.
  2. I'm absolutely sure, that they have capable programmers - and the idea of the nexus companion is pretty good, too (despite the fact that its viewing angle is a little too small). My thought was more like, how could we support developing the software and trying to remove bugs. Yeah, iCUE seems to be finally going into the right direction, but as you said - due to the fact that there is no financial gain, bugfixing will only be done, if many people complain and complain all over again about the same stuff. The problem nowadays with the whole steering of fans/rgb/whatever is that there are many ecosystems and not one single standard, where anybody could himself attach to. Many users complain about that - not here, but in different message boards. The reason behind this, is to keep the users within the ecosystem of the single manufacturers, but it would be more - interesting - if there was a monitoring or controlling standard for the whole rgb/fan/etc. stuff.
  3. Due to the fact that there are many problems with the iCUE software, in my opinion, you should make this software open source. The benefit of this would be a strong community with capable programmers who could help with fixing bugs within iCUE. Dear reader: What is your opinion on that?
  4. Getting the error as well with 3.34.170 ... restarting the system or shutting it down triggers it.
  5. Hi there! Just a quick feature request here: It would be great, if you added a RAM usage widget. I don't know, if this software is written in C++ or anything else, but you could use this to get the values and create a widget just like the cpu percentage widget. It might even help you in the quest of the search for the cpu usage problems in the icue software. Just create an instance of the object below and call the needed functions as few times as possible to save clock cycles. // system_stats.h #pragma once #include "TCHAR.h" #include "pdh.h" #include "windows.h" class SystemStats { public: SystemStats(); int currentCpuUsage(); int currentRamUsageInPercent(); int freeMemoryInPercent(); private: PDH_HQUERY cpuQuery; PDH_HCOUNTER cpuTotal; }; // system_stats.cpp #include "system_stats.h" SystemStats::SystemStats() { PdhOpenQuery(NULL, NULL, &cpuQuery); PdhAddEnglishCounter(cpuQuery, L"\\Processor(_Total)\\% Processor Time", NULL, &cpuTotal); PdhCollectQueryData(cpuQuery); } int SystemStats::currentCpuUsage() { PDH_FMT_COUNTERVALUE counterVal; PdhCollectQueryData(cpuQuery); PdhGetFormattedCounterValue(cpuTotal, PDH_FMT_DOUBLE, NULL, &counterVal); return (int)counterVal.doubleValue; } int SystemStats::currentRamUsageInPercent() { MEMORYSTATUSEX memInfo; memInfo.dwLength = sizeof(MEMORYSTATUSEX); GlobalMemoryStatusEx(&memInfo); return memInfo.dwMemoryLoad; } int SystemStats::freeMemoryInPercent() { return 100 - currentRamUsageInPercent(); }
×
×
  • Create New...