Jump to content

Fiery

Administrators
 View Profile  See their activity

  • Posts

    12354

  • Joined

  • Last visited

  • Days Won

    546

 Content Type 

Everything posted by Fiery

  1. Fiery
    Thank you for your feedback!
  2. Fiery
    Thank you for your feedback!
  3. 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.
  4. Fiery
    Thank you for your feedback! I've responded in the HEX code topic too.
  5. Fiery
    @Surjeet @BHSY @COSTAJUNIOR @JariKoi Thank you for your input. Soon we will get to work
  6. Fiery
    Thank you! Can you please create 2 different ISA Sensor Dumps, one at idle, the other one at load, and also check both the CPU temperature and TSensor temperature reading in IPMI and send those to me as well? Problem is, there're a bunch of thermal readings for your motherboard and it's quite difficult to figure out which is which Here's the list: 10 11 12 13 15 16 1B 20 52 57 65 71 73 75 7C T: 36 36 86 102 104 50 86 36 0 0 255 11 11 36 255 T: 36 36 86 102 104 50 86 36 0 0 255 11 11 36 255 T: 36 36 86 102 104 50 86 36 0 0 255 11 11 36 255 T: 36 36 86 102 104 50 86 36 0 0 255 11 11 36 255 T: 36 36 86 102 104 50 86 36 0 0 255 11 11 36 255 T: 36 36 86 102 104 50 86 36 0 0 255 11 11 36 255 T: 36 36 86 102 104 50 86 36 0 0 255 11 11 36 255 T: 36 36 86 102 104 50 86 36 0 0 255 11 11 36 255 T: 36 36 86 102 104 50 86 36 0 0 255 11 11 36 255 T: 36 36 86 102 104 50 86 36 0 0 255 11 11 36 255 Obviously stuff like zero, 11, 102, 104 and 255 Celsius are bogus readings, but the rest could well be the CPU temperature.
  7. Fiery
    Please try to turn it off. The next-generation AIDA64 should position the SensorPanel correctly even without pinning.
  8. Fiery
    Here's the fix: https://www.aida64.com/downloads/latesta64xebeta
  9. Fiery
    @Bauze We've fixed the issue in the latest beta version of AIDA64 Extreme available at: https://www.aida64.com/downloads/latesta64xebeta Let me know how it works.
  10. Fiery
    Thank you! Please upgrade to the latest beta version of AIDA64 Extreme available at: https://www.aida64.com/downloads/latesta64xebeta
  11. Fiery
    @Surjeet We've fixed both issues in the latest beta version of AIDA64 Extreme available at: https://www.aida64.com/downloads/latesta64xebeta
  12. Fiery
    Thank you! @ill @SKiZZ Make sure to upgrade to the latest beta version of AIDA64 Extreme available at: https://www.aida64.com/downloads/latesta64xebeta Let me know how it works.
  13. Fiery
    In AIDA64 please press Ctrl+D --> Sensor Debug --> USB Dump. Copy-paste the full results into this topic, or attach the results as a TXT file to your post. Thanks, Fiery
  14. Fiery
    BTW, what Razer product do you try to use AIDA64 with? DeathStalker Ultimate keyboard? Do you use any features of the Razer Synapse framework with your Razer hardware? I'm just asking because we haven't found any traces of a 64-bit RzSwitchbladeSDK2.dll 😞 Which means we gotta figure out an alternative method to talk to the Razer LCD. One option may be to sack Razer Synapse 2.0 (which will be deprecated in October this year anyway), install a special driver for the Razer LCD and talk to the device directly. It may work out, but then you'd lose the ability to install and use Razer Synapse.
  15. Fiery
    It's best if you backup your original settings before using scaling. This feature was implemented to ease the migration from the old (v7.xx) AIDA64 to the next-generation AIDA64 (v7.99 and eventually v8.xx). It should be used only once, when you experience the shrinking issue after migrating to the new AIDA64. Once you applied it once, you should be good to go. As for going back to 100%, it cannot work as a scaling-back, since rounding errors would cause one-pixel discrepancies. An undo feature would work of course, but since this is whole scaling thing should be used once -- when you switch from the old to the new AIDA64 --, we aren't keen on investing too much efforts into it.
  16. Fiery
    Have you tried to use pinning? (AIDA64 / Preferences / Hardware Monitoring / SensorPanel / Pin SensorPanel to monitor)
  17. Fiery
    We've just rolled out the first beta build of the next-generation AIDA64 that fixes -- among many other things -- several issues related to how AIDA64 handles mixed DPI monitor setups: https://forums.aida64.com/topic/18367-the-next-generation-aida64-is-around-the-corner/
  18. Fiery
    The latest AIDA64 beta build is already a preview of the next-generation AIDA64 which is a native 64-bit application and so it requires 64-bit DLL modules. It means, in your particular case the new AIDA64 requires the 64-bit variant of RzSwitchbladeSDK2.dll. We will check it out, maybe there's a new trick to be implemented in AIDA64 to find the right (64-bit) RzSwitchbladeSDK2.dll file automatically. Until then, you can try to copy the 64-bit RzSwitchbladeSDK2.dll into the AIDA64 installation folder to make it work. Also, make sure to check this topic:
  19. Fiery
    The scaling feature only scales SensorPanel items but not images. So the image files (BMP, PNG, JPG) you use for either regular images or as custom gauge states will not be altered during the scaling process. The only aspect about images that is altered is the resizing dimensions. But your layout doesn't seem to use resizing for images. In order to make sure your panel is suitable for various DPI settings, you need to use high-resolution images for still images and custom gauge states and use the resizing facility. As an example: if you need a 250x300 pixel sized custom gauge, try to use a set of gauge state images sized at 200% of that, so 500x600 pixels each. Then, after placing the images on your layout, use the Resize parameter for the gauge and enter 250x300 there. If you'd like to see an example of how resizing high-resolution images work for both still images and custom gauges, check the file called sensorpanel_default.spzip in the AIDA64 installation folder.
  20. Fiery
    In AIDA64 please press Ctrl+D --> Sensor Debug --> ISA Sensor Dump. Copy-paste the full results into this topic, or attach the results as a TXT file to your post. Thanks, Fiery
  21. Fiery
    With the latest beta build we've migrated to a new development channel: In your case the issue must be that AIDA64 cannot find a 64-bit aidardsp.dll module to load. I'm not even sure if one exists at all
  22. Fiery
    I've sent you a private message about this
  23. Fiery
    Funnily enough, this one seems to be a compiler bug that we cannot fix on our end. Apparently there's a 78 character limitation on the caption of the very first item in popup menus. What we can do is add a header to the popup menu as a workaround. We will also report the compiler bug to Embarcadero.
  24. Fiery
    Thank you for your feedback'
  25. Fiery
    We could finally reproduce the bug. It seems to be only a visual issue. In other words, even though the filename looks cut, the actual filename is properly used by the custom gauge. We will still fix the issue of course
×
×
  • Create New...