![]() I made it disabled by default in the latest (4.6.3) version BTW. So all you need to get rid of settings reset (if you understand and accept the risk of persistent settings) is disabling that option. But nobody normally reads any documentation supplied with application sadly. I documented it since day one after providing this option. MSI Afterburner) can do it optionally (it is controlled by “Erase autosaved startup settings” option in "AMD compatibility" settings group). Sapphire Trixx) provide startup settings erase feature in unconditional form (i.e. To bypass this unsafe autosaving feature, majority of third party applications _purposely_erase_ all Wattman startup settings on applying new clocks, fan speeds, voltages and so on. ![]() But in reality Wattman will silently record such changed fan speed as new startup setting, even considering that you _never_ asked it to do so. erroneously drag fan speed slider to minimum) then remove the application, reboot the system and expect fan settings to be restored to defaults. With such implementation you could simply try to launch some third party tool from Sapphire, GB or MSI, plaay with some setting (e.g. Any AMD ALD API setting changes became persistent, which means that Wattman silently records any GPU settings changes made either by itself or third party applications and silently reapply those settings after reboot. ![]() There is rather unsafe design pattern in ADL API, which was introduced in AMD driver with Wattman announce. Settings reset is expected and by design. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |