Jump to content

Fiery

Administrators
 View Profile  See their activity

  • Posts

    11545

  • Joined

  • Last visited

  • Days Won

    489

 Content Type 

Everything posted by Fiery

  1. Fiery
    We've implemented support for the OLED display of SteelSeries Apex 7 and Apex Pro keyboards in the latest AIDA64 beta build: https://www.aida64.com/downloads/latesta64xebeta You can activate it in AIDA64 / main menu / File / Preferences / Hardware Monitoring / LCD / SteelSeries.
  2. Fiery
    We've implemented support for the OLED display of SteelSeries Apex 7 and Apex Pro keyboards in the latest AIDA64 beta build: https://www.aida64.com/downloads/latesta64xebeta You can activate it in AIDA64 / main menu / File / Preferences / Hardware Monitoring / LCD / SteelSeries.
  3. Fiery
    Yes, and thank you for the USB device data. Please check if it works: https://www.aida64.com/downloads/latesta64xebeta You can activate it in AIDA64 / main menu / File / Preferences / Hardware Monitoring / LCD / Art.Lebedev.
  4. Fiery
    We've checked the developers section, and yes, it seems to be relatively easy to implement support for the wide strip of LCD display of the Optimus Popularis keyboard. Am I right in understanding that the keyboard uses a logical drive (like D:\ or E:\) as a virtual disk drive where one can write the LCD data (raw images) onto in order to update the LCD displays of the keyboard? Also, we need to have the USB device IDs for the Optimus Popularis keyboard in order to detect its presence. Please right-click on the bottom status bar of AIDA64 main window --> System Debug --> USB Dump. 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.
  5. Fiery
    Yes, the forum seems to fire notification emails only when your post gets quoted. I've quoted it now, so I hope you get a notification
  6. Fiery
    Thank you. Weird, since we're using the same version but it fails to report the Hardware Monitor values. Maybe you need to have an Asus ROG motherboard along with the AIO cooler to make LiveDash work with all its features?
  7. Fiery
    Since it's not true GPU utilization, we wouldn't want to deal with it.
  8. Fiery
    Thank you, and you're right, we'll update our PCI database accordingly in the next AIDA64 beta update.
  9. Fiery
    Memory module properties are listed on the Motherboard / SPD page in AIDA64. However, in case you don't have memory modules but soldered down BGA memory chips, you can find the memory chip information on the Computer / DMI page in AIDA64, under the Memory Devices group.
  10. Fiery
    Please note that we haven't received a response from Asus so far. We've pinged them again today...
  11. Fiery
    We've analyzed the way Asus Ryuo and Ryujin water coolers handle their built-in OLED screens, and we're afraid of them using their own integrated flash memory to store the image that is uploaded to the device and then gets displayed on the OLED screen. In which case a software like AIDA64 -- one that overwrites the image one to ten times a second -- could very quickly wear out the flash memory of the device and kill the display basically. We're not 100% sure about this, since it's just our theory, but we've asked Asus about it and waiting for their response.
  12. Fiery
    We've checked LiveDash, but somehow our version doesn't have the Hardware Monitor option there in the left menu. What version of LiveDash do you have installed, and where did you download it from?
  13. Fiery
    We'll add it (PMULL) to the CPU page in the next AIDA64 for Android update.
  14. Fiery
    Maybe that's the trick then. To be super quick Great job!
  15. Fiery
    Try to update the BIOS of your motherboard to the latest version and return your CPU to its default settings (no overclock). If that doesn't help, then try to lower the DRAM (memory) frequency.
  16. Fiery
    We'll work on that.
  17. Fiery
    Do you own one?
  18. Fiery
    Such issues could occur on Asus ROG motherboards when a reading comes from the EC (Embedded Controller). Polling for EC registers could collide with background Asus processes/services as well as activities of the BIOS itself. So far we haven't found a 100% reliable way to avoid such collisions
  19. Fiery
    Yes, we've heard about such issues when using SPF devices with Win10, but so far we haven't found a resolution
  20. Fiery
    Indeed, those values do not back the theory of why it takes so much time to update the SensorPanel on your system. Unless of course the SensorPanel rendering itself takes a lot of time in case you have a complex layout.
  21. Fiery
    Do you mean you'd like to add new LCD layout items via a quicker method -- or move existing items to a different place using a quicker method?
  22. Fiery
    Refresh rate is always higher than the configured value, because collecting sensor readings takes time. In your case I suppose it takes 200 to 400 milliseconds to collect all sensor readings. You can verify that by right-clicking on the bottom status bar of AIDA64 main window --> Sensor Debug --> Sensor Profiling Dump. Smooth transition is not supported by the SensorPanel/LCD bars right now.
  23. Fiery
    Try to enable Samsung LCD support in AIDA64 first, and check if the display appears in the Device Manager as an unknown device. When it does, you can install the driver for it.
  24. Fiery
    I'm afraid we cannot do that until we revamp the LCD configuration part of the Preferences panel. Currently there's no room for the LCD options to be quadrupled. Even the four LCD type dropdown lists are a bit of a stretch right now, since it's not explained at all why there are four of them. --- As for the temperature sensor crash, does it crash the whole system or only AIDA64 crashes? What motherboard, CPU and video card(s) do you have in your system, and do you have any external storage devices connected?
  25. Fiery
    Thank you for your feedbacks. 1) About the SPD issue, please post an updated SMBus Dump (Full) dump. 2) As for the crash on the Computer / Sensor page, does it happen in all cases (when you go to the Sensor page), in the same manner?
×
×
  • Create New...