Skip to content

v1.0 Beta 5

Pre-release
Pre-release
Compare
Choose a tag to compare
@Sparronator9999 Sparronator9999 released this 08 Jan 23:10
· 81 commits to main since this release
v1.0.0-beta.5
09c1b57
This commit was signed with the committer’s verified signature.
Sparronator9999 Sparronator
GPG key ID: E39582019E956F00
Verified
Learn about vigilant mode.

Time for another major beta update, with an all-new auto-updater, bug fixes, and another new config!

Summary of changes since v1.0 Beta 4 (hotfix 1):

  • Breaking config change: Change RegConfs to have an OffValue and OnValue, instead of just a single Value to be applied when enabled
  • Add config for MSI Katana GF66 12UG (#32)
  • Add an experimental auto-updater and ask on the first config editor launch if YAMDCC should check for updates periodically
    • The YAMDCC updater is still experimental. You may experience data loss if you save anything other than the YAMDCC executables in the same folder as Updater.exe.
  • Add a new option to auto-switch other fans' profiles when changing any fan's profile
    • This requires all fans in your system to have the same number of fan profiles to enable.
      • This option will be enabled by default for any loaded config that meets this requirement.
    • To avoid confusion, all fans' fan profiles should also be in the same order
  • The EC-to-config feature will now look for and overwrite the Default fan profile if it exists, or create and insert its own Default fan profile if it doesn't already exist.
    • Before this update, the EC-to-config feature would always overwrite the first fan profile, regardless of if it is the Default fan profile or not.
  • Force the YAMDCC config editor to always run as a single instance
    • If the config editor is already running and a second instance is started, the existing instance will be restored and focused
  • Fix the charge limit Enabled check box not having any effect when unchecked (disabled)
  • Fix the global YAMDCC settings (GlobalConfig.xml) being saved with the wrong config version, causing any app that loaded it to discard it
  • Fix the service log level not actually being set when using the log level menu in the config editor to set it
  • Fix a config editor crash when exiting with the EC monitor enabled
  • Minor UI and tooltip updates
  • Other performance improvements and internal changes

Click here for the full changelog.

Please report any bugs to the issue tracker.

Assets 4
Loading