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.

v1.0 Beta 2

Happy (early) New Year! It's time for the second beta release!

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

• Fix a long-standing rare bug in YAMDCC which caused issues including:
  • EC monitoring breaking after a few minutes of monitoring
  • The config editor not responding to attempts to apply a config or toggle Full Blast
  • Freezes/crashes of the YAMDCC config editor or service (in extreme cases)
• Add progress dialogs for service start, stop, install, and uninstall
  • This should make it more obvious if YAMDCC is still responding while configuring services
• Fix keyboard backlight brightness slider scrolling too quickly in response to mouse clicks
• Update dependencies:
  • MessagePack: v3.1.0 -> v3.1.1
• Other internal code changes

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 1

After nearly 6 months of (somewhat) active development (and more than a year
since development started), YAMDCC is finally ready for a beta release! 🎉🥳

Please report any bugs to the issue tracker.

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

See the Wiki for configuration instructions.