Jump to content

Grestorn

Members
  • Content Count

    107
  • Joined

  • Last visited

  • Days Won

    3

Everything posted by Grestorn

  1. Wow. I'm sure I've looked at this at some point in the past. Totally forgot that this was there. Sorry for bothering you! And thanks a lot for adding the HighFlow Next support!!!!
  2. No, I'm not. I don't know how the export works actually, but something has changed obviously, since it used to work. My guess would be that you've changed the name of the exported field, so the Aquasuite doesn't recognize it anymore. Is there anyway to check the actual values exported? I can get into touch with Aquacomputer, but I need as much info as possible. Also, while we're talking about the Aquasuite: Are you planning on adding the new devices to your data import? Like the High Flow NEXT which has been introduced a couple of months ago?
  3. Yes, I don't doubt that it's there - I never did (see my original posting). The problem is, that it's no longer exported to the Aquasuite! That's my actual problem
  4. I'm using the AIDA64 data in the Aquacomputer Aquasuite. Since the last version(s) the value for the Ampere (RTX 3090) GPU temperature is no longer listed there. They suspect this to be a problem on AIDA's side. Since the value is still displayed in the AIDA64 sensor page, I presume that it might be a problem with the export? Here the values imported from AIDA in the Aquasuite:
  5. Thanks, Fiery. And I totally agree. But since digital PSUs are still a bit of a rare curiosity, I doubt that will happen anytime soon.
  6. I've been using digital PSU's from Thermaltake for ages now. I like how they can be monitored through AIDA64. Unfortunately, my current PSU "Toughpower iRGB PLUS 850W Platinum" has issues with my new RTX 3090. The occasional hard reset right when the 3D mode kicks in, most likely caused by the PSU acting too fast on a power spike caused by the 3090. So I want to replace the PSU. I'm a bit fed up with TT, I thought my PSU should be easily enough for the RTX 3090. I don't want to lose the monitoring feature of AIDA64, so I'd like to get an alternative which can be monitored.
  7. I don't need that checkbox right now, cause AIDA64 is used to monitor AC stuff at the moment. But in case I'd need a fast response of AIDA's monitoring, it would be nice if I could turn the AC polling off temporarily.
  8. Aquacomputer updated their Aquasuite the other day. With that update, they also updated the firmware of many of their hardware components, including the D5 Next to version 1014. Since that update, AIDA64 doesn't see the D5 Next's values anymore. HWInfo still sees them, though, so the export must work technically, there seems to be some misalignment between AIDA64 and the D5 Next. Other values of Aquacomputer's components are still showing up fine, only the D5 Next is affected (on my system). In that regard, I'd still very much appreciate if it would be possible, t
  9. I think this is not about averaging. It's about the issue that using a discreet multiplier to calculate the frequency is simply wrong for Ryzen. That's why Ryzen Master shows such a vastly different core frequency than AIDA64. In HWInfo shows an "effective CPU clock" for each core, which actually reflects the value Ryzen Master is showing. See this: https://www.hwinfo.com/forum/threads/effective-clock-vs-instant-discrete-clock.5958/
  10. Hi, after a very long time of using my old 5960x system and AIDA64 passively, I'm now building a new machine based on Zen 2, and because of that I'm interested in the latest developments once again. I've just read this article about issues with AMD Zen's CPU clocking mechanics: https://www.techpowerup.com/review/1usmus-power-plan-for-amd-ryzen-new-developments/ What stands out there is the statement of HWInfo's author, he claims that the "traditional" way of measuring a CPU (core) clock has several issues, which is something I've been wondering for quite some time myself
  11. I looked up the LCD profiling dump (rmb on the status bar, SensorDebug->LCD Profiling Dump). And I realized that there are things listed there, which I don't actually use: ------[ Versions ]------ Program Version : AIDA64 Extreme v5.92.4376 Beta BenchDLL Version: 4.3.759-x64 Windows Version : Microsoft Windows 10 Pro 10.0.16299.19 (64-bit) ------[ Motherboard Info ]------ Motherboard ID : <DMI> Motherboard Model : Asus Rampage V Extreme Motherboard Chipset : Intel Wellsburg X99, Intel Haswell-E DMI MB Manufacturer : ASUSTeK COMPUTER INC. DMI MB Product : RAMP
  12. Well, if you're in need of suggestions for improvements... The possibility of moving more than one item at a time The possibility of changing certain values of more than one item at a time Faster z-Ordering (Drag&Drop) Option to select an item from the preview (like each click on a spot activates the next item down the z-ordering at that spot) Those come to my mind right away...
  13. Hi Fiery, I didn't know about that function. You learn something new every day... So, in my case it's the aquearo that takes almost all of the time. Is that a technical neccessity or something that could be optimized, either on your side or on the side of AquaComputer? Thanks! ------[ Versions ]------ Program Version : AIDA64 Extreme v5.90.4251 Beta BenchDLL Version: 4.3.741-x64 Windows Version : Microsoft Windows 10 Pro 10.0.15063.413 (64-bit) ------[ Motherboard Info ]------ Motherboard ID : <DMI> Motherboard Model : Asus Rampage V Extr
  14. I know this has been an issue many times already, but I'd like to bring it up again, sorry for that. I know that setting the update frequency to a low value doesn't do any good if the update cycle of all sensor data is taking longer than the update frequency. I tried to speed up the cycle by disabling everything but "Load kernel driver" in the Stability tab. Still, the update is at best about once a second. Some values (like volume) even much lower. Isn't there any way to speed this up?
  15. That should work fine enough for my purposes as well. I'm sure I'll figure out a way to use it properly...
  16. Yes, way to go... !! Can't wait to get this in the Panel. In theory, separate indicator values would work well. For a simple "LED" indicator, I'd make create bar elements for each value on to of each other. 0 would make them very small (i.e. invisible) while 1 would make it big enough, so that only one color becomes visible. This way you could also use a "sliding" indicator, showing the throttling reason over time (similar to GPU-Z's display) by placing a 'graph' element for each value on top of each other. 0 being all the way down and 1 all the to the top.
  17. Hm, when I look at the graphs of MSI Afterburner, it seems that the bits are actually mutual exclusive. And GPU-Z also displays it as a single state. So it seems even though it's technically represented as a bit field, there's only one bit that can be set at one time (which also would make sense logically). I'd just go for a single value with one discreet value for each state. A string wouldn't help me, as you said yourself.
  18. Thanks for this status report! Very much appreciated. I thought that these values are published in the NVAPI but then you'd have certainly found it yet. Maybe you can contact the guys from GPU-Z, RivaTuner/Afterburner. They show this value, among others. For how to integrate it: Either make a single value which could assume discreet values like 0=No limit, 1=Power Limit, 2=Temperature Limit, 3=Voltage limit. That would be fine for me, because I'd use this to create a color indicator (making a big bar which is mostly hidden behind a texture so that you can only see the bar's color t
  19. Might I bring my request back to your attention?
  20. No insight on that idea? I'd really appreciate that function!
  21. Hi! I've been using AIDA64 for a some years now and I've put a lot of work in my panel - I really appreciate the support you put into AIDA64! One thing I'd like to add to my panel is the reason for the current limit for the GPU. GPU-Z, EVGA Precision X and MSI Afterburner all have indicators to report the cause for throttling as "Power limit", "Voltage limit", "Temperature limit" or "No Load Limit". I guess these values are available through the nvidia API. I guess the best would be to 4 different sensor values for each of those, each of them being 0 or 1. I'd then be able to a
×
×
  • Create New...