v1.1.2

Prevent users from deleting the last entry in the temperature/speed tables. (See #15)

v1.1.1

Windows

Spaces in the install path are now supported. (See #13)

Linux

No changes. (But built differently and untested. If you experience problems, you could try the previous version.)

v1.1.0

Windows

Handle XTU incompatibility

I'm not exactly sure about what triggers this, since I think I used Hyper-V in the past. But after switching to Windows 11, it resulted in me not being able to access the alfc UI, due to not handling an error related to this:

Now, a message in the UI about CPU tuning not being available is shown if that error happens.

I would like to note that I have personally not seen much of a difference from adjusting those settings in the first place, so it's not a particularly big loss in my opinion.

Linux

No changes, v1.0.3 attached for your convenience. 🙂

v1.0.4

Windows

Fixed node version mismatch.

(Also: It's highly recommended not to use previous versions that didn't include NodeJS!)

Linux

No changes, v1.0.3 attached for your convenience. 🙂

v1.0.3

• Adjusted default CPU fan speeds. Reasoning: Differences in terms of temperature andperformance are insignificant when only the CPU gets hot. But the noise difference IS significant.

Windows only

- Increased the range of supported node versions for the package that doesn't include node.
Screwed up included node version, misunderstood requirements, addressed in v1.0.4.

v1.0.0

.