Jump to content

mondueo

Members
  • Posts

    31
  • Joined

  • Last visited

  • Days Won

    1

Posts posted by mondueo

  1. Yeh the import/ export is a buggy  mess.  I logged a ticket about it but have not gotten a response.  I believe it uses the primary display settings when importing and exporting.  You pretty much have to match the display environment of the user who exported.  And if the user who exported had 2 different monitors with 2 different dpi settings well I am Afraid it probably was corrupted on export.  In that case there is nothing you can do.  Making your own panel isn't hard though.  See this thread half way down:

     

  2. @Fiery Thank you for the update.  While most of us knew that this is a Windows 11 bug, we were more upset of the fact we were not getting much of a explanation as to why other programs have found work arounds and Aida64 has not.  Thanks for the explanation, this makes sense.

    On the support side, Aida has been very quiet as of late.  Some of the paid customers have filed tickets about this issue and never received a response. Me included.  So naturally it's going to be frustrating to your customers when we don't get any answers, good or bad.  Microsoft has Hundreds of doors to bang on (which door do we bang on?), and a good majority of your customers don't know the difference and/or won't be able to explain what is happening clearly in a support ticket to Microsoft. Lots of people don't understand testing methodology, test environments, outside variables etc. So we come to you for help hoping that Aida can work with Microsoft as an advocate for us and for it's software.  As a software developer myself, my team is always trying to find workarounds to problems outside of our control. 


    There are plenty of people, me included that would like to help test this bug with you and help narrow down a cause.
    Maybe a good start would be to create a new Form Topic for incorrect CPU usage and have people post system specs, screen shots etc and start from there? That way support team could reach out.

    Thanks for the temporary workaround in the next beta build.  Let us know if you need any help diagnosing this issue in the future.  

    • Like 1
    • Thanks 1
  3. 17 hours ago, jimmysombrero said:

    I'm running the latest non-beta versions of both Win 11 and Aida64 and Aida64 is not reporting CPU usage correctly.  HWinfo64 and MSI Afterburner don't seem to be having any issues, so Windows doesn't seem be the only cause of the issue. 

    I'm slightly more perturbed than I would be normally, however Aida64 is paid software that requires you to keep paying if you ever update your hardware, while the other software is free.  I personally would rather have accurate monitoring than the panel.  The only reason I pay for Aida64 is the panel and that functionality is useless if it isn't an accurate representation of my CPU usage.  Finalwire needs to figure it out or they are going to start losing paying customers. 

    They are aware of the issue. It is a Microsoft issue.  But there are obviously work arounds for the time being.  Aida has chosen not to implement this.  Aida64 has been quiet as of late on this issue as well...  Multiple support tickets have been submitted from many people.  Unfortunately, they choose not to respond to most of these.  I have filed a couple myself and have gotten zero response. Even though they say they expedite paying customers with keys. This was 2 weeks ago.   A formal post about this issue would go a long way.  Transparency is always best in these situations, rather than leaving your paying customers guessing. Yes, I have pretty much thrown in the towel on Aida64. I am definitely not paying for it again after my subscription is done.  Why should I pay for broken software? I had to do a clean install of windows 11 21h2 and turn off updates to get correct values again.

    I have no idea if they are still working on a fix or if they are hoping Microsoft will have a hot fix soon.  Since it's been this long (3 months), I am not holding my breath for Microsoft.  @Fiery can we have an update on this.  What is the plan?  This is still an issue.

    • Thanks 1
  4. Fiery, Here is a screen shot to support my evidence.  I did a simple calculation to show that it's taking the 150% scaling and applying it to the Sensor panel size and also enlarging the text.... (1920 x 1.5 = Aida64 resolution...) It's also enlarging the Bar.  I can only image that it will also have issues with gauges and other things.  Please keep in mind, I have already put some of these sensors pieces and sizes back in their place such as the RAM, NETWORK and CPU values.  You can Clearly see in RED other values floating outside the background space. 

    Scaling.png

  5.  

    3 hours ago, Fiery said:

    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. You may need to enable status bar in AIDA64 / main menu / View first.


    Thanks,
    Fiery

    I was running the aida64 build from July.  I exported the sensor panel from the latest build.  I installed the latest build and the issue is resolved. 

     

     New issue:

     

     Fiery, I have 2 monitors.  4k at 150% scaling(primary) and one set to 1080p 100% scaling(secondary).  The sensor panel rests inside the 1080p monitor.  There seems to be a big bug on exporting the sensor panel in this situation.  I have not tested this extensively, but when exporting the panel to save it, It seems to be reading the primary monitor scaling settings.  In my case 150% scaling.  It's shifting and enlarging all the text and images according to the primary monitor settings.  Can we please have a fix for this?  I spent literally hours on a panel yesterday and decided to reinstall windows.  When I went to import the panel all the values were shifted and enlarged the senor panel size was also larger than what I saved it as...took me hours to fix everything.  And when I have to do a reinstall again....I will have to fix the sensor panel again.  Can we fix the export from reading the scaling value of the primary monitor?  Or have a setting to tell which scaling value to use?  This is a extremely frustrating bug....

    Thanks,

    Mondueo

     

     

     

  6. I just did a clean install of windows 11 so I could be on build 21H2 to bypass the Window 11 sensor errors....and when I imported my sensor panel, the $CPUMODEL tag says UNKNOWN. Other tags work just fine such as the one for the motherboard name.   Windows Task manager ID's the CPU fine.  Any help would be appreciated. 

  7. On 11/23/2022 at 2:59 AM, Fiery said:

    Somehow we're unable to reproduce the issue.  Maybe Microsoft has already fixed the issue in one of the KB's applied on 22H2?

     

    Just curious then, seems off still based on this screen shot.  Even the reported Clocks aren't accurate?  (also, I am building out a new panel atm little junky looking still ;) )

    Current windows build: 22621.963

    No new Win11 updates are available.
    Aida64 Update frequency on Sensor page is 500ms and Core Clock just sits at 5300mhz all the time while Windows task manager reports different clocks.

     

    Untitled.png

    • Thanks 1
  8. I have the same problem.  Under compatibility mode in windows under the .exe properties you can have aida64 ignore DPI scaling. Set it to system.  But as far as the resolution issue.  Where the window moves when the res changes like when you go in game...no idea.  It's super annoying.  I have a feeling there is an issue with the program itself.

    image.png.d85354540021f759de2d8e676c9ee19b.png

×
×
  • Create New...