Quoted from "InfoSeeker"

It probably appears I am a bit 'button centric', but the Input > Button' function is completely dysfunctional with X70 (button_fail)

Quoted from "InfoSeeker"

With the 'power supply' monitoring option activated I see no results.
setting.jpg data_view.jpg

Quoted from "B3L13V3R"

When I use my desktop overlays, they work but blanked out both screens' backgrounds to a grey (see screenshots). It also hides the taskbar. Strange. It was working as it should for a few hours but at a random time, my desktop turned grey, and the taskbar disappeared.

Quoted from "Speedy-VI"

Quoted from "InfoSeeker"

Are you able to have the Button Input function properly on all 3 of your systems?

I just tested this. I have not set up a button in quite a while so I may be hazy on how it is supposed to work (or how it used to work). In your video, you expect 3 things to happen that did not happen:

• When the button is in Relative mode and set to 0, you expect the button value to increment when you click Button Input.
• When you move the dial, you expect the button value to change
• When you increment the button value but do not click Button Input, you expect the slider and dial to change.

I saw the same exact behavior but to me it makes sense. To me, the button value is user-input data and it is not affected by moving the slider or dial. In Relative mode, the button value acts as an offset, and moving the slider or dial should not change the offset value. In Absolute mode, the button value is an absolute value and moving the slider or dial should not change this value.

1. If the button is in Relative mode and set to 0 and you click Button Input, the slider and dial will not change because the offset is 0.
2. If the button is in Relative mode and set to value X (not zero), and the slider and dial are at value A, clicking Button Input will cause the slider and dial to move to A+X (if X is positive) or A-X (if X is negative).
3. If the button is in Absolute mode and set to value X, and the slider and dial are at value A, clicking Button Input will cause the slider and dial to jump to value X.
4. Clicking Button Input does not cause the button value to increment, it just sends whatever value the button is set to, which will affect the slider and dial (unless the button is in Relative mode and set to 0).

Moving the slider or dial does not change the button Absolute or Relative value. Again, to me, the button value is a user-input data value (either Absolute or Relative) that is not affected by the position of the slider or dial. Incrementing/decrementing the button value does not do anything until you click Button Input. When you click Button Input, the button value is sent to the slider and dial which then react accordingly.

Maybe it used to work as you expected and they rethought this. What I am seeing makes sense but I don't know if it used to work this way. Does this behavior make sense to you?

Quoted from "Taubenhaucher"

OK, Chrome has solved it.
I tried that and I think it works, at least as I understand it.
The button is controlled by the "Value" field, for example if I enter 1 and press the "Button Input" the value changes on the slider and dial, both relative and absolute.

The value at the button changes the value of the slider and the dial by exactly the set value each time the knob is pressed.

If the value is 0 nothing should change according to my understanding.

Quoted from "sebastian"

Quoted from "InfoSeeker"

It probably appears I am a bit 'button centric', but the Input > Button' function is completely dysfunctional with X70 (button_fail)

The buttons input works without any error. When you use relative mode you have to set a value diffrerent to zero.

Quoted from "InfoSeeker"

With the 'power supply' monitoring option activated I see no results.
setting.jpg data_view.jpg

this works only when you have a supported PSU

Quoted from "Taubenhaucher"

The button is controlled by the "Value" field, for example if I enter 1 and press the "Button Input" the value changes on the slider and dial, both relative and absolute.

The value at the button changes the value of the slider and the dial by exactly the set value each time the knob is pressed.

If the value is 0 nothing should change according to my understanding.

Quoted from "Dundys"

So far X71 is OK, no lag and actually it feels snappier then even X69, that is great so this has been fixed, at least it seems that way for now, we will give a little time.
I will report back if anything changes.

Thank you

Quoted from "sirn"

I've been running X71 for a few hours, but sadly the high CPU usage in Aqua Computer Service is still there.
It is even higher when Aquasuite is left running for a long time. It has been only two hours with X71, but I'm also seeing the same issue.
In the last two reboots, I haven't even logged in to Windows. I'm seeing this behavior with two of my machines with Aquasuite running, one with QUADRO, and another one with Aquaero 6 LT.

Quoted from "sebastian"

The buttons input works without any error. When you use relative mode you have to set a value diffrerent to zero.

Quoted from "InfoSeeker"

My system's PSU is a Corsair AX1600i.
Aquacomputer Hardware Monitor does not appear to sense it, but HWiNFO does.

Quoted from "InfoSeeker"

If the button were allowed to loop to min from max, one could step through all value repeatedly to determine the best value.

Quoted from "Speedy-VI"

Quoted from "InfoSeeker"

My system's PSU is a Corsair AX1600i.
Aquacomputer Hardware Monitor does not appear to sense it, but HWiNFO does.

If HWINFO can monitor the PSU, you can import the data into AQS via HWINFO's Shared Memory Support. This feature works great but it does have a 12-hour limit unless you buy a HWINFO license, which I feel is well worth it. I have a Thermaltake iRGB Plus PSU that I bought mainly because it has a USB port on it. Thermaltake's software is complete trash but HWINFO and SIV can monitor it. Since HWINFO can monitor it, I can import that data into AQS.

I prefer to disable all Hardware Monitoring in AQS and import sensor data from HWINFO because it's sole purpose is to monitor sensors and it is very good at it. HWINFO is updated often to keep up with ever changing hardware. It has been updated 31 times this year compared to 6 times for AQS. Nothing against AQS. It's just that monitoring sensors is not the primary focus of the program. AQS is best at cooling loop component control. HWINFO is best at monitoring sensors. Since the Shared Memory Interface makes it easy to import everything that HWINFO monitors into AQS, I take advantage of this by using each program for what it is best at doing.

Quoted from "InfoSeeker"

Agreed, if you look at the 2nd attachment (PSU_absent) you will see the PSU under the the HWiNFO tab. The feedback is informational for the Devs.

Quoted from "Speedy-VI"

This is correct if the button is set to Absolute mode, which it is in your screen shots. If the button is set to Relative mode, it acts as an offset.

Examples - If the slider and dial are at 2 and the button is in Relative mode and set to 3, when the Button Input is clicked, the slider and dial will change to 5 which is the value they were at (2) plus the value of the button (3). If the slider and dial are at 5 and the button is in Relative mode and set to -3, when the Button Input is clicked, the slider and dial will change to 2 which is the value they were at (5) minus the value of the button (-3).