Jump to content
AIDA64 Discussion Forum


  • Content Count

  • Joined

  • Last visited

Community Reputation

0 Neutral

About vlad

  • Rank

Recent Profile Visitors

887 profile views
  1. Well, I wish I could help with that... But I can`t. I will be patient. Thank you for your efforts!
  2. I was curious: how are things going with the implementation of the requested feature?
  3. 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!
  4. 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.
  5. 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
  6. 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?
  7. 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...
  8. 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...
  9. 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.
  10. It works as expected. Thank you for taking care of the problem. Excelent work!
  11. Thank you for taking the time to deal with this!
  12. Thank you. It works much better. Still a problem with using 2 or 3 digits to represent a sensor, the number keys (top raw and and numpad numbers for 3 digits) not responding to background color (unlit).
  13. Yes there is, but if you have a sensor maped to a raw of keys, say qwerty, and the "bar" is up to lets say "letter" the ones after it from"y" onward, will remain unlit, regardless of the "background color" chosen. So if you map 3 sensors to the 3 raws of keys: "qwerty", "asdf" and "zxcv" you will have most of the key unlit, unless the sensor "bar" ar always close to 100%
  14. Hello to the developers! Thank you for keeping such a good care of this software product. Regarding the feature that is the subject of this topic: after using it for 2 months I have some feedback. Right now, if you configure a raw of keys to show something, you loose the background color (the one you set globaly), so if the "bar" is half full, the rest of the key go unlit. Why this is a problem: if you have the qwerty, asdfg, zxcvb raws asigned to some sensors that do not reach 100% most of the time and instead go arond, let`s 50% you end up having most of your keys unlit, which is making the keaboard hard to use in dim light. If it is not to much trouble, it would be nice to have the extended areas of the keyboard and other rgb peripehrals available to maping (like zones on the mouse, extra keys on keyboard and so on...). I know that are a lot of peripherals out there so it may be hard to cover them all, but at least the products from the most used peripherals like Corsair, Logitech, Razer... Anyway point 2 is not that important, but point one ( persistent background color for raws of keys ) it would improve usability. In the hope that you will have time to address this request I thank you and wish you well!
  • Create New...