|
Post by llamatron on Nov 6, 2018 9:30:26 GMT
Did you try sending the same messages that don't stick than CAM, but resending them at regular intervals to "refresh" the speed override ?
But I understand if you're a bit fed up with this, not easy to work on stuff you can't quickly test yourself, and anyway people are not supposed to run two software to control a single AIO.
|
|
|
Post by siv on Nov 6, 2018 12:54:38 GMT
Did you try sending the same messages that don't stick than CAM, but resending them at regular intervals to "refresh" the speed override ? But I understand if you're a bit fed up with this, not easy to work on stuff you can't quickly test yourself, and anyway people are not supposed to run two software to control a single AIO. No, but you sent it once, the speed changed and then dropped. I currently do not plan to implement endlessly sending the same message to set the fan speed as SIV can already control the Kraken X coolers provided you only use SIV. I don't, won't and can't support SIV controlling any coolers at the same time as another utility is controlling the same coolers and advise you not to effectively ask for such a facility. I suggest you ask NZXT to fix their suboptimal firmware so that it takes 50ms rather than 1300ms to read the information from the Kraken X. I have logged ticket 214197 about this which you could reference.
|
|
|
Post by llamatron on Nov 6, 2018 17:20:37 GMT
I don't, won't and can't support SIV controlling any coolers at the same time as another utility is controlling the same coolers and advise you not to effectively ask for such a facility. I suggest you ask NZXT to fix their suboptimal firmware so that it takes 50ms rather than 1300ms to read the information from the Kraken X. I have logged ticket 214197 about this which you could reference. Yup, that makes sense, to not use 2 softwares to control 1 device.
I did open a ticket and refered to your ticket number, let's hope they'll react. We're probably not the only ones for who it's an issue.
Anyway thanks for your work ! It's nice to have an alternative to that terrible CAM software to control the Kraken.
|
|
|
Post by siv on Nov 6, 2018 17:39:42 GMT
I did open a ticket and refered to your ticket number, let's hope they'll react. We're probably not the only ones for who it's an issue. My guess is that the CAM developers don't even know it's so slow. With just SIV active and one Kraken X it's not too bad, but if say HWiNFO is also reporting the Kraken X or there are multiple Krakens then it's too long and will cause the SIV AIOs thread to be delayed and slow down the control of other AIOs.
|
|