Jump to content

Fiery

Administrators
  • Posts

    11334
  • Joined

  • Last visited

  • Days Won

    476

Everything posted by Fiery

  1. The trick is that you must use such fonts that are available in both Windows and in the Chrome version running on your mobile device. I'm not sure if anyone manages a list of those fonts, so your best method to find out is to just play around and try different, popular fonts and note down which one works and which one got replaced by a different font in Chrome.
  2. What version of Aquasuite and Windows 10 are you using? I assume you're using the latest AIDA64 version of 6.32.
  3. AIDA64 doesn't specifically pull data out of Aquasuite, but rather polls information, readings and measurements from Aquaero and other devices made by AquaComputer.
  4. I don't think you can do that, since the display hasn't got its own USB connection
  5. I've replied you in your separate topic.
  6. As for the missing 3rd GPU fan, please right-click on the bottom status bar of AIDA64 main window --> Video Debug -->nVIDIA GPU Registers. Copy-paste the full results into this topic, or attach the results as a TXT file to your post. You may need to enable status bar in AIDA64 / main menu / View first. Also right-click on the bottom status bar of AIDA64 main window --> Video Debug --> nVIDIA SMBus Dump. Copy-paste the full results into this topic, or attach the results as a TXT file to your post. We're kinda lost about the memory/resource error, since we cannot find the place in AIDA64 where that occurs, and it's extremely difficult to find it when you don't have the system on hand (here in our labs). Let's deal with the missing 3rd GPU fan issue first, and we'll see where we can go from there. BTW, please confirm that in either EVGA's Precision software or GPU-Z you can see the 3rd GPU fan measured properly. Thanks, Fiery
  7. Can you please check how RPM and duty cycle (%) values look like when the video card is under load? I'm wondering if you can achieve a 100% duty cycle for the first two fans and then it would be very interesting to know what the GPU3 fan duty cycle indicates then. We may use an incorrect conversion formula for GPU3 fan duty cycle, but not sure if it's a matter of wrong ratio or something else.
  8. Fiery

    Image png error

    It's not quite clear to us what causes the PNG issues. Our best guess is that certain image editors place some big data into the PNG file that causes the crash in our code. BTW, I've managed to place the image you've attached to your post on a SensorPanel. Probably it's because the image got converted by our forum engine. Try to load the PNG file into another image editor, maybe PAINT.EXE or a free image editor of your choice, and save it to a new PNG file to convert it and get rid of the problem in the file.
  9. Please right-click on the bottom status bar of AIDA64 main window --> Video Debug --> ATI GPU Registers. Copy-paste the full results into this topic, or attach the results as a TXT file to your post. You may need to enable status bar in AIDA64 / main menu / View first. Thanks, Fiery
  10. That's a difficult issue, since other software and tools would stick to using a dot for decimal separator, regardless of the current regional setting. Probably a new option in the Preferences is the way to go, although when it's possible, we prefer to avoid that. A dropdown list of "Windows Default / Dot / Comma" would be suitable, what do you think?
  11. When we came up with the AES benchmark, hardware acceleration wasn't available for it yet. Same thing with the SHA1: hardware acceleration was introduced after we designed and introduced that benchmark method too. Now it's the same story with SHA3: currently there's no hardware acceleration (at least not in x86 CPUs), but it's coming soon. As for the longevity and relevance of the AES benchmark, we're watching the market and will make a decision on its fate when the right time comes.
  12. 1) No, such frame stats cannot be measured or displayed by AIDA64. 2) Fraps and RTSS are supported by AIDA64, albeit recently RTSS seems to have gone incompatible with AIDA64 -- we're investigating that part.
  13. You can adjust the SensorPanel resolution in AIDA64 / main menu / File / Preferences / Hardware Monitoring / SensorPanel. Please note that SensorPanel layouts are designed for a specific resolution, and when you import it and want to use a different resolution, you need to adjust the layout accordingly.
  14. We've picked SHA3 over SHA2 exactly because it has no specific CPU acceleration.
  15. That one uses HDMI connector and so it can be plugged into your PC and will become a secondary monitor. In which case you can use the AIDA64 SensorPanel module and move the SensorPanel to your secondary monitor.
  16. Most picture frames do not feature a facility to pass a bitmap image via the USB connection. Let me know if you're sure that your device supports such a facility.
  17. It's a difficult question. Are you looking for an alphanumeric (character) display or a fancier, graphical screen?
  18. Thank you, we'll check LCD Smartie. For us driver download wasn't done automatically under Win10, but the Windows Update facility offered an optional driver update "wch.cn" for the device and that worked out. Where did you get USB_LCD.DLL (LCD Smartie plugin) from?
  19. AFAIK fake device manufacturers use such tricks that are deeply embedded into the firmware of the device, including not just proofed files but also patched Android API calls. I wouldn't spend too much time on trying to reverse this activity.
  20. What output of AIDA64 do you find difficult to be post-processed? Are you trying to load e.g. a CSV log file generated by AIDA64 into Excel perhaps?
  21. Thank you! I'm afraid we cannot find the relevant register that would correspond to the 3rd fan of your video card
  22. Please right-click on the bottom status bar of AIDA64 main window --> Video Debug --> nVIDIA GPU Registers. Copy-paste the full results into this topic, or attach the results as a TXT file to your post. You may need to enable status bar in AIDA64 / main menu / View first. Also right-click on the bottom status bar of AIDA64 main window --> Video Debug --> nVIDIA SMBus Dump. Copy-paste the full results into this topic, or attach the results as a TXT file to your post. Make sure to use AIDA64 v6.32 (latest version). Thanks, Fiery
  23. I'm afraid for most PC's it's not possible to meausure overall system power consumption in a reliable and accurate way.
  24. That's a very interesting and peculiar anomaly. My best guess is that the whole process takes more time to complete than what's expected from the average throughput because of the overhead of the graph drawing, time measurement, etc. If you push a right mouse click on the Save button, you can save all datapoints to a CSV or TSV file
  25. It's very difficult to find out the protocol details (if there's a proper protocol) without help from the person who's responsible for developing the firmware of the device. Have you tried to use your display with other software like LCDSmartie?
×
×
  • Create New...