Jump to content
AIDA64 Discussion Forum


  • Content Count

  • Joined

  • Last visited

Community Reputation

0 Neutral

About vlad

  • Rank

Recent Profile Visitors

1015 profile views
  1. It is normal for wip. I don`t do much coding except for occasional scripting, but even that can get... intense. Writing a plugin from scratch is no easy task. I think you did a great job so far. I like the fact that you can still use a button, even if it is controlled by Aida64. I can see the potential: having a graph for say, total CPU usage and when you press the button, you get a full (6,15,32 whatever Elgato you use) of details, like per CPU usage, power usage, thermals... Keep up the good work. I think you provide great customer support.
  2. Thank you for putting in the effort to implement this feature. It works great. Only one thing that I don`t know if you are aware: it does not know of the folder structure of the device ( meaning that it is always there, no matter if you are in the first screen or in a subfolder of functions). Interesting fact: even if it is placed over a uised buton, it only overrides the graphic and not the function. The button can still be pressed and works as configured.
  3. Well, I wish I could help with that... But I can`t. I will be patient. Thank you for your efforts!
  4. I was curious: how are things going with the implementation of the requested feature?
  5. I think that option 1 (Just like with HWiNFO) makes the most sense. You can display any value that you need, without blocking the device. The intended use scenario is having a subfolder with the sensors, while keeping the rest of the buttons for other functions. Perhaps CPU and GPU visible in all the other shortcut folders to always have a general view of the most important stats, no matter what I do. Thank you for moving so fast with this!
  6. Thank you for your efforts. I was hoping for good news. From what I have noticed in your case, no news is usually good news being a sign that you are looking into the matter. I am convinced that you will do a great job exploiting the potential of this device.
  7. It has been a week. I was curious if you can give me an answer, whatever is possible or not to implement this functionality? I am hoping for a positive answer, because I like the Aida64 software and do not really want to install HW info
  8. There is a plugin for HW info that works like this: https://github.com/exension/hwinfo-streamdeck It would be possible to implement something similar for Aida64?
  9. A big hello to the developers, followed by a question: Any chance to add LCD support for Elgato Stream Deck? https://www.elgato.com/en/gaming/stream-deck That would be nice...
  10. Noticed that this morning, when I swaped the white "background" color for a desaturated light blue that turned white on the said keys. Then I did some color testing and come up with the bug...
  11. Have another bug for you: The Numpad numbers and and the top raw numbers (so only the part actualy used by a 2 or 3 digit meter) have the B <-->R channels swaped for the "background" color. Meaning that white shows white, but using any combination of RGB that does not have R and B equal results in wrong colors, compared to the rest of the keboard "background" keys. If you put, for example a pure red you can see that very well, because the number keys "background" becomes blue instead.
  12. It works as expected. Thank you for taking care of the problem. Excelent work!
  13. Thank you for taking the time to deal with this!
  • Create New...