Jump to content

Fiery

Administrators
 View Profile  See their activity

  • Posts

    12478

  • Joined

  • Last visited

  • Days Won

    558

 Content Type 

Everything posted by Fiery

  1. Fiery
    That looks normal. I suspect the slow update rate is because WigiDash software does the updating of the display too slowly. Please note that unlike with most LCD protocols, WigiDash displays are updated through shared memory interface with their WigiDash software. So the actual communication with the display hardware is not done by AIDA64, but by WigiDash software.
  2. Fiery
    I've sent you a private message about this.
  3. Fiery
    It is sadly due to a firmware limitation of Turzx/Turing screens: when the layout you build is too complex, the rendered image can only be transferred in 2 chunks (2 steps). That causes flashing/blinking effect. If it bothers you too much, try to come up with a less complex layout, for example by using a simpler background image.
  4. Fiery
    No, since as far as we know, it's not possible to measure the actual GPU utilization on Intel GPUs.
  5. Fiery
    It depends on how the standard Android Battery API is implemented on your phone.
  6. Fiery
    In order to have support for your GPU, you need to upgrade to the latest AIDA64 version of 8.20: https://www.aida64.com/downloads/latesta64xe
  7. Fiery
    Thank you for your feedback!
  8. Fiery
    Yes, but the serial numbers there are detected using a different driver call.
  9. Fiery
    Yes, somehow the new native NVMe driver doesn't provide serial number at all, or provides a different serial number than the drive has got. We're not sure why that is, our best guess is that there's a driver bug that Microsoft has to fix up.
  10. Fiery
    Thank you for your feedback! We will fix the mentioned issue in the next AIDA64 beta update.
  11. Fiery
    @Benni231990 @FatBoyNL @Tomorrow @Miroslav Tuhársky We've implemented native NVMe support in the latest AIDA64 beta update available at: https://www.aida64.com/downloads/latesta64xebeta
  12. Fiery
    We've implemented native NVMe support in the latest AIDA64 beta update available at: https://www.aida64.com/downloads/latesta64xebeta
  13. Fiery
    @Cybrdude We've implemented native NVMe support in the latest AIDA64 beta update available at: https://www.aida64.com/downloads/latesta64xebeta
  14. Fiery
    A hibát javítottuk a legújabb AIDA64 béta kiadásban: https://www.aida64.com/downloads/latesta64xebeta
  15. Fiery
    We've implemented support for WeAct displays in the latest AIDA64 beta update available at: https://www.aida64.com/downloads/latesta64xebeta Let us know how it works.
  16. Fiery
    The above mentioned new AIDA64 beta update is now available for download: https://www.aida64.com/downloads/latesta64xebeta
  17. Fiery
    That screen in USB mode is not supported by AIDA64 yet. We do have plans to implement support for it later this year though.
  18. Fiery
    Such issues are usually caused by a mixup in the OpenCL layer of Windows. A full video driver cleanup + reinstall should solve it.
  19. Fiery
    Are you sure the fan is not stopped? Does it still show zero RPM even when the CPU is under heavy load?
  20. Fiery
    I suppose the polling of all the sensors available in your system plus rendering the SensorPanel layout consumes so much CPU cycles on your system that it elevates the idle CPU clock too much and so makes your CPU run hotter.
  21. Fiery
    We've ordered a device and we'll see if we can implement support for it.
  22. Fiery
    Does the GPU hotspot reading fluctuates between meaningful values and bogus (meaningless) readings? That could explain that behavior.
  23. Fiery
    Thank you! We're working on it... I will let you know in this topic once we implemented support for your PSU in AIDA64.
  24. Fiery
    Thank you, we will add the missing GPU sensor readings in the next AIDA64 beta update.
  25. Fiery
    Thank you, we've ordered one. Once it arrives, we'll jump on it to see if we can implement support for it in AIDA64.
×
×
  • Create New...