Jump to content

Fiery

Administrators
 View Profile  See their activity

  • Posts

    12283

  • Joined

  • Last visited

  • Days Won

    541

 Content Type 

Everything posted by Fiery

  1. Fiery
    Thank you! We've fixed the issue in the latest AIDA64 beta update: https://www.aida64.com/downloads/latesta64xebeta
  2. Fiery
    It is available now 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 how it works.
  3. Fiery
    Please 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 how it works.
  4. Fiery
    We've fixed the issue in the latest AIDA64 beta update available at: https://www.aida64.com/downloads/latesta64xebeta Let me know how it works.
  5. Fiery
    Thank you! We're working on implementing support for the OLED screen of the ROG Azoth keyboard.
  6. Fiery
    Yes, absolutely.
  7. Fiery
    What mobile device do you have? What Android version do you have installed?
  8. 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 makes a difference.
  9. Fiery
    The issue you've described only happens on AMD Radeon RX 6000 Series video cards. On such video cards AIDA64 reads GPU information and measures video card related readings exclusively using video driver (AMD Adrenalin) calls. Since there're no direct (low-level) video register accesses performed on those video cards by AIDA64, the issue must happen somewhere inside AMD's domain, ie. in their video driver. What I can suggest you is try the next-generation AIDA64: Maybe the fact that it's a native 64-bit process makes a difference. Other than that, we're stuck: we cannot fix a buggy video driver from our end 😞
  10. Fiery
    Thank you! Please send us an updated USB Dump using the latest AIDA64 beta version: https://www.aida64.com/downloads/latesta64xebeta 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.
  11. Fiery
    Lian Li responded on Discord that they want us to contact them via the contact form on their website. So we did do that -- although there wasn't any appropriate contact form variant to use there. We're waiting for their response.
  12. Fiery
    @Loyd Quite frankly, those screens have messy firmware to begin with. I personally am surprised that it works at all We struggled a lot to make them work with AIDA64 even when only one screen is connected. We will try to tweak it more to make it work better, but it's like doing renovations on a house of cards...
  13. Fiery
    I've sent you a private message about this
  14. Fiery
    Please disconnect the Turzx device (the one that works fine) from your PC. Connect the second, non-branded device to your PC (the one that doesn't work). 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. Thanks, Fiery
  15. Fiery
    Thank you for the screenshots. We've contacted MSI and asked for guidelines on how to measure W_Flow_1. We're waiting for their response.
  16. Fiery
    You've got a private message.
  17. Fiery
    In order to replicate the issue, we'd need a test system with 2 EDID blocks. Do you know how to achieve that?
  18. Fiery
    Can you please post a screenshot of HOF AI Suite where you can upload a bitmap image to the display device? Also, regarding the HOF Panel III device itself: does it come as a standalone device or is it part (module) of another Galax product, like a GeForce video card?
  19. Fiery
    Can you please post a photo of the BIOS Setup where it shows all fan RPM readings as well as the WFlow_1 reading?
  20. Fiery
    Can you put the weather value to the Registry? If you could, then you could use this trick: https://www.aida64.com/user-manual/hardware-monitoring/displaying-custom-values
  21. Fiery
    We currently have no technical information on that panel, so we cannot tell whether it's possible to handle it directly, ie. to send bitmap images to it. Do you know of any software that can do that?
  22. Fiery
    No, but in case you can see a pattern in how the measured values differ to real values, like if they're always 2x or 4x or 8x more than the actual values, then you can use the Correction facility of AIDA64 (in AIDA64 / Preferences / Hardware Monitoring / Correction) to divide down the values.
  23. 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
  24. Fiery
    I've sent you a private message about this
  25. Fiery
    What version of AIDA64 are you using?
×
×
  • Create New...