Jump to content

Fiery

Administrators
 View Profile  See their activity

  • Posts

    12417

  • Joined

  • Last visited

  • Days Won

    551

 Content Type 

Everything posted by Fiery

  1. Fiery
    Could be that too...
  2. Fiery
    It's more complicated than that. The OpenCL layer is multiple files plus Registry entries, and everything has to be correctly configured for the whole chain to work properly. Try to do a complete reinstall of ForceWare drivers to make it work.
  3. Fiery
    Thank you! That's a screen that we've never seen before. It's currently not supported by AIDA64, and unless we can figure out how it works, I cannot make any promises about supporting it at this time.
  4. Fiery
    In case the screen appears as a secondary monitor under Windows, then you can simply use the SensorPanel feature of AIDA64. Otherwise, please send us an USB Dump to see what the screen is all about. 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
  5. Fiery
    Where did you acquire those screens from? Please post an USB Dump of both screens: 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
  6. Fiery
    Please send me the EDID block of the system in email. If you have no tools to dump the EDID or don't know my email address, then please drop me a private message.
  7. Fiery
    No, it's not possible to use skins for the OSD Panel. If you need deep customizations, just use the SensorPanel module of AIDA64 instead of the more basic (but much easier to use) OSD Panel.
  8. Fiery
    Thank you! We've checked Lian Li's website, and they mention that it is possible to use the display as a secondary monitor under Windows. In which case you can simply move the SensorPanel window to that screen and you wouldn't need to use the LCD facility of AIDA64.
  9. Fiery
    Thank you! I'm afraid since it seems almost impossible to acquire the HOF Panel III as a standalone test device, we cannot implement support for it. We'd need a sample in order to analyze how it works.
  10. Fiery
    Thank you! We've fixed the issue in the latest AIDA64 beta update: https://www.aida64.com/downloads/latesta64xebeta
  11. 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.
  12. 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.
  13. 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.
  14. Fiery
    Thank you! We're working on implementing support for the OLED screen of the ROG Azoth keyboard.
  15. Fiery
    Yes, absolutely.
  16. Fiery
    What mobile device do you have? What Android version do you have installed?
  17. 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.
  18. 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 😞
  19. 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.
  20. 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.
  21. 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...
  22. Fiery
    I've sent you a private message about this
  23. 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
  24. 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.
  25. Fiery
    You've got a private message.
×
×
  • Create New...