Jump to content

Fiery

Administrators
 View Profile  See their activity

  • Posts

    12228

  • Joined

  • Last visited

  • Days Won

    538

 Content Type 

Everything posted by Fiery

  1. Fiery
    We've implemented support for Turing (Turzx) LCD devices. Let's continue discussing Turing displays in their own topic:
  2. Fiery
    @MJP @Damster @thehinac @fyrewyre @petrovv111 @Pepo @cyablo @Naudnaud @sherror @remekra @FiX @rydernword @Mrkillerhomer_xD @RaM @Slayver @ForumWT @Citywolf @ThomasK @KiKoMaSo @AndersDuda @Ultim8um @tibcsi0407 We've implemented support for Turing (Turzx) LCD devices. Let's continue discussing Turing displays in their own topic:
  3. Fiery
    We've implemented support for Turing (Turzx) LCD devices. Let's continue discussing Turing displays in their own topic:
  4. Fiery
    We've added support for Turing (Turzx) displays. It works with the following models: - Turing 2.1-inch (480x480 pixels) - Turing 3.5-inch (480x320 pixels) - Turing 5-inch (800x480 pixels) - Turing 7-inch (1024x600 pixels) - Turing 8.8-inch (1920x480 pixels) You can enable the LCD device from AIDA64 / Preferences / Hardware Monitoring / LCD / Turing. You can check it out in the latest AIDA64 beta build at: https://www.aida64.com/downloads/latesta64xebeta Please let us know if you find any difficulties enabling or using this new feature. Also let us know if you've got another kind of LCD device that is currently unsupported by AIDA64. Regards, Fiery
  5. Fiery
    Thank you! Please check the latest AIDA64 beta build too: https://www.aida64.com/downloads/latesta64xebeta I hope it works properly now
  6. Fiery
    Easter Sale is only for customers who have their licenses already expired, so may be up for a renew deal
  7. Fiery
    We will fix that it in the next AIDA64 beta update.
  8. Fiery
    Please upgrade to the latest beta version of AIDA64 Extreme available at: https://www.aida64.com/downloads/latesta64xebeta Let me know if it helps.
  9. Fiery
    Thank you! We've cleaned up the SPD timing levels and correct the clock frequencies for DDR5 modules in the latest AIDA64 beta build: https://www.aida64.com/downloads/latesta64xebeta Let me know how it works.
  10. Fiery
    Does the UEFI Setup (BIOS) and CPU-Z show the clock frequency of your EXPO profile as 3000 or 3003 MHz? I assume AIDA64 is more precise in calculating the clock frequency based on the best (most ideal) latency value encoded in EXPO, that's why it shows slightly higher clock frequency. But, when you calculate latency timings using 3003 MHz, worse values may come out in the end compared to if you based your calculations on 3000 MHz.
  11. Fiery
    That happens because for some reason it's very slow to communicate with the BeadaPanel display. I'd try using a different cable. If that doesn't help, a different USB port on your computer. If that doesn't help, try to update the firmware of the BeadaPanel.
  12. Fiery
    Thank you!
  13. Fiery
    We've replaced his latest version with your fixed version, so it's all fixed now
  14. Fiery
    We appreciate your attention to potential issues in the language module. In case your fixes are based on the latest beta, then we can join the 2 projects together. I just wanted to avoid you guys separately going on translating left and right, and then it would be impossible for us to come up with a single language module that we distribute as part of AIDA64.
  15. Fiery

    Access Violation

    Fiery replied to IndyMX's topic in Bug reports

    Please contact our Sales Department and ask for a refund: https://www.aida64.com/support/contactform
  16. Fiery
    Please note that in order to detect the missing details, the camera ID information had to be previously encoded into the Android profile of the device. When the manufacturer of the device (in your case Samsung) didn't encode the info there, then sysinfo apps cannot read or detect it.
  17. Fiery
    Awesome, thank you!
  18. Fiery
    Thank you, but the language module was already updated in the latest beta. It's maintained by another AIDA64 fan.
  19. Fiery

    Access Violation

    Fiery replied to IndyMX's topic in Bug reports

    That's fair. Thank you for giving our software a chance though.
  20. Fiery
    Can you please explain the steps you perform to import the .sensorpanel file of your choosing?
  21. Fiery
    Please let us know how to implement touch support for your new generation displays. For Matrix Orbital EVE displays we use touch facility to scroll between LCD pages. When the user touches the left 25% of the screen, AIDA64 switches to the previous LCD page; and when he/she touches the right 25% of the screen, AIDA64 switches to the next LCD page. It would be great to implement similar functionality for BeadaPanels too.
  22. Fiery

    Access Violation

    Fiery replied to IndyMX's topic in Bug reports

    I'm afraid the issue you're experiencing is too generic, so it would take a lot of efforts on your part to dig down deeper, e.g. disable various modules of AIDA64 to try to pinpoint the reason of the error message. If you're up for it, we can go down that path, but I still cannot guarantee that we could find the bug that way So in case you have a sour taste in your mouth about the $$ investment, then perhaps the best way for you is to get a refund and find another solution.
  23. Fiery
    Thank you for your kind words.
  24. Fiery
    I'd do at least a few hours. Even better if you could let it run through the night.
  25. Fiery
    We're working on it. Please note that what seems like a single display is actually a large family of displays with at least 5 different communication protocols. So in order to support all Turing/Turzx displays, we need to do a lot of research and development.
×
×
  • Create New...