dna
-
Posts
10 -
Joined
-
Last visited
Content Type
Profiles
Forums
Events
Posts posted by dna
-
-
On 10/8/2019 at 3:35 PM, Fiery said:
We've implemented a new option called Alignment on the AIDA64 / main menu / File / Preferences / Hardware Monitoring / OSD page. You'll know what to do
Ok i get it now.. at first I was like "that option has been there for a long time" .. Then I figured out what you did. Alignment is not new, but what you did add is a new option within the dropdown called Justified which justifies the title and value separately. Thank you for adding this, much appreciated!
-
Hello, I have used the AIDA64 OSD panel for a very long time.. maybe 10 years or so; I absolutely love it. One thing I would love to be able to do is to justify the title of each OSD Item separately from the reported values. i.e. - have all the titles be on the left and the values to the right, and the total width of the OSD Panel dependent on the longest title + value string.
You can see in my screenshot how i have got it setup in a similar fashion, but I had to do so by using a specific number spaces after the item title and also using a monospaced font like Courier New (all characters have same width). However as you can see in my other screenshot, this method I use has its flaws.. for items that have values which can have multiple orders of magnitude (i.e. 1, 10, 100), the will push or pull the alignment. When Ram Used is only 5000MB, this is expressed using 4 digits. But, when the system is using 12000MB, it must use 5 digits to denote this (obviously). This is true for any item whose value can change by 1 or more orders of magnitude, as demonstrated in my example. So, while my little spacing trick is nice, it would be great if something could be written in the code that will allow for justifying the titles independently of the values, and perhaps even a variable for minimum spacing between them.
Feel free to let me know your thoughts.
Images (below)
- Image 1 (Left): my current OSD setup
- Image 2 (Right): showing how the spacing changes in response to changing sensor values)
Cheers,
Michael
-
On 9/25/2019 at 2:54 AM, Fiery said:
I really don't know... Because we have done everything we could: talked to both the management and the right technical professionals at Corsair who understands the issue in depth. And when I say "we", it's not only us here at FinalWire, but also the other folks behind CPU-Z, HWiNFO, HWMonitor and SIV.
I think the only way that may work is when multiple (10+, maybe 100+) inquiries to be submitted to Corsair customer support. That should trigger someone from middle management to dig deeper and think about the issue thoroughly.
ok so you think i should just approach the normal support team.. i can do that. it would be cool if we could get a group of people together to do this. if you have any contact info for someone i may be able to reach out to, please DM me and we can discuss that. We seem to be in agreement on one thing.. that a single user report to customer service will do very little to help. Of course I will do it anyways. I would absolutely love to have this data appear on my OSD panel.. opening iCUE to view my water temps (i have water temp probes positioned after the radiators, after the CPU and after the Pump/Res) is far from ideal, I hardly ever check them because it takes so much time.. its just not a very user-friendly solution for active monitoring..but, I digress
-
On 9/22/2019 at 8:29 AM, Fiery said:
This is a collision between AIDA64 and iCUE. Please report this issue to Corsair. We've been in contact with them for over a decade now, but this is the only issue where we cannot convince them to fix their software. AIDA64 -- as well as many other 3rd party monitoring applications including CoreTemp, CPU-Z, GPU-Z, HWiNFO, HWMonitor, MSI Afterburner, Rivatuner, SIV, SpeedFan, etc -- use industry standard synchronization mutexes in order to prevent such collisions when multiple monitoring software is trying to interact with the same hardware. This works great as long as you use two or more of the mentioned software concurrently. We've got to the point of convincing Corsair to implement a synchronization mechanism in their previous generation software (Corsair Link Software), but then at a certain point they simply removed the mutex and never implemented in iCUE. It means iCUE cannot be used concurrently with 3rd party monitoring applications which is simply unacceptable IMHO. No matter how much pressure us and the developers of the previously mentioned 3rd party monitoring software put on Corsair, they stick to their stance on this matter. Only you, the customers of Corsair and owners of Corsair hardware have a chance to convince Corsair to change their mind.
This makes sense. So my question to you would be this: given the nature of the issue and its complex history, what would be the best thing that I can do, as a Corsair consumer, to help motivate their development team to act on this. Contacting support is not likely to help, as this issue goes well beyond the scope of first-layer tech support. This appears to be a problem that senior technicians and developers need to be presented with, and I'm afraid that spending an hour explaining the problem to general tech support will be a waste of my free time. Maybe I'm wrong. I really don't know, which is why I ask for your opinion on the most effective way for a customer/consumer to bring this to the attention of middle-management or senior employees, done in such a way that it doesn't fall on deaf ears, so to speak
-
Motherboard: ASUS Maximus XI Formula
OS: Win 10 Pro
Hello, I am having an issue with the option in Stability settings that allows you to enable Corsair Link sensors. This, it seems, is pulling sensor data from my Commander Pro, which is a hub that connects several water temp probes, 6 radiator fans, and lighting strips. When i enable that option, I can see where I'm able to add the water temp sensors into my OSD panel, however, enabling the option in Stability section does something where it's screwing up the Corsair iCUE software. Once enabled in AIDA64, the iCUE software gets really buggy, the stops reading the Commander Pro correctly, sensors start dropping out, etc.
Not sure if this is a problem with iCUE or a problem with AIDA64... both are currently updated using latest releases (AIDA64 on latest beta, iCUE on latest stable) -
19 hours ago, Fiery said:
Embedded Controller (EC) is a special chip on your motherboard that extends the usual sensor measurement capabilities of the Super I/O chip (that's also on your motherboard) with special readings. However, on some Asus motherboards polling (reading) EC registers can cause slowdowns and latency spikes. In which case it's best to disable EC support in AIDA64, and by that sacrificing a few sensor readings. If you make a screen shot or photo of the Computer / Sensor page with and without the EC options enabled, you can see which values you would lose when you disable EC support. In most case those are not vital sensor readings, and there are only a few of them.
makes perfect sense. thank you for being able to resolve this so quickly, even though this probably isnt a bug but rather a known limitation/conflict. i appreciate the help!
- dna
-
On 4/1/2019 at 3:39 AM, Fiery said:
Please try to disable the two Embedded Controller related options in AIDA64 / main menu / File / Preferences / Stability, and restart AIDA64 to apply the changes. Let me know if it makes a difference.
Hi Fiery,
Amazing! It worked! I opened the menu this is what I found:
- "Controller (EC) Support" = enabled
- "Embedded Controller (EC) bank switching" = disabled
So, per your instructions I diabled the "EC Support" option, rebooted, and now im back up and running. I don't get any of the CPU latency spikes like I was getting before.
Can you explain what those options are for and why they may have been causing an issue? I really appreciate the help!
- M
-
On 4/1/2019 at 3:39 AM, Fiery said:
Please try to disable the two Embedded Controller related options in AIDA64 / main menu / File / Preferences / Stability, and restart AIDA64 to apply the changes. Let me know if it makes a difference.
Will do.
-
Current beta is lagging the PC during gameplay and other intensive tasks. I’ve never experienced this before in the 15 years I’ve been using this tool and ~10 years using the OSD panel. So I spent a lot of time troubleshooting this because it never crossed my mind that AIDA64 would be a potential culprit. Indeed, when I completely close it, the latency spikes cease.
this was tested on my primary rig (9900k, 2080ti, ASUS M11F, nvme/pcie system drive - with system overclocked and with optimized defaults.. doesn’t matter (ie I ruled out overclock instability)
im going to test on secondary rig with 8700k, 2080 (non-Ti), ASUS M10H mobo, 970Evo nvme system drive
will report back
let me know what sort of diagnostics you’d like me to report to help get this situated
-Cheers
AIDA64 keeps starting up despite all settings
in General Discussion
Posted
thanks for this. My issue was actually being caused by having AIDA64 integrated into MSI Afterburner software (which adds some extra sensors/monitoring into Afterburner)