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. Contacting support is not likely to help, as this issue goes well beyond the scope of first-layer tech support. 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. Only you, the customers of Corsair and owners of Corsair hardware have a chance to convince Corsair to change their mind. 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. It means iCUE cannot be used concurrently with 3rd party monitoring applications which is simply unacceptable IMHO.
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. This works great as long as you use two or more of the mentioned software concurrently. 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. 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. This is a collision between AIDA64 and iCUE. both are currently updated using latest releases (AIDA64 on latest beta, iCUE on latest stable)
Not sure if this is a problem with iCUE or a problem with AIDA64. Once enabled in AIDA64, the iCUE software gets really buggy, the stops reading the Commander Pro correctly, sensors start dropping out, etc. 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. 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.
Hello, I am having an issue with the option in Stability settings that allows you to enable Corsair Link sensors.
0 kommentar(er)
