Fiery

Administrators
  • Content count

    6274
  • Joined

  • Last visited

  • Days Won

    184

Fiery last won the day on February 14

Fiery had the most liked content!

Community Reputation

242 Excellent

1 Follower

About Fiery

  • Rank
    AIDA64 Developer
  • Birthday

Contact Methods

  • Website URL
    http://www.aida64.com

Profile Information

  • Gender
    Male
  • Location
    Budapest, Hungary
  • Interests
    AIDA64 :)
  1. Is the video card fan spinning when you try to add it?
  2. Thank you for your feedback
  3. Thank you. That's rather weird then. Please right-click on the bottom status bar of AIDA64 main window --> CPU Debug --> CPUID & MSR Dump. Copy-paste the full results into this topic, or attach the results as a TXT file to your post.
  4. Since they both will be displayed on the Sensor page, I don't think we need to replace anything Whichever you don't like, just ignore it
  5. What version of BSPlayer are you using? BTW, we've checked it with BSPlayer 2.70 Free, and it displays the media title properly in AIDA64.
  6. That look odd. Do you happen to have Low-level PCI bus operations or Low-level SMBus operations or Low-level sensor operations disabled in AIDA64 / main menu / File / Preferences / Stability?
  7. Processes: We of course have the code to enumerate running processes. I just find it quite complicated to configure it that way. E.g. if you want to configure it for a particular game, you need to launch the game, go back to AIDA64, find the process in the list of processes, etc. To do that with all the games and applications you use on your computer is quite a task. Not to mention you need to do that in the future with newly installed games/applications. Let's just say it's not a feature we would see implemented in AIDA64, unless there's a very easy way of detecting the computer state. Duty cycle: Fan duty cycle is quite misleading, since when the duty cycle is configured and then detected at e.g. 30%, it doesn't mean the fan is actually spinning. Focusing on the RPM is a lot better, since that way you can be aware of a stopped or clogged fan. VLC: I'm sorry, but both HTTP and Telnet protocol is way too overkill to be used in the AIDA64 hardware monitoring module. And DBus is not supported by Windows.
  8. It seems on your particular motherboard model the Vcore reading has to be multiplied by 1.2. We'll implement that in the next AIDA64 beta update
  9. Thank you for your feedback, I'm glad you like the way we steer the development of AIDA64
  10. Those temperatures are reported by AIDA64 too.
  11. There seems to be no classic sensor chips in your system, or they're connected to an IPMI BMC. Have you tried to check the Computer / IPMI page? Maybe sensor values are reported via IPMI on your system. Regards, Fiery
  12. Thank you for the feedback. The limit has to be fixed, so it will be increased from 10 to 25 in the next AIDA64 beta update
  13. 1) Smooth transitions and animations are not supported because of the limitations of the LCD rendering engine. It's really not designed to handle such effects and it doesn't support complex associations between slides/pages. 2) It'd be quite difficult to automatically detect which type of usage is currently going on on the computer And due to multi-tasking, detecting the starting or stopping of certain processes could be misleading too. 2) VLC is not supported at this time. Do you have a sample code that can take such details from a running VLC process? BTW, Winamp should be able to play movies too -- although it's not the ideal tool for the job 3) It's because fan duty cycle is a misleading value that shall be ignored. You should rather focus on the fan RPM readings. The GPU duty cycle was implemented only because certain video cards only support duty cycle detection, and doesn't support fan RPM measurement. For most motherboard fans both are always supported, so we only deal with the RPM measurement for motherboards. 4) Please send me your updated French language module in email, and I'll take a look into those changes Thank you!
  14. Thank you, we'll fix that issue in the next AIDA64 beta update