Jump to content

schrutic

Members
  • Posts

    20
  • Joined

  • Last visited

Posts posted by schrutic

  1. 4 minutes ago, Fiery said:

    You can see a more precise and dynamically updated BCLK reading on the Computer / Overclock page.

    You can adjust the number of decimal digits for clock frequency readings at AIDA64 / main menu / File / Preferences / Hardware Monitoring / Decimal digits for clock speeds.

    Well don't I feel silly. That worked perfectly. Thanks @Fiery!

  2. Hey there AIDA64 Team!

    Is there anyway to increase the precision for the Bus Clock?

    I first noticed this while using the RemoteSensor panel with CPU FSB simple sensor item. It appears that it rounds up/down to the nearest mhz. This is slightly problematic for me as I overclock my bus. Here is a screenshot showing what I see.

    image.png.b97f0b2e03cc1f8d180e456c02d40566.png

    At the top is HWINFO64 where you can see it matches AIDA64 CPUID. Is there anyway to update the Real Clock and the CPU FSB simple sensor item to reflect what is in AIDA64 CPUID? This way we get a little more precision with this clock speed.

     

    Thanks!

  3. 9 hours ago, Fiery said:

    Yes, thanks a lot for performing the tests.  Please upgrade to the latest beta version of AIDA64 Extreme available at:

    https://www.aida64.com/downloads/latesta64xebeta

    After upgrading to this new version, make sure to restart Windows to finalize the upgrade.

    Let me know how it works.

     I've got 3 fans and 3 correct fan speeds! :)

    image.png.60449cb536c75f2e804fea50e647f5a0.png

    As always, @Fiery, thanks for the hard work!

  4. @Fiery well this is interesting...

    I've set the GPU fans to 100% and they do display the correct values:image.png.af9420506210aede3eb1dd3f6c6d138d.png

     

    However, anything under 100% and things start to get weird... It looks like GPU3 is actually the correct percentage while GPU and GPU2 appear to have the wrong ratio.

     

    Here they are at 75%:

    image.png.5f29b5316c87dcb97b1beb077c3e1ef2.png

     

    Here they are at 50%:

    image.png.8b31d3096a60e20420a9f2df64d939c8.png

     

    Here are the values at 25%:

    image.png.bb64e7599292ad76f5cb1046b1250f6e.png

     

    Finally here they are at 15%:

    image.png.80bcd33547f934f9ce5551cf872cda20.png

     

    @Fiery I hope the above was helpful.

     

  5. Hey @elitegamer352 and @gbubrodieman! So sorry for the delay. I didn't have notifications turned on so I never saw these.

    From my screenshot above I was on 6.30.5511 Beta

    image.png.1fa3643da973478196e288ce19d9b633.png

     

    I'm currently on 6.32.5600.

    image.png.b87d71f2ba095d5351bc227113c25b5f.png

     

    As you can see above I do see the third GPU fan, however I'm noticing that the GPU Fan % is off for GPU and GPU2 fans. On the EVGA 3080 FTW Ultra 600 RPM is 20% not 44%. @Fiery Is this a known issue?

    I hope this helps!

     

  6. The temperatures in AIDA64 appear to be 2 degrees higher than the other tools that monitor my GPU temperatures. Is this a known issue? Or perhaps, is there a different temperature I should be looking at in AIDA64?

    In the screenshot I have the following applications running simultaneously.

    • EVGA Precision X1
    • HWiNFO64
    • GPU-Z
    • AIDA64

    All of the temperatures match except for AIDA64. These are my idle temps, but this 2 degree difference scales even when under load. Any help would be appreciated! :)

    2005001791_wrongtemps.thumb.png.9b3e0b03c6e1b46d8b5f30eb35527ba4.png

  7. On 11/10/2020 at 8:22 AM, Fiery said:

    We've implemented that somewhat secret feature in order to avoid having to use conversion or special expressions.

    That really is a secret feature... and it works perfectly. Is it fair to say that this secret feature isn't documented anywhere? :)

    image.thumb.png.0807d28f0976e8f0c846a4a597437d98.png

     

    On 11/10/2020 at 8:22 AM, Fiery said:

    but the problem with the current LCD layout / SensorPanel editor is that it's already too complex for average users.

    I don't mean to push back but, isn't it fair to say that AIDA64 users aren't average users to begin with? B) I would venture to guess that most of the users of AIDA64 are power users. Being one of them, I can wholeheartedly say that having more options, even if on the surface they appear complex, is desired, especially for an application that provides us with detailed low-level data.

    From a screen real estate perspective, nesting this feature in a collapsible section (that is collapsed by default) at the bottom of the window labeled Advanced Settings could mitigate this issue.

    As you can see I'm really pushing for this feature... :)

     

    Thanks again for secret tip and let me know if this is something that could ever get added to your development roadmap!

     

     

     

  8. There are a few of the sensors where the default unit and value are either too large or just aren't desired. For instance, the default Download Rate. Currently the default Download Rate displays in KB/s. While I can change the unit label, I don't have any way to change the value itself. My enhancement request is to allow what I'm calling Value Modifiers or Expressions. These would only be available for sensors whose values are numbers (ints, floats, etc.).

    Let's go through a real world example of how we could implement this. Here is my current sensor panel. Note the upload and download speeds being in KB/s (red box). While it's nice to see KB/s, I would rather it display in MB/s.

    sensor_panel_modify.png.4d91ae2555ddf1e89f5656fa090506b9.png

     

    With this enhancement, rather than requesting one off sensor calculations or modifications, I feel it would be easier and more powerful to let the end user decide how to display the values. With my proposed enhancement I would be able to modify the value of the Download Rate by creating a custom expression. Below, the end user would be able to choose a custom operator (+, -, /, *, ^, etc.) then choose which operand would be the sensor value and which operand would be the custom value. Because performing math on a given value could lead to out of control decimal places, it would be ideal to include some level of precision, hence adding a section for precision.

    mockup_focus.png.f53b8814e6caa4e905c1cfe9ba711ff2.png

     

    My custom Value Modifier (above) would take the Sensor Value and divide it by my own Custom Value (1000). Essentially this would turn 1200.1 into 1.20. Next, I could use the already existing Show unit functionality and modify my label from KB/s to MB/s. Now I would have the value I desire and have much more flexibility with all of the other sensor values.

    I hope my intentions are clear and that my enhancement request is easy to understand. Please reach out if there is anything you would like me to clarify.

     

    This should go without saying, but thank you for all of your hard work on this application. I use it daily and greatly appreciate all of its features! :)

     

     

     

     

×
×
  • Create New...