v1.0

After nearly eight months and over 300 commits (plus the year before I released this project), YAMDCC is finally ready for a full release!

v1.0 comes with configs (and full support) for 5 laptops:

• MSI Crosshair 17 B12UGZ
• MSI GF63 Thin 11SC
• MSI Modern 15 A5M
• MSI Katana GF66 12UG
• MSI Titan GT77HX 13VH

Many more MSI laptops are likely to be supported with the generic configs.

Summary of changes since v1.0 RC:

• Fix update checks (again)
• Add decoded text display to EC Inspector
• Add success dialogs to service stop and uninstall
• Update dependencies:
  • MessagePack: v3.1.1 -> v3.1.2
• Minor bug fixes and optimisations

Click here for the full changelog.

v1.0 RC

This is it folks, hopefully the last update before the full 1.0 release!

A few more updater fixes this time around.

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

• Add configs for the following laptops:
  • MSI Crosshair 17 B12UGZ (#48)
  • MSI Titan GT77HX 13VH (#49)
• Add success dialogs to service stop and uninstall
• Fix crash when attempting to check for updates from the YAMDCC config editor if the updater (Updater.exe) couldn't be found
• Fix updater not passing file path arguments with spaces correctly
• Better version detection
• Close/kill all running instances of YAMDCC (both the config editor and EC Inspector) before installing an update
  • The YAMDCC service is already stopped before updating
• Back up YAMDCC configs from previous versions before updating
  • They would get moved to the Old folder, then get permanently deleted if updating again

Click here for the full changelog.

No one reported any config editor bugs since the last release. Either that means I'm a better programmer than I expected, or the bugs haven't been found yet...

Please report any bugs you find to the issue tracker.

v1.0 Beta 8 (hotfix 1)

This is a hotfix release to fix a few updater bugs:

• Fix crash when no releases are found during a background update check
• Fix potential bug causing the updater to rank beta releases as "more up-to-date" than full releases
• Try to update to the latest pre-release if no regular release is found

Click here for the full changelog.

See v1.0 Beta 8 for changes between Beta 7 and 8.

More updater fixes are likely to come in the RC, mainly relating to determining whether the latest (pre-)release is more or less up-to-date than the current version.

v1.0 Beta 8

Please use v1.0 Beta 8 (hotfix 1) instead, as it contains a crash fix for background updates.

More bug fixes, optimisations, and a new tab in the config editor!

Summary of changes since v1.0 Beta 7:

• Add a new tab in the config editor with general config info (i.e. config author and laptop model/manufacturer)
  • This has been present in YAMDCC configs since the beginning, but never shown anywhere
• Disable the Apply, Revert, and Full Blast buttons while the YAMDCC service is processing any of these requests
• The YAMDCC updater now shows our custom crash dialog (the same one as the config editor) if it crashes
• The YAMDCC crash dialog now shows the crashing program's name (in the crash message) and version (in the crash report)
• Every setting that got saved as a separate file (i.e. last loaded config and EC-to-config state) have been moved to the global config
  • If you update after starting the process to get your laptop's default fan profile but before a reboot, the EC-to-config progress will be lost and you might need to start over (but your existing fan profiles will be left intact if you didn't reboot). Keep this in mind when updating to this release.
  • The last saved config will be migrated automatically the first time you open the config editor. The migration will be removed by the time the full v1.0 releases.
• Bug fixes:
  • Fix crash when toggling advanced options without any config loaded
  • Fix buggy curve editor when loading a new config (e.g. no config loaded before the new one)
  • Fix crash dialog not closing the application that opened the crash dialog when using the close (X) button to close the crash dialog
• Tons of optimisations and refactors

Click here for the full changelog.

This will likely be the last beta release before the v1.0 RC (which will release once I fix all the bugs that I probably introduced in my optimisation frenzy), then a full release after that.

Please report any bugs you find to the issue tracker to ensure the full v1.0 release is as stable and bug-free as possible.

v1.0 Beta 7

An optimisation/bugfix update this time around.

Summary of changes since v1.0 Beta 6:

• Various small bug fixes:
  • Fix crash that could occur when attempting to log a null string
  • Fix the "service not responding" message that appears in the config editor not being persistent
  • Revert to using net for service start/stop since sc doesn't wait for services to finish starting.
    • This causes issues if the YAMDCC service crashes during startup
  • Detect if the YAMDCC service is running before attempting to stop it during an update
  • Don't restart the YAMDCC service was not running before an update
• Replace Octokit and Markdig with Newtonsoft.Json and Marked.NET respectively (saves ~1 MB)
• Roll our own API code for YAMDCC updates instead of relying on Octokit (made possible with Newtonsoft.Json)
• Several optimisations across all YAMDCC projects

Click here for the full changelog.

Please keep reporting any bugs you find to the issue tracker to ensure the actual v1.0 release is as stable and bug-free as possible.

v1.0 Beta 6

If you are having issues updating to this release from the updater, click here to view and download this update on GitHub.

A smaller (in terms of features) beta update this time around, with many updater fixes and a new config option for advanced users!

Summary of changes since v1.0 Beta 5:

• Add a new config option: FanMode
  • This is an advanced option that should only be changed if you know what you're doing.
  • This setting has undefined behaviour if both of the below are true:
    • The fan profile is set to anything other than Default
    • The fan mode is set to anything other than Advanced
  • Not all of the options provided may work as intended on all laptops
  • This change is backward compatible with existing configs (they will continue to use the old RegConf method of setting the correct fan mode)
• New updater features:
  • Updated version check method to differentiate between old, up-to-date, and newer/development versions.
  • Add option to force re-install the latest release if running the latest version or running a development version
  • Link to the corresponding GitHub release when showing a changelog
  • Add possible solutions to the update check error messages
• Several updater bug fixes:
  • Fix two crashes when the updater asks for UAC permission (to toggle automatic update cheks and while installing an update)
  • Fix background update check not working at all (would always return "up to date", even when checking manually returned "update available")
  • Disable bottom row of buttons while downloading and installing an update (this prevents someone from trying to start an update again after it's already in progress)
  • Fix broken "bytes remaining" text while downloading an update (including duplicated "bytes" text and incorrect unit rounding)
  • Fix the auto-update task not being removed when uninstalling YAMDCC
  • Several tweaks and internal changes

Click here for the full changelog.

This will probably be the last feature update of YAMDCC before v1.0 is released, so keep reporting any bugs you find to the issue tracker, but keep in mind your feature request will most likely be added to v1.1 instead.

v1.0 Beta 5

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
  • The included configs have been updated for this change
• 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.

v1.0 Beta 4 (hotfix 1)

This is a hotfix release to fix YAMDCC crashing when attempting to uninstall the service and deleting the YAMDCC data directory.

Click here for the full changelog.

See v1.0 Beta 4 for changes between Beta 3 and 4.

Please report any bugs to the issue tracker.

Remember to stop the YAMDCC service (Options > Stop service and exit) before installing new releases to prevent "file in use" errors.

If you need to ask, you're probably looking for the Release build.

v1.0 Beta 4

Please use v1.0 Beta 4 (hotfix 1) instead, as it contains a crash fix when uninstalling the YAMDCC service.

Time for a major beta update, fixing a few long-standing bugs that have been here since the beginning and adding an all-new tool for config creators!

Summary of changes since v1.0 Beta 3:

• Fix the config editor not supporting anything other than a fan profile with exactly 7 fan curve points
  • This change will make it easier to support non-MSI laptops (assuming there's anyone making configs for non-MSI laptops).
• Rename YAMDCC.exe to ConfigEditor.exe
• Create EC Inspector (ec-inspect.exe), a tool to dump and monitor EC registers
  • This should make it easier to troubleshoot configs without relying on NoteBook FanControl's ec-probe.exe
• The YAMDCC service log level can now be adjusted from the default via Config Editor
• Show a progress dialog while connecting to the YAMDCC service
• Increase EC status timeout to 10 ms
  • This fixes (or at least reduces) EC read errors, especially while using EC monitoring, for some users
• Various config updates
  • Move generic configs to their own subfolder
  • Add dual-fan generic configs for all MSI laptops
  • @tedomi2705: Add config for MSI Modern 15 A5M (#29 - first pull request!)
• Other internal changes and bug fixes

Click here for the full changelog.

Please report any bugs to the issue tracker.

Remember to stop the YAMDCC service (Options > Stop service and exit) before installing new releases to prevent "file in use" errors.

If you need to ask, you're probably looking for the Release build.

v1.0 Beta 3

Time for yet another beta update!

Below is a summary of changes since v1.0 Beta 2:

• Better keyboard navigation:
  • Fix incorrect TAB ordering for some windows and dialogs
  • Add keyboard shortcuts to the config editor
• Fix a possible indefinite hang if the config editor fails to connect to the YAMDCC service by adding a timeout of 5 seconds
• Update some dialog messages
• Minor optimisations

Click here for the full changelog.

Please report any bugs to the issue tracker.

Remember to stop the YAMDCC service (Options > Stop service and exit) before installing new releases to prevent "file in use" errors.

If you need to ask, you're probably looking for the Release build.