Version 1.2-6.5 (watchdog tweaks, sanity-checks):
-ADL watchdog INIT reason is now clarified in log.
(this seems to be causing some confusion, please be aware that the watchdog starting does not mean that timing events are happening)
-More safety-checks added before ADL helper takes actions.
(continuation of 1.2-6.4's changes, looking for more potentially bad-situations that technically shouldn't happen)
Version 1.2-6.4 (watchdog tweaks):
-ADL watchdog interval can now be set. (including completely disabling timing-events)
-More safety-checks have been added on watchdog actions.
Version 1.2-6.3 (hotfix):
Addressed issues:
-ADL watchdog setting STOCK clocks when a card is pre-overclocked and when custom clocks is disabled.
*Original clocks are reverted properly when the profile is dropped*
**This is an unintended behavior and was corrected, blocking is supposed to behave similar to 1.2-5 in this specific case.
[where the pre-set clocks are respected in ALL circumstances => IF custom clocks is off either by checkbox OR selected devices to manage]
-Some Windows components such as the Windows registration dialog, System Information, etc -- (and probably more), were being detected by the internal rules [fullscreen detection, 3D-detection].
**The under-the-hood (non configurable) rejection of system processes has been improved, both for the scanner and window pickers.
Make sure that you are running 64bit-builds on 64bit-Windows, else this rejection will be significantly crippled.
Version 1.2-6.2 (hotfix -- critical):
-Addresses a 'deadlock' between the Main UI-Thread and ProcessScanner.
This looks like a regression between beta and release of 1.2-6. The ordering of two CriticalSections were flipped.
--If using any 1.2-6 release build (after beta), please update asap.
Version 1.2-6.1 (hotfix):
Fixed issues:
-ProcessScanner in some circumstances did not apply profile custom-clock rule changes, until the rule is re-applied.
(aka, disabling and re-enabling it, or changing dialog focus)
-Minor memory-leak (4-bytes per time) may be noticed when disabling, deleting, undoing, and then re-enabling rules w/ custom-clocks in effect.
Version 1.2-6 (major release: dealing with stuck clocks & the latest 16.11 drivers):
Fixed issues:
-Start with Windows, in specific circumstances created the scheduler entry as 'SYSTEM'.
-Clock-States should no longer get stuck when using ADL -- be it from ClockBlocker crashes (hung helper), driver-crashes, or full OS hangs.
(If ClockBlocker detects stuck states on startup, or whenever its ADL Helper is run -- these states will be automatically corrected)
-ADL init, and thus setting of clocks sometimes did not work on the latest 16.11 releases. (where all 3 retry attempts would fail in the log)
-Compute-Method no longer reliably held clocks on the latest 16.11 releases.
New Additions:
-BugTrap:
**If the controller process crashes, a crash-dump can be saved to email to me. (please send these in if you see a crash a few times, it will help me immensely in getting the software stable for everyone)
-ADL WATCHDOG:
**ADL-Helper now has a background task that constantly monitors clock-states. If clock-states change (for any reason) your desired clocks are automatically restored.
-Explicit Clock Control (custom clocks):
**You can now set a custom Overdrive target globally, in profiles, and override the stuck-clock 'fixing' reverted clocks.
=> You also may specify which devices these target applies to. (such as if you have both an IGP and discrete cards, or multiple discrete cards in the machine concurrently)
=============
Note that to enable Custom clocks in profiles you need to:
-"Enable custom clocks" on Settings > General
-Choose "Use ADL-method" on Settings > General
-Move your graphics device from the left to right on Settings > "[ADL] GPU-Picker"
As always please use common sense in what clocks you apply, especially if you're adding voltage via an altered vBios or through another utility.
**Some hardware will need options such as "Extend official overclocking limits" enabled in a tool such as Afterburner (for instance for memory clock control on the R9 Fury).
As this is not an overclocking tool (more of a supplement), I have not automated this process.
-"SHIFT" may be held during startup as an emergency halt to using custom clocks. (this will uncheck Enable custom clocks)
=============
-Added "wait-on", "wait-for", and "wait-after" concept. (these are in the Settings > General tab)
*wait-on => Process to wait on
*wait-for => Duration of time to wait for this process
*wait-after => After wait-on process has launched, or after timeout on wait-for, waits an additional period. (to give ample time for the other program to fully start)
**These options only apply whenever ClockBlocker is started from the loader processes on startup. Normal starts after a machine is running are not delayed.
**This option has been added due to custom clock control and profiles, and to address startup race-conditions.
=============
For a usage example with MSIAfterburner (if you use a clock profile in both tools on Windows Startup):
-Click on "Set Wait-On"
-scroll down and select MSIAfterburner.exe
-Select "File-Name", just like you would with the profile picker for a rule edit or addition.
-Click on "Set Wait-For"
-Enter in 60 or 120 seconds. (there's no realistic reason to not pick the largest delay, as wait-for ends as soon as the process launches)
-Set Wait-After to 8-10 seconds
=============
Misc:
-Complete rewrite of Task-Scheduler interactions, and removal of account-login prompt
-Eliminated all resize-flicker on buttons (only two more GUI-elements that aren't double-buffered remaining in the program)
-Added dialog scrollbars for the Settings > General tab (if the dialog is vertically smashed, the page can be scrolled now-- it still auto sizes horizontally)
-Various 'minor' tooltip edits and GUI tweaking
-Vulkan, DX12, and Mantle should now be properly detected by the 3D-detection rule
-Improved Compute-Method (for "reliable" approach only), which should work with the latest 16.11 drivers.
NOTE: Recent drivers (at least on the Fury-X & probably also on other cards) have changed the way that Power-Management works for CL and DC workloads.
The empty kernel trick no longer reliably works (alternate method), additionally in these drivers at very-low loads a Fury-X can drop to ~1018mhz.
The effective range of the Compute approach is ~1018-1050 now. (should still keep the card over 1000mhz at all times -- still effective, but if you want locked 1050 and if a game's load is too low you may need to use ADL)
»» Нажмите, для закрытия спойлера | Press to close the spoiler ««