Jump to content

Fiery

Administrators
 View Profile  See their activity

  • Posts

    12364

  • Joined

  • Last visited

  • Days Won

    548

 Content Type 

Everything posted by Fiery

  1. Fiery
    @manuuuu400 We've implemented the requested new option (Decimal digits for flow sensors) in the latest AIDA64 beta update available at: https://www.aida64.com/downloads/latesta64xebeta
  2. Fiery
    It can, but then you need to place the 64-bit sens_oal.dll file to the installation folder of AIDA64 v7.99, and rename the file to OpenAL32.dll. I've just tried it and it works fine.
  3. Fiery
    Yes, you can evaluate AIDA64 v8.00 for 30 days in mid-September. Until then you can check AIDA64 v7.99 beta which is a preview of v8.00: https://www.aida64.com/downloads/latesta64xebeta
  4. Fiery
    By default Creative's distribution of OpenAL incorrectly places a 32-bit library (DLL file) named OpenAL32.dll into the \Windows\System32 folder of 64-bit Windows installations. Installers are supposed to place 64-bit DLL files in that folder of 64-bit Windows systems. Since it uses a 64-bit main binary, AIDA64 v7.99 cannot load 32-bit DLLs and so the issue you're experiencing is normal. You need to find a 64-bit OpenAL library to replace the incorrect OpenAL32.dll file. You can put the 64-bit OpenAL DLL file to either the installation folder of AIDA64 v7.99 or to the \Windows\System32 folder.
  5. Fiery
    Can you please submit a crash report when the crash occurs? That way you'd enable us to analyze where the crash occurs inside AIDA64 for Android.
  6. Fiery
    The status of such readings is still the same.
  7. Fiery
    It means your Elgato device is not yet supported. Please let us know what model do you have, and also 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
  8. Fiery
    We've talked to MSI but apparently our code and the formula we use are correct. It's a very strange anomaly. Can you please send us two ISA Sensor Dumps? One at idle and one with the CPU under load. Please indicate the rough pump RPM for both states as well. We will check the register dumps for the raw readings for the pump to see the base values for the calculations we use. To create such dumps, 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
  9. Fiery
    Thank you for your feedback!
  10. Fiery
    You can enable Elgato LCD support in AIDA64 / Preferences / Hardware Monitoring / LCD / Elgato.
  11. Fiery
    We will definitely have exciting news coming up in September about all of that
  12. Fiery
    We will of course make sure to implement full support for the new Turing 8-inch screens as well. And quickly 🙂
  13. Fiery
    It can only be remedied in case Turing provides a firmware update for their screens that would fix this issue. But I don't think the firmware can be updated on Turing screens at all
  14. Fiery
    The firmware of the latest Turing screens is quite peculiar when it comes to how they update frames. Once the size of the image toe be sent to the display becomes too large, AIDA64 has to cut it in half to make sure the firmware can "digest" the data. So as your layout becomes more complex, the rendered image may cross over the threshold and would mean that it sadly has to be sliced up to make it work with the firmware.
  15. Fiery
    Thank you for your feedback, it looks awesome! Unfortunately it's not possible currently to use different rotation setting for different Turing screens. We will unlock that possibility in a future update to AIDA64.
  16. Fiery
    Thank you! Please check the latest AIDA64 beta update on your 9.2-inch Turing screen: https://www.aida64.com/downloads/latesta64xebeta
  17. Fiery
    I'm not sure why that would be useful. Can you please explain the benefits or usage scenario of having the full list of timings?
  18. Fiery
    The title of the original Aliexpress listing is deeply misleading...
  19. Fiery
    Yes, we've removed the redundand entries. So in the latest version we only show the best timing step for any given clock frequency setting.
  20. Fiery
    It's under NDA, so I cannot share
  21. Fiery
    Quite frankly we use the formula provided by MSI, but it looks strange so it may not be how we've interpreted it the first time we've implemented it. That's why we've asked them for clarification and a more detailed explanation on the formula they provided. We will make sure to fix it in case it requires adjustment.
  22. Fiery
    Thank you for your detailed feedback and test runs! We've contacted MSI to clarify and also to assist us in resolving this issue. When comparing the measured values, please note that the UEFI Setup uses a different measurement unit than AIDA64. The UEFI Setup shows the water flow reading in L/M (Litres per Minute) while AIDA64 uses the LPH unit (Litres per Hour). So there should be a 60x difference (60x ratio) between the two values.
  23. Fiery
    Could be that too...
  24. 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.
  25. 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.
×
×
  • Create New...