Fiery

Thank you for the feedback

Thank you, we'll add the Aquaero temperature in the next beta

Thank you. I'm afraid we need Aqua Computer's kind assistance to figure the missing bits out. They said they will be able to give us a hand next week, so stay tuned Thank you, we'll fix that.

That is a Windows limitation, you can look it up. Many websites bashed Windows 8 and Windows 8.1 for example, when they were rolled out, that they still don't solve the DPI scaling issues. E.g. http://techreport.com/blog/25797/high-ppi-support-in-windows-8-1-still-not-so-great Yes, it is possible to develop a DPI aware application user interface, but it requires a complete rewriting of the user interface code, and reproducing all graphical content like icons and placeholder pictures as well, in multiple DPI levels. The user interface part of AIDA64 is over 200.000 lines of code, not in the league of such utilities like WinRAR or DropBox. Don't get me wrong, they are great utilities, but they don't have a complex UI like AIDA64. And yes, Microsoft fixed Office 2013, but it's the least you can expect from the company that develops Windows and fails to come up with a real solution to the DPI issues And I'm pretty sure not even Microsoft has a full software portfolio that would support proper DPI scaling. As for 4K, as I've mentioned above, when you use 200% DPI (or 400%), things are much less blurry. We've got a Win8.1 tablet with a 2560x1440 native resolution, and we use 200% DPI scaling on it. AIDA64 looks fine there, but of course it's not as sharp as without DPI scaling. And with 4K displays you can simply use 200% DPI scaling setting to avoid blurriness -- which affects most Windows applications. You've listed a few exceptions, but the majority of Windows applications are still not fully DPI aware. We would be more than happy to come up with a quick fix for the DPI issue, just like we do with other bugs or anomalies about AIDA64. But with DPI scaling, there's no quick fix. Yes, you could add a simple entry to the manifest file to enable DPI awareness, but then the whole UI would fall apart. You could of course rewrite 200.000 lines of code, but it would take a hell of a lot of time. And quite frankly, we're still hoping to see Windows 10 or worse case Windows 10 SP1/Update1 to come up with a real solution to the DPI issue. A new windowing system that is based on relative placement and percentage-based UI element dimensions would be terrific. Of course that would also raise the need to rewrite all the UI code, but at least it would mean a proper solution, a proper fix to the problem, not just beating around the bush. I would personally feel like a fool if we had to rewrite the UI code to make it DPI aware now, and then having to rewrite it again when Microsoft comes up with the proper DPI solution...

I like the idea of animations, but it's not really feasable to do that. AIDA64 supports over 50 different LCD devices, but only a few of them are capable of providing 30+ FPS update rate (which would be required to properly display animations). And even if you would push 30+ frames per second to the Razer or Logitech G19 LCD, it would put quite a pressure on the CPU to render that many frames a second. I'm not sure whether certain eye candy would worth so much CPU cycles and hassle BTW, AIDA64 has an Alerting facility that could warn you about excessive temperatures, a stopped cooling fan or voltage drops.

That is a limitation of Windows, and we cannot fix it from our end. User interface layout of classic Windows applications is still based on pixel measurements, so when you use DPI scaling, all pixels of the UI are scaled automatically by Windows. When the DPI is set to 200%, text and images are not that blurry, but in your case it's not set to 200%, but more like 150%. The seemingly incorrect desktop resolution is also due to the DPI scaling: this is a trick Windows uses to make the application believe it is running on a less high resolution display than the actual hardware supports. We've tried to come up with a workaround for that, but haven't been able to scale up the reported resolution to make it an accurate value Regards, Fiery

Thanks for the feedback. Here's a new AIDA64 Extreme beta update: http://www.aida64.com/downloads/latesta64xebeta In this beta we've fixed the liquid levels calculation issue, and added fan voltages, fan currents and fan powers. We've also added the new readings to all hardware monitoring modules, such as OSD Panel, Desktop Gadget, LCD, SensorPanel, Logging, External Applications, and Alerting. AIDA64 doesn't support measuring or displaying decimal digits for temperature readings. We do not believe that's a necessary information, since there's no practical difference between having a certain hardware component running at 35.1 or 35.4 Celsius. We've checked the pump properties, but so far we haven't been able to identify those readings in the Aquaero/Aquaduct information block. It must be there somewhere, but it's not documented We may be able to find it if you could help us by submitting an Aquaero sensor dump: right-click on the bottom status bar of AIDA64 main window --> Sensor Debug --> Aquaero Dump. Copy-paste the full results into this topic, or attach the results as a TXT file to your post. When you issue the dump, please takes notes (or create a screen shot) of the actual values of the pump related readings, so we can try to find the values among the Aquaero raw registers in the dump. We've also tried to find a solution to calculate water quality, but so far we've had no luck about that. We'll try to ask Aqua Computer about that, maybe they would be kind enough to point us to the right direction. BTW, Aqua Computer has contacted us to notify us about an upcoming major change in the Aquaero registers layout. They said once the new firmware is available for download, they'll send us documentation on the new layout to let us adjust AIDA64 accordingly. We'll try to be quick about that, but please keep in mind that if you update to the new firmware, the values displayed by the above linked AIDA64 beta update may become wildly inaccurate due to the data layout changes. Thanks, Fiery

Thank you. It seems the issue is due to Logitech's Gaming Software package sometimes not being able to insert the necessary keys to the Registry to let 3rd party applications auto-detect the API DLL path. We've added a workaround to handle such issues. Please upgrade to the latest beta version of AIDA64 Extreme available at: http://www.aida64.com/downloads/aida64extremebuild3215x1k0nqwmldzip After upgrading to this new version, make sure to restart Windows to finalize the upgrade. Let me know if it helps.

Thank you for the screen shot. Please upgrade to the latest beta version of AIDA64 Extreme available at: http://www.aida64.com/downloads/aida64extremebuild3215x1k0nqwmldzip After upgrading to this new version, make sure to restart Windows to finalize the upgrade. Let me know if it helps.

Thank you for the feedback

Thank you for the feedback. Modern AMD processors (APUs) usually provide such unrealistic CPU core diode temperature readings at idle. However, once you put a load on the CPU, the temperatures start to make more sense.

Thank you for the feedback

Thank you for the feedback. Does Aquaduct report 2% for Level 2? Does it report the liquid levels measurement unit as LPH (l/h) ? Please note that the existing AIDA64 sensor dumps currently do not cover Aquaero/Aquaduct raw registers output. We'll need to add a specific Aquaero/Aquaduct sensor dump to see how the registers look like.

You will need to extend (renew) your existing license if you want to download further updates. Updates and technical support are tied together, since in many cases when you experience an issue about AIDA64, we'll need to issue a new beta or stable update to fix it up.

You can download the mentioned new AIDA64 Extreme beta update from: http://www.aida64.com/downloads/aida64extremebuild3211m4wrgf1cnuzip Please let me know how it works.

Here's the new AIDA64 Extreme beta that implements the fix for the gauge label issue, and also supports down to -1000 pixel coordinates: http://www.aida64.com/downloads/aida64extremebuild3211m4wrgf1cnuzip

The automatic LCD page switching feature has been added to the latest AIDA64 Extreme beta release available at: http://www.aida64.com/downloads/aida64extremebuild3211m4wrgf1cnuzip After upgrading to this new version, make sure to restart Windows to finalize the upgrade. You can configure it in AIDA64 / main menu / File / Preferences / Hardware Monitoring / LCD / LCD Options. Let me know how it works

We've just implemented support for Aquaero and Aquaduct devices. Please refer to the following forum topic, and post your findings there: http://forums.aida64.com/topic/2611-aquaero-and-aquaduct-sensor-support/ As for Thermaltake DPS-G, we're planning to work on that in January.

We've just implemented sensor support for Aquaero and Aquaduct devices. Please refer to the following forum topic, and post your findings there: http://forums.aida64.com/topic/2611-aquaero-and-aquaduct-sensor-support/ This topic closed. Regards, Fiery

We've just implemented sensor support for Aquaero and Aquaduct devices. Please refer to the following forum topic, and post your findings there: http://forums.aida64.com/topic/2611-aquaero-and-aquaduct-sensor-support/ This topic closed. Regards, Fiery

We've implemented sensor support for Aquaero 4, Aquaero 5, Aquaero 6, Aquaduct Mark 2, Aquaduct Mark 3, Aquaduct Mark 4, and Aquaduct Mark 5 devices. We'll need to refine and extend the current sensor module, so please take the first AIDA64 beta as ... well, the first beta http://www.aida64.com/downloads/latesta64xebeta For Aquaero 4, Aquaduct Mark 2 and Aquaduct Mark 3, the following readings are available in the first beta: - 6 generic temperatures - 4 fan speeds (RPM) - 1 flow sensor (LPH -- litres per hour) For Aquaero 5, Aquaero 6, Aquaduct Mark 4, and Aquaduct Mark 5, the following readings are available in the first beta: - 16 generic temperatures - 4 fan VRM temperatures - 12 fan speeds - 4 flow sensors - 4 liquid level sensors (%) Fan VRM temperatures, flow sensors and liquid levels are only available on the Computer / Sensor page currently. As soon as the Aquaero sensor module gets more mature, we'll add the new type of readings to the rest of the AIDA64 hardware monitoring modules (e.g. OSD Panel, SensorPanel, LCD). Note: For Aquaero 5, Aquaero 6, Aquaduct Mark 4, and Aquaduct Mark 5 you need to have Firmware Revision 1036 or later to assure AIDA64 uses the proper register offsets for sensor readings. It may or may not work with older firmware releases. Please let us know how it works on your Aquaero/Aquaduct device. Note that Aquaeros/Aquaducts are very complicated devices, so we'll need a bit more time to put every piece of the puzzle together. Let me know if you miss anything from the current capabilities of the Aquaero/Aquaduct sensor solution. Thanks, Fiery

1) Do you have the latest Logitech G19 drivers installed? If yes, then please try to reinstall it, and restart Windows. 2) Are you using AIDA64 v4.70? (latest version) Regards, Fiery

Yes, we've seen that when they unveiled it a month ago. We definitely will support it, but we'll also introduce our own solution for the same purpose. Stay tuned Regards, Fiery

Alright, it will be -1000 pixels for both the X and Y axis

Yes, I understand the motivation behind using negative coordinates What I'm wondering is: what should be the absolute minimum for those values? X = -50 and Y = -50 would be enough? Or should it be more like -1000 pixels?