MSI Afterburner 2.2.0 Beta 12 (2012-02-02)

msi-afterburner · *Last edited by msi-afterburner; 02-02-2012 at 03:40.*

Hi guys, today we have another update of MSI Afterburner 2.2.0 beta 12, do you guys find the Beta 11 already support HD 7950? If not, you can also use the Beta 12 to support HD 7950! There is another new GPU (5500+2270? lol) is supported by Afterburner 2.2.0 Beta 11/12, try to run it with Afterburner!

Changes list includes:

- Memory clock limit has been extended to 180% on AMD RADEON 79x0 graphics cards in unofficial overclocking mode
- Added low-level clock frequencies monitoring for AMD RADEON 79x0 graphics cards
- Added PowerTune adjustment slider for AMD HD 6xxx and 7xxx series graphics cards
- Improved overclocking profiles format provides compatibility with future graphics cards. Please take a note that existing overclocking profiles (startup overclocking profile and profile slots) will be ignored and must be recreated in new version
- MSI On-Screen Display server has been upgraded to v4.3.2. New version gives the following improvements:
o Added gamma corrected video capture support
o Framerate limit ratio for video capture in no longer controlled via the server's profiles. Now it can be adjusted directly into MSI Afterburner's video capture properties
o Added Direct3D9Ex support (DOTA 2 and Darkness 2 demo)
o Improved desktop windows notification mechanism eliminates unwanted beeps occurring on some systems during the server startup / shutdown
o Output video dimensions are now cropped to be multiple of 16 to improve compatibility with some third party MJPG decoders
o Improved OpenGL On-Screen Display coordinates calculation for framebuffer coordinate space mode
o Now "Enable compatibility with modified Direct3D runtime libraries" option is compatible with Direct3D9 game engines using double FPU precision (MassEffect series)

download link:
http://downloads.guru3d.com/MSI-Afte...load-2850.html

erm · 02-02-2012, 04:30 | posts: 350 | Location: Italia

Thanks ! Now install it...

Conrad.TDI · 02-02-2012, 04:39 | posts: 23

wow! Very quick update. Thanks as usual for the efforts.

TFL Replica · 02-02-2012, 05:29 | posts: 357

Thanks for the update.

Olvik · 02-02-2012, 06:28 | posts: 138 | Location: Spain

Thanks

IMaysky · 02-02-2012, 06:34 | posts: 40

Cool. Thanks.

AMD@OPA · 02-02-2012, 07:15 | posts: 14 | Location: Germany

Thanks !

GAR818 · 02-02-2012, 07:44 | posts: 1,076 | Location: LOS ANGELES

Thanks for this software Unwinder, amazing stuff. And its free and works for every graphics card. Honestly if it wasnt for you and your great software, we would be stuck with some mediocre effort by the other guys. Thanks again and PM me your email address so i can donate some money through paypal.

msi-afterburner · 02-02-2012, 08:11 | posts: 401

Quote:

Originally Posted by GAR818

Thanks for this software Unwinder, amazing stuff. And its free and works for every graphics card. Honestly if it wasnt for you and your great software, we would be stuck with some mediocre effort by the other guys. Thanks again and PM me your email address so i can donate some money through paypal.

Purchasing the msi graphics card is the best support to alexey and msi

GAR818 · 02-02-2012, 08:21 | posts: 1,076 | Location: LOS ANGELES

Quote:

Originally Posted by msi-afterburner

Purchasing the msi graphics card is the best support to alexey and msi

I own a local computer store in Burbank, CA, ive purchased over 500 MSI boards and graphics cards in the last 2 years

PirateNeilsouth · *Last edited by PirateNeilsouth; 02-02-2012 at 07:56.*

ERROR OPENING FILE FOR WRITING

RTSSHooks.dll

EDIT : Fixed, had to uninstall msi afterburner and reboot system because of a file couldn't be removed, never had that before

TFL Replica · 02-02-2012, 07:58 | posts: 357

Quote:

Originally Posted by PirateNeilsouth

ERROR OPENING FILE FOR WRITING

RTSSHooks.dll

EDIT : Fixed, had to uninstall msi afterburner and reboot system because of a file couldn't be removed, never had that before

This occurs if an application that used the OSD does not close properly. You didn't have to uninstall or reboot your system.

PirateNeilsouth · 02-02-2012, 08:10 | posts: 1,612 | Location: Manchester

Quote:

Originally Posted by TFL Replica

This occurs if an application that used the OSD does not close properly. You didn't have to uninstall or reboot your system.

That's what the software told me to do :p

Anyway it only took a few seconds

Simplex · 04-21-2012, 14:11 | posts: 53 | Location: Poland

Quote:

Originally Posted by TFL Replica

This occurs if an application that used the OSD does not close properly. You didn't have to uninstall or reboot your system.

So what is the solution in that case? What is the process/serice name that has to be closed in order to fix the problem?

OmegaRED · *Last edited by OmegaRED; 02-02-2012 at 08:04.*

Is it possible to have 2 separate user defined fan profiles?

For example I would like one for my 6990 and another for the 6970 but it seems that if I make one for the 6990 it is automatically applied to the 6970.

Unwinder · 02-02-2012, 09:34 | posts: 10,312 | Location: Taganrog, Russia

Quote:

Originally Posted by OmegaRED

Is it possible to have 2 separate user defined fan profiles?

For example I would like one for my 6990 and another for the 6970 but it seems that if I make one for the 6990 it is automatically applied to the 6970.

No, user defined fan curve is a global setting for all GPUs.

OmegaRED · *Last edited by OmegaRED; 02-04-2012 at 22:17.*

Quote:

Originally Posted by Unwinder

No, user defined fan curve is a global setting for all GPUs.

It would be very useful to have user defined fan curves linked to each gpu since many people use a mix of aftermarket and reference coolers on their multi-gpu setups. It's such an odd limitation given you can have separate fan speeds for each gpu why not add in the custom curve too.

ElGreco · 02-10-2012, 23:42 | posts: 39

XCL Command in 7970 Crossfire setups

It seems that the /xcl command unlocks only the limits of GPU1 in my CCC. What command should i use to extend the limits also of GPU2 in CCC?

Thank you...

slickric21 · 02-11-2012, 01:04 | posts: 1,681 | Location: U.K

I've noticed that my 7970 wont downclock to 300mhz /.85v after using AB (to load an OC profile) instead it only drops back to 500mhz /.95v untill a reboot is done.

is this normal ?

Unwinder · 02-11-2012, 05:39 | posts: 10,312 | Location: Taganrog, Russia

Quote:

Originally Posted by ElGreco

XCL Command in 7970 Crossfire setups

It seems that the /xcl command unlocks only the limits of GPU1 in my CCC. What command should i use to extend the limits also of GPU2 in CCC?

Thank you...

It is clearly declared in the readme that XCL command line switch only affects AMD graphics cards attached to Windows desktop. So before unlocking clock ranges temporary disable CF and extend desktop on each card you want to be unlocked.

Xzibit · 02-02-2012, 11:19 | posts: 4,383 | Location: Europe

Thank you!

solidsteel144 · 02-02-2012, 11:24 | posts: 71 | Location: Texas

Is it possible to go beyond the +20% slider limit for PowerTune?
Just curious.

Awesome update BTW.

Darkasantion · **Memory**: OCZ 2x2GB @ 548 5-5-5-15

Quote:

Originally Posted by solidsteel144

Is it possible to go beyond the +20% slider limit for PowerTune?
Just curious.

Awesome update BTW.

Where do you find that slider btw? Did have a quick look, but can't find it anywhere in Afterburner, yet got 2 HD6970's in Crossfire, so it should work I assume

.

solidsteel144 · 02-02-2012, 11:55 | posts: 71 | Location: Texas

Quote:

Originally Posted by Darkasantion

Where do you find that slider btw? Did have a quick look, but can't find it anywhere in Afterburner, yet got 2 HD6970's in Crossfire, so it should work I assume

.

Settings/General Tab towards the bottom.

Unwinder · 02-02-2012, 13:18 | posts: 10,312 | Location: Taganrog, Russia

Quote:

Originally Posted by solidsteel144

Is it possible to go beyond the +20% slider limit for PowerTune?
Just curious.

Awesome update BTW.

Nope, there is a limit in BIOS for CCC and all third party tools similar to clock limits. But theoretically it is possible to fake PowerTuner limit in PowerPlay table emulation via registry similar to what /XCL command line switch is doing with clocks.