Jump to content

Fiery

Administrators
 View Profile  See their activity

  • Posts

    12444

  • Joined

  • Last visited

  • Days Won

    554

 Content Type 

Everything posted by Fiery

  1. Fiery
    @Surjeet We've fixed both issues in the latest beta version of AIDA64 Extreme available at: https://www.aida64.com/downloads/latesta64xebeta
  2. 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.
  3. 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
  4. 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.
  5. 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.
  6. Fiery
    Have you tried to use pinning? (AIDA64 / Preferences / Hardware Monitoring / SensorPanel / Pin SensorPanel to monitor)
  7. 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/
  8. 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:
  9. 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.
  10. 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
  11. 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
  12. Fiery
    I've sent you a private message about this
  13. 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.
  14. Fiery
    Thank you for your feedback'
  15. 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
  16. Fiery
    Even if you only alter the first state by selecting a single file, the filename still gets cut?
  17. Fiery
    Do you select the 16 states (in your first example) in a single round by selecting 16 files in the file open dialog? We've tried that but couldn't reproduce the bug As for the state icon, that is due to a limitation of the new compiler. We had to remove it to avoid visual issues to occur. We'll try to find a way to put it back or find another way to indicate the SensorPanel item type (e.g. gauge) as well as the sensor type (e.g. temperature) in the same chart cell.
  18. Fiery
    Awesome 🤘
  19. Fiery
    We're moving at a high pace with resolving the bugs of v7.99, so you can expect the fixed build in a few days
  20. Fiery
    Thank you, we will fix the issue in the next AIDA64 beta update. Please note that AIDA64 Shared Memory has switched from ANSI to Unicode encoding, so you will need to adjust your shared memory buffer reading code accordingly. You can detect if the shared memory buffer is Unicode encoded by checking the 2nd byte of the buffer: if it's a zero byte (0x00), it means you're dealing with a Unicode shared memory buffer.
  21. Fiery
    @thomwithah We've implemented rotation support for Asus ROG AIO screens in the latest beta update of AIDA64: https://www.aida64.com/downloads/latesta64xebeta Please note that this is already a beta build of the next-generation AIDA64. Learn more about it at: https://forums.aida64.com/topic/18367-the-next-generation-aida64-is-around-the-corner/
  22. Fiery
    We've implemented rotation support for Asus ROG AIO screens in the latest beta update of AIDA64: https://www.aida64.com/downloads/latesta64xebeta Please note that this is already a beta build of the next-generation AIDA64. Learn more about it at:
  23. Fiery
    @Playkappa @Asryan @Schoen @Dashinator @Eliasa We've implemented rotation support for Asus ROG AIO screens in the latest beta update of AIDA64: https://www.aida64.com/downloads/latesta64xebeta Please note that this is already a beta build of the next-generation AIDA64. Learn more about it at:
  24. Fiery
    Here it is: https://www.aida64.com/downloads/latesta64xebeta Make sure to backup your existing SensorPanel layout before pressing right-click on the SensorPanel --> Scale --> Scale all items up by 150% After the scaling some items may still be a pixel off here and there due to rounding.
  25. Fiery
    We can start with a basic HEX code input panel and gradually improve it to fulfill all your needs. @BHSY @COSTAJUNIOR @JariKoi Guys, please chime in: if we started to design a brand new colour picker dialog, what would you like to see on it? Which colour picker dialog do you find ideal to use? (e.g. the one of MS Word, MS Paint, etc)
×
×
  • Create New...