Jump to content

Fiery

Administrators
 View Profile  See their activity

  • Posts

    12490

  • Joined

  • Last visited

  • Days Won

    558

 Content Type 

Everything posted by Fiery

  1. Fiery
    Let's handle this issue here, no need to use 2 different support channels. As for the bug, it's not actually a bug. There's no way to sort the available disk drives in a way to recognize which one is added the last to the list. So there's no way to sort them in "arrival order" so to speak. Windows itself manages disk drives in a very peculiar manner, and quite frankly we cannot understand the logic behind the ordering of drives by Windows. For example, when you have a single M.2 NVMe drive (Samsung SSD 980 PRO 1TB) installed as a system drive, here's how Windows 11 24H2 indicates the steps of adding more and more SATA SSD drives to the system: 1) When connecting a new single SATA drive to SATA connector P1, the list of drives as managed by Windows (no special ordering like alphabetical sorting): KINGSTON SV300S37A120G Samsung SSD 980 PRO 1TB 2) When connecting another new single SATA drive, this time to SATA connector P3: Corsair Force LS SSD KINGSTON SV300S37A120G Samsung SSD 980 PRO 1TB 3) When connecting another new single SATA drive, this time to SATA connector P2: Corsair Force LS SSD KINGSTON SV300S37A120G Samsung SSD 980 PRO 1TB INTEL SSDSC2BB120G4 4) When connecting the 4th new single SATA drive, this time to SATA connector P4: INTEL SSDSC2BB120G4 Corsair Force LS SSD KINGSTON SV300S37A120G Samsung SSD 980 PRO 1TB SanDisk SSD U110 128GB And since AIDA64 manages connected disk drives based on Windows drive ordering, everytime we connected a new SATA drive to this particular test system the SensorPanel layout had to be adjusted to fit the new drives order. It's a pain in the butt, but so far we couldn't figure out a way to mitigate this issue. Apart from putting external (e.g. USB) drives to the end of the list so at least connecting/disconnecting an external drive wouldn't mess up the order of internal drives.
  2. Fiery
    You're right, it's a bug that was "introduced" with the new "Custom (n states)" gauge type. We've fixed it, as well as added a 3rd option to recognize the gauge index in the filenames, when the index is preceded with a space character.
  3. Fiery
    The total number of sensor slots are over 3000 (!) by now, so adding 10 more doesn't really affect overall performance of the rendering engine or the configuration window behavior.
  4. Fiery
    It was never possible to select images using the filename convention you mentioned. When you selected exactly 16 files with the old "Custom (16 states)" gauge type, then the filenames were not checked for the gauge index, and it works the same now too with the "Custom (16 states)" gauge type. With the "Custom (n states)" gauge type you need to use dash or underscore character before the gauge index in the filename. If you want, we can add a 3rd option with space character before the gauge index as well.
  5. Fiery
    Thank you! This is a new Astral video card variant that AIDA64 doesn't recognize just yet. Please let us know the full model ID of your video card, e.g. ROG-ASTRAL-RTX5090-32G-GAMING.
  6. Fiery
    Awesome Thank you for your feedback!
  7. Fiery
    Make sure to upgrade to the latest beta version of AIDA64 Extreme available at: https://www.aida64.com/downloads/latesta64xebeta After upgrading to this new version, make sure to restart Windows to finalize the upgrade. If it still doesn't work, then in AIDA64 please press Ctrl+D --> Video Debug --> nVIDIA SMBus Dump. Copy-paste the full results into this topic, or attach the results as a TXT file to your post. Thanks, Fiery
  8. Fiery
    Thank you Your feedback is truly valuable and a great motivation to keep elevating the SensorPanel feature to new heights 🚀
  9. Fiery
    Thank you! Now we've found the culprit Do you know what the device "Covecube Virtual Disk" belongs to?
  10. Fiery
    Custom color renaming and deletion are comin' up in the next AIDA64 beta build Till then, please stress-test the color picker dialog to make sure everything's a-okay with it. And don't be shy to post any new ideas or suggestions about it.
  11. Fiery
    So now I gotta kill you both with @Surjeet 😂 The following new items are comin' up in the next beta build hour (1-12) hour (0-23) minute second
  12. Fiery
    @Surjeet Thank you for guys for your feedback. We'll add a rename and delete option to the right-click context menu of the custom color patches. IMHO it's best to have them there rather than on the 3 dots button.
  13. Fiery
    Thank you I know it's not everything one can imagine for date customizations, but hopefully a good start.
  14. Fiery
    Thank you, we've added your monitor to the latest AIDA64 beta update: https://www.aida64.com/downloads/latesta64xebeta
  15. Fiery
    @Surjeet @BHSY @JariKoi @COSTAJUNIOR @Loyd In the latest AIDA64 beta build we've implemented the finalized color picker all across the UI: https://www.aida64.com/downloads/latesta64xebeta When configuring a SensorPanel item the new right-click context menu to allow you to pick a custom color quick & easy is also available now.
  16. Fiery
    We've implemented the requested feature in the latest AIDA64 beta update: https://www.aida64.com/downloads/latesta64xebeta
  17. Fiery
    We've implemented the requested feature in the latest AIDA64 beta update: https://www.aida64.com/downloads/latesta64xebeta
  18. Fiery
    @rinaldop @BHSY @JariKoi @Garageman @COSTAJUNIOR In the latest AIDA64 beta updated we've added a few new sensor items to provide more flexibility for date representation on the SensorPanel: https://www.aida64.com/downloads/latesta64xebeta The new items are: year month (1 to 12) month name day of month (1 to 31) day of week (1 to 7) day of week Name week of year (1 to 52)
  19. Fiery
    Please send us an updated SMART Dump using the latest AIDA64 beta build: https://www.aida64.com/downloads/latesta64xebeta In this build we've extended that dump to include more debug information. It will enable us to find the exact point in the code where the issue occurs.
  20. Fiery
    Thank you for your feedback. Please note that on many devices the standard Android Battery API is inadequately implemented, and fails to provide proper charge counter information for the battery. If you want, you can hide the incorrect charge counter information from the Battery page by unchecking the charge counter option in the AIDA64 Settings.
  21. Fiery
    We've tested it, and the screen never goes blank while the system is locked until the point the system goes to sleep. Then -- since AIDA64 detects when the computer goes to sleep and also when resumes from sleep -- AIDA64 blanks the screen before the computer goes to sleep. Once the computer resumes from sleep, the screen starts working again.
  22. Fiery
    How do you connect that screen to your motherboard? Is it connected via USB? If yes, then in AIDA64 please press Ctrl+D --> System Debug --> USB Dump. Copy-paste the full results into this topic, or attach the results as a TXT file to your post.
  23. Fiery
    Please try it with the latest beta version of AIDA64: https://forums.aida64.com/topic/18367-the-next-generation-aida64-is-around-the-corner/
  24. Fiery
    Done And thank you for your feedback.
  25. Fiery
    I'm afraid no, that's not supported by the standard Windows fonts AIDA64 uses.
×
×
  • Create New...