MSI Afterburner 2.3.1 (2013-01-23)

Config editing is not recommended, GUI is the way to go.

 

Just reproduced some weirdness with clicking mouse buttons on tray icons in single tray icon mode. Investigating.

 

Confirmed. Tray icon mouse button clicks could be ignored under Win8 in single tray icon mode. The fix will be available in the next version, thanks for reporting.

 

Then those people are out of luck. There are more interesting tasks in development list than providing support for old things, sorry.

 

Hotkey engine doesn't support binding mouse buttons and I'm afraid there are no plans to support it in nearest future.

 

Nope. It is easier to implement proper cursor capture than doing such workaround.

Low chances, sorry. New NV flagman GPU is around the corner, I'm focused on supporting it, then new AMD hardware with new VRM access interface, then porting AB and OSD server to new compiler. The list is never ending and tasks like cursor, which doesn't brind many use to majority of users and don't add new selling points, have low chances to get attention.

 

1) You may official overclocking mode (which is enabled by default and doesn't require any config edits) and stay within CCC clock limits. That's the only overclocking way AMD officially supports.
2) You may use unofficial overclocking mode 2. It will remove flickering but will also kill PowerPlay so the card won't downclock in idle.
3) You may extend CCC clock limits with /XCL command line switch and keep using official overclocking mode via CCC or Afterburner.

 

Keep dreaming. ATI stay in some stupid position on overclocking during last 10 years since RADEON 9000 PRO announce back in 2002. That time they didn't even have any form of overclocking in their control panel (CCC monster was born few years later) so it was possible to overclock ATI cards with thir party tools only. RADEON 9000 PRO was the first overclocking protected card in the world AFAIR, and it gave a lot of headache to third party developers.
With it ATI applied digital signature to clock area in BIOS (to prevent BIOS editors from editing it) and added simple algorithm to reset clocks to defaults if any kind of overclocking was applied in Windows via third party tools. Some devs just gave up on overclocking it, others tried to break through ATI restrictions somehow. To bypass it RivaTuner provided ATIOverclockingAntiprotection patch script which modified driver binaries and ripped protective code from it. Similar form of runtime driver patch existed in w1zzard's ATITool.
Things didn't change that much since that time. ATI created CCC with Overdrive support, but the amount of overclock they allows is way too small even for overclocking beginners. Official API, provided by AMD to vendors for their custom OC tools development also allows overclocking up to CCC clock limit only. Going beyond it officially is a "no go" for any vendor. Extending CCC limit is only possible via flashing special BIOS, but it cannot be created by vendors themselves and it require AMD's digital signature to be applied to clock info. Vendors tried to ask ATI to allow easier overclocking many times with no luck. So every tool going beyond CCC limits uses "holes" in the driver:

- Sapphire Trixx, HIS iTurbo (both are created by my good friend w1zzard) and MSI Afterburner (with unofficial overclocking mode = 1) use undocumented Overdrive/PowerPlay table programming interface. The interface is REALLY old and it has a lot of open issues (e.g. it may reset fan speed and power limit to defaults on some cards, it is incompatible with AMD's own ULPS and may cause BSOD, it has numerous PowerPlay compatibility issues (including infamous flickering in the latest AMD drivers)). MSI Afterburner (with unofficial overclocking mode = 2) is also the same undocumented Overdrive/PowerPlay table programming interface, but it additionally sets all PowerPlay level clocks and voltages to the same values to it virtually "disables" PowerPlay.
- ASUS GPU Tweak (ASUS own internal development) and MSI Afterburner (with /XCL command line switch) may optionally use debug "hole" in AMD driver - software PowerPlay table emulation via the registry. RacerX utility also is based on software PowerPlay template generated on 69xx card by ASUS GPU Tweak. It should be used with care BTW, because PowerPlay tables are different and depend on GPU family and VGA BIOS, so adding 69xx PowerPlay table to different GPU registry may result in some unwanted side effects (e.g. changed fan speed, because it is also calibrated there).
- Fianlly, some tools (e.g. ASUS GPUTweak, PowerUp Tuner or MSI Afterburner out of box without any CFG tweaks) just allow overclocking withing CCC limits.