The software was shocking, I returned the loop controller due to it after owning it for a day. Shame as the fan controller was decent hardware wise.

cant beat the Aquaero have one controlling via water Temp and its great, it has the potential to do so much more which I dont currently use but I may do on the next refill and clean cycle

I don't really get how you can screw up something like this.

suty455:

cant beat the Aquaero have one controlling via water Temp and its great, it has the potential to do so much more which I dont currently use but I may do on the next refill and clean cycle

Aquacomputer Aquaero or Octo or Quadro are one of the best controllers plus Aquasuite which literally is one of the easiest software to use, when I started to water cool my PC I bought it and I never looked back Thanks, Jura

schmidtbag:

I don't really get how you can screw up something like this.

Out of house programming + lack of details in user stories

Mineria:

Out of house programming + lack of details in user stories

But still, it's not that hard to develop something like this, and it wouldn't take much for EK to do a little QA testing.

schmidtbag:

But still, it's not that hard to develop something like this, and it wouldn't take much for EK to do a little QA testing.

QA will not help if they agreed on something with the developer and everything found afterwards gets labeled as additions instead of bug fixes, which probably is the case. Such can dependent on developer drive up costs far beyond budget, seems like quite a few companies run into that particular issues these days. Hence why setting up all details in user stories before agreeing on specifications is of utter importance, everything missing will most likely be threated as an additional implementation/feature. It's not an excuse though, especially if it is a product that is sold afterwards.

schmidtbag:

But still, it's not that hard to develop something like this, and it wouldn't take much for EK to do a little QA testing.

Tell that to Corsair lol.

Mineria:

QA will not help if they agreed on something with the developer and everything found afterwards gets labeled as additions instead of bug fixes, which probably is the case. Such can dependent on developer drive up costs far beyond budget, seems like quite a few companies run into that particular issues these days. Hence why setting up all details in user stories before agreeing on specifications is of utter importance, everything missing will most likely be threated as an additional implementation/feature. It's not an excuse though, especially if it is a product that is sold afterwards.

I don't see how that's legal. The developers were contracted to make something to a certain standard. If it was signed off by EK and then they went ahead and broke things afterwards, that's not what was agreed upon.

insp1re2600:

Tell that to Corsair lol.

I have lol, and with much resistance.