Jump to content

Fiery

Administrators
 View Profile  See their activity

  • Posts

    11959

  • Joined

  • Last visited

  • Days Won

    520

 Content Type 

Everything posted by Fiery

  1. Fiery
    Thank you for your feedback! We keep pushing hard to polish out the remaining issues in the next-generation AIDA64 beta channel.
  2. Fiery
    In your particular case the advantage of using higher than 100% resolution for your images would be that the rendered SensorPanel would look sharp on your 4K main monitor (with 150% display scale) as well as your small secondary display. Of course if you never wanted to use your layout on a high-DPI screen and/or you never wanted to share your layout with anyone, having blurry images on a high-DPI screen may not be of an issue.
  3. Fiery
    You can create any still images and gauge state images at any pixel dimensions, it's completely up to you. But, if you wanna have for example a 288x288 pixel gauge at 100% display scale setting, in order to support high-DPI screens it's recommended to use at least 2x resolution images. So in this particular example a 2x resolution image you should use would have a resolution of 576x576 pixels. That means your layout would look great up to 200% display scaling which is what the vast majority of people use today. In other words, rarely anyone goes above 200% display scale today. However, since 5K, 6K and 8K screens are about to become more affordable and so more popular, shooting for 3x or even 4x resolution is not a bad practice either if you wanna future-proof your SensorPanel layouts.
  4. Fiery
    I haven't found you in customer database. It _may_ mean that you purchased a license from an illegitimate store that sells counterfeit AIDA64 product keys. Please send me your AIDA64 product key in private message.
  5. 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. Let me know if it helps.
  6. Fiery
    Thank you! Funnily enough, none of the thermal readings correspond to the CPU temperature So we will simply remove it. You can focus on the CPU Diode temperature reading that is directly read from the CPU itself.
  7. Fiery
    Please check the latest beta version of AIDA64 too: https://www.aida64.com/downloads/latesta64xebeta
  8. Fiery
    Thank you for your feedback!
  9. Fiery
    Thank you for your feedback!
  10. 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.
  11. Fiery
    Thank you for your feedback! I've responded in the HEX code topic too.
  12. Fiery
    @Surjeet @BHSY @COSTAJUNIOR @JariKoi Thank you for your input. Soon we will get to work
  13. 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.
  14. Fiery
    Please try to turn it off. The next-generation AIDA64 should position the SensorPanel correctly even without pinning.
  15. Fiery
    Here's the fix: https://www.aida64.com/downloads/latesta64xebeta
  16. 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.
  17. Fiery
    Thank you! Please upgrade to the latest beta version of AIDA64 Extreme available at: https://www.aida64.com/downloads/latesta64xebeta
  18. Fiery
    @Surjeet We've fixed both issues in the latest beta version of AIDA64 Extreme available at: https://www.aida64.com/downloads/latesta64xebeta
  19. 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.
  20. 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
  21. 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.
  22. 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.
  23. Fiery
    Have you tried to use pinning? (AIDA64 / Preferences / Hardware Monitoring / SensorPanel / Pin SensorPanel to monitor)
  24. 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/
  25. 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:
×
×
  • Create New...