First, thanks for this reverse engineered tool.
This issue is just an info for others, it can be accommodated into the readme if we can agree on the things I did here.
I got my hands on one of the AIOs and it ran 3200rpm constant, making noise.
I compiled the app for Windows x64 target, all that I had to change in the app build was to disable the AOT in the build configuration.
I can confirm the app working on Windows 11 and the setting from the app can live together with official GCC app.
My recommendation would be to have the GCC app running and controlling the fans while having set Customized pump mode to curve of constant rpm 2000 for all targets. (cli is used only for setting pump settings once)
If you want to set something with the cli tool, best is to probably turn off GCC and then set the values and turn the GCC back on.
GCC UI won't show the correct pump mode, but it shows correctly the current RPM and curves, it also does not seem to revert back the custom values I set earlier.
First, thanks for this reverse engineered tool.
This issue is just an info for others, it can be accommodated into the readme if we can agree on the things I did here.
I got my hands on one of the AIOs and it ran 3200rpm constant, making noise.
I compiled the app for Windows x64 target, all that I had to change in the app build was to disable the AOT in the build configuration.
I can confirm the app working on Windows 11 and the setting from the app can live together with official GCC app.
My recommendation would be to have the GCC app running and controlling the fans while having set Customized pump mode to curve of constant rpm 2000 for all targets. (cli is used only for setting pump settings once)
If you want to set something with the cli tool, best is to probably turn off GCC and then set the values and turn the GCC back on.
GCC UI won't show the correct pump mode, but it shows correctly the current RPM and curves, it also does not seem to revert back the custom values I set earlier.