Fiery

@rzo11 @Arthur30 @Twisticles We've just rolled out the first beta build of the next-generation AIDA64 that fixes the GPGPU benchmarking and stress testing issues on GeForce RTX 5000 Series:

The above mentioned new beta build is now available for download:

@BHSY @COSTAJUNIOR Here it is: https://www.aida64.com/downloads/latesta64xebeta Please note that we've already implemented this new feature in the next-generation AIDA64 development build. Learn more at:

We're happy to report that we've just rolled out the first beta build of the next-generation AIDA64: https://www.aida64.com/downloads/latesta64xebeta The new AIDA64 will be rolled out as v8.00 stable update in September. Until then, please feel free to check it out as a beta build. We consider this first build already quite stable, but we'd love to hear your feedback too. As for what you can expect of AIDA64 v8.00, here's the list of improvements: native 64-bit binaries, new compiler, faster startup and operation OpenCL support for nVIDIA GeForce RTX 5000 Series GPUs to unlock GPGPU benchmarks and GPU stress testing dynamic DPI scaling (a.k.a. per-monitor DPI awareness) improved and fixed handling of multiple monitors, especially with mixed DPI settings Unicode string handling, improved localization, fixed Windows codepage discrepancy issues Windows PE v3.0+ support Windows 11 style icons (coming later in the summer) SPZIP file format for more compact and better manageable SensorPanel layouts discontinued support for all 32-bit Windows versions and Windows XP x64 In case you find any issues while using the new generation AIDA64, please report them here, in this topic. *** Compatibility with pre-Windows 10 systems *** Please note that under Windows Vista, Windows 7, Windows 8 and Windows 8.1, you may have to install Microsoft Visual C++ Redistributable for Visual Studio 2015 (x64) in order to use the new AIDA64 version. *** Migrating existing SensorPanel layouts *** Before upgrading to this build, make sure to backup your settings, e.g. your AIDA64.INI file in the AIDA64 installation folder. This is especially crucial in case you use SensorPanel. The next-generation AIDA64 revamps handling SensorPanel positioning and sizing in mixed DPI screen setups. *** Migrating SensorPanel layouts previously designed in mixed DPI screen setups *** If you have a SensorPanel layout that you designed on a high-DPI screen but used on a low-DPI screen, the layout may become too small (gets shrunk) after migrating to the next-generation AIDA64. For example, if you have a 4K primary monitor with 150% scaling setting and a 1080p secondary screen with 100% scaling, and you designed a 1920x1080 pixel sized SensorPanel that you used to fill up your secondary screen with AIDA64 v7.65, the layout will shrink to 1280x720 pixels after migrating to the next-generation AIDA64. In such case make sure to backup your settings, e.g. your AIDA64.INI file in the AIDA64 installation folder, and right-click on your SensorPanel --> Scale --> Scale all items up by 150%. Of course if you have a different scenario, for example a main monitor with 200% scaling and a secondary screen with 100% scaling, you need to use SensorPanel --> Scale --> Scale all items up by 200%. *** Report files are now Unicode encoded by default *** Report files generated by the next-generation AIDA64 use Unicode encoding by default. It may become an issue if you process the report files (e.g. CSV and XML reports) using your own solution. In such case you may need to adjust your code accordingly and/or switch to ANSI or UTF-8 encoding in AIDA64 / Preferences / Report / Report File / Encoding. *** External LCD displays may now require 64-bit libraries *** The next-generation AIDA64 requires 64-bit external libraries. For certain external displays you may need to find the right 64-bit library (DLL) file to make them work. In case your LCD stops working after migrating to the next-generation AIDA64, check the following list, grouped by display vendor: Abacom: there's no 64-bit ch341dll.dll library, so you cannot use this LCD with the next-generation AIDA64. It may be possible to develop a direct USB communication protocol and avoid relying on the ch341dll.dll library. Let us know if you have an Abacom device that you'd like to use with the next-generation AIDA64. AlphaCool, AX206, BWCT, LCD2USB, LCDInfo, Modding-FAQ, Razer, RoboPeak, Trefon, VoCore: there devices require the 64-bit LibUSB DLL, filename: libusb0.dll, can be found in the bin\amd64 folder of the LibUSB Win32 distribution package SDC Megtron: there's no 64-bit lcdDriverAPI.dll library, so you cannot use this LCD with the next-generation AIDA64. It may be possible to develop a direct USB communication protocol and avoid relying on the lcdDriverAPI.dll library. Let us know if you have a SDC device that you'd like to use with the next-generation AIDA64. Wallbraun: there's no 64-bit LUIse.dll library, so you cannot use this LCD with the next-generation AIDA64. It may be possible to develop a direct USB communication protocol and avoid relying on the LUIse.dll library. Let us know if you have a Wallbraun device that you'd like to use with the next-generation AIDA64.

You need to make sure a file named preview.png or preview.jpg gets into the SPZIP package. It can be a hidden image on your layout with the required filename, or after creating the SPZIP file using the Export feature on the SensorPanel Manager you can open the created SPZIP file (with a tool that can alter ZIP archives) and place the file manually there.

The OP idea was about import, and I assume your idea is about exporting, isn't it?

Hi Guys, We're thinking of showing a preview image when you try to import an SPZIP format SensorPanel layout. So below the question "Are you sure you want to overwrite your existing SensorPanel settings?" in the same dialog it would show you the layout thumbnail. If you like the idea, let us know if the filenames preview.jpg and preview.png for the preview image would be suitable for you. So in case AIDA64 finds an image placed in your SPZIP archive named preview.jpg or preview.png it will not use it for the layout but just as a preview image shown at import.

You need to build your layout in AIDA64 / Preferences / Hardware Monitoring / LCD / LCD Items. You can import a layout there too in case you wanna start your layout based on someone else's layout.

How about this one? You can import this one into your Turing layout too: https://download.aida64.com/SensorPanelCoreWide.zip https://www.aida64.com/user-manual/sensorpanel/sensorpanel-core-template

Internally, we were debating on whether the background image update would be -- as you suggested -- possible only on demand, by e.g. pressing an "Update Image" button. But we ultimately went for a less confusing and more automatized solution and just implemented the 30-second delay between image updates. Since the VU1 framework on itself also has a built-in protection about updating the e-ink with the same image, this solution IMHO is safe enough to prevent major issues to happen. The only inconvenience is that during the VU1 layout design process you can see the changes you make with a bit of a delay. But fortunately on the LCD layout preview (in AIDA64 Preferences) you can see what changes, so IMHO it's okay this way, and it's not too much of a compromise.

Hi Darius, You can acquire a license in our Online Store at: https://www.aida64.com/online-store Regards, Fiery

I apologize for the late response. We've just rolled out VU1 dial support in the latest AIDA64 beta build. Please check the following forum topic and use it for further discussion on all things VU1

Thank you for your feedback! We'll expand the number of supported VU1 dials from four to eight in the next AIDA64 beta update. I personally would feel more comfortable about frequent e-ink updates only after discussing this matter with the project owner.

I apologize for not responding to your now -- I admit -- quite old topic. And no, you haven't done anything wrong, but we simply ran out of development resources last year and couldn't take on such projects that didn't attract a wide range of users of AIDA64. Fortunately in the 2nd half of 2024 we managed to expand and optimize our development team in order to take on a variety of new and old projects.

The beta channel of AIDA64 will soon migrate to a brand new AIDA64 version that will support Unicode characters. I assume that will solve this issue too. Make sure to enable automatic updates to beta builds in AIDA64 / Preferences / General / NetUpdate / Update type / Stable and beta updates.

No, what I meant is to do away with the current way of switching between pixel strides: you currently left-click on the "1 px" (or "2 px", etc) button in the SensorPanel Manager to cycle through the pixel stride options. We can either keep that behavior and add a right-click context menu, or simply get rid of the cycling through pixel strides with left-click and instead show the context menu when you do a left-click (instead of right-click).

Thank you for your feedback. We definitely don't wanna remove the keyboard navigation, especially because we're investing more and more energy into improving the accessibility aspects of AIDA64. Right-click context menu is coming your way in the next build Related to that: do you guys think we should do away with the normal click (left-click) behavior and display the context menu with left click too? It would mean that you couldn't cycle through the various strides, but instead would always have to use the drop-down menu to select the stride.

We'll temporarily suspend the always-on-top behavior of the SensorPanel while the SensorPanel Grid and SensorPanel Manager windows are open to prevent those smaller windows getting "tuck away" under the SensorPanel window.

Quite frankly, I'd prefer to find a solution without using 2 such navigation blocks. IMHO two seemingly similar blocks would confuse novice SensorPanel users as well as would make keyboard based navigation requiring an unnecessary learning curve. Instead, how about a right-click menu on the pixel selection button where you can easily choose you preferred stride? If you reckon that would work, please provide us a comprehensive list of stride variations to include in the list. Would e.g. 1px, 5px, 10px, 20px, 50px, 100px, 150px, 200px be sufficient?

Thank you for your feedback!

It looks great! Thank you for your feedback. And yes, we're aware of the fact that the VU1 Server only updates the background image when it changes, but when you fiddle around with the layout, every small change (like trying a different text size, switching the icon on or off) would generate a new background image that the VU1 Server will consider a new image and so would update the display.

It may open behind the SensorPanel window in case you have Keep SensorPanel the topmost window (always on top) enabled for the SensorPanel. We'll fix that issue in the next AIDA64 beta update.

The dump indicates that AIDA64 couldn't load its kernel driver for some reason. Do you have it (AIDA64) properly installed?

Thank you, I've sent you an email about this matter.

We cannot really do much about a device that has a slow screen update rate.