MSI Afterburner 2.2.0 Beta 14 (2012-02-21)

msi-afterburner · **MSI Afterburner 2.2.0 Beta 14 (2012-02-21) -** 02-21-2012, 08:20 | posts: 402

Hi guys, the latest afterburner 2.2.0 beta 14 is ready for you to download. Yes, you are right, there is no beta 13.

Anyway, this beta supports the voltage control of HD 7X50 card, if you get the card, you may try to play it.

Changes list includes:

- Fixed sub-zero temperatures reading on certain custom design MSI graphics cards with LM96163 and NCT7718W dedicated thermal sensors.
- Added workaround for bug in AMD drivers causing unofficial overclocking to be reset to defaults after adjusting PowerPlay settings. Now unofficial overclocking settings are being forcibly reapplied after applying new PowerPlay settings.
- Hardware abstraction layer (HAL) architecture has been improved to provide compatibility with future NVIDIA graphics cards series.
- Now multi-GPU overclocking and fan control settings synchronization is performed at HAL level instead of display driver wrapper level to improve HAL architecture extendibility and provide compatibility with future NVIDIA graphics cards series.
- Shared control memory format has been upgraded to v2.0. New format provides power limit adjustment support and forward compatibility with future NVIDIA graphics cards series.
- Now it is possible to override group names for values displayed in the On-Screen Display or in Logitech keyboard LCD display.
- MSI On-Screen Display server has been upgraded to v4.3.3. New version gives the following improvements:
o Fixed issue causing gamma correction to be applied twice under certain conditions and causing video to appear too bright when capturing video with gamma correction option enabled.
o Output video dimensions are no longer being forcibly cropped to be multiples of 16. Now cropping is optional and can be enabled via GUI
o Dedicated 1/2, 1/3 and 1/4 frame downsampling routines have been replaced with unified arbitrary downsampling routine. Now MSI Afterburner provides arbitrary frame downsampling functionality and allows selecting 360p, 480p, 720p, 900p, 1080p frame sizes for both 16:9 and 16:10 aspect ratios. Please take a note that arbitrary frame sizes list is user extendable so you may add your own custom frame sizes if necessary via the configuration file.
o Improved tabbed text formatting provides better compatibility with custom group names.

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

PhazeDelta1 · 02-21-2012, 08:23 | posts: 9,349 | Location: 90° N

awesome.

BetA · 02-21-2012, 08:55 | posts: 3,380 | Location: somewhere behind the Milky Way

lol, WHat happened to Beta 13? or wasnt there a version 13 after all? did they skipped it?

anyway, THX for the new version

Hilbert Hagedoorn · 02-21-2012, 09:21 | posts: 16,989 | Location: Guru3D testlab

Quote:

Originally Posted by BetA

lol, WHat happened to Beta 13? or wasnt there a version 13 after all? did they skipped it?

anyway, THX for the new version

13 is bad luck, we have never released a build with 13 in it.

TFL Replica · 02-21-2012, 09:32 | posts: 357

Downloaded, updated and tested. Captured a nice 720p video in Skyrim.
I also peeked into the configuration file: 16:9 720p,050002D0h -> 0500=1280 and 02D0=720
This should preemptively answer a lot of questions. It's very easy for anyone to add custom frame sizes.
Thanks for another great release!

WhiteLightning · 02-21-2012, 09:36 | posts: 20,490 | Location: Netherlands

Nice update! Thanks!

Olvik · 02-21-2012, 11:12 | posts: 138 | Location: Spain

Thanks!

stangowner · 02-21-2012, 11:52 | posts: 562 | Location: MA

Quote:

Originally Posted by msi-afterburner

- Shared control memory format has been upgraded to v2.0. New format provides power limit adjustment support and forward compatibility with future NVIDIA graphics cards series.

Hi Alex,

I tested the remote server and .net wrapper this AM to make sure they were fine. I can read the memory properly, but can't apply changes. In examining my code, I do think I have a memory offset miscalculation for writing memory in multi-gpu systems (reading is OK). However, even after correcting this, I still can't apply the changes. After scratching my head a little more, I decided to test the SDK sample and that doesn't work neither. Afterburner says an external profile was applied, but no changes to the hardware are made (same result from both from the SDK sample and my stuff). Can you reproduce? Or am I just missing something here?

Also, I'd like to update the .NET library, remote server and mobile apps shortly for the 3 new settings added in v2. Can I emulate those yet, or do I need to wait? If so, can you send me a config to use?

Thanks,
Nick

Xzibit · 02-21-2012, 12:09 | posts: 4,383 | Location: Europe

Thank you, sir!

Unwinder · 02-21-2012, 12:34 | posts: 10,323 | Location: Taganrog, Russia

Hi Nick,

Quote:

Originally Posted by stangowner

Hi Alex,

I tested the remote server and .net wrapper this AM to make sure they were fine. I can read the memory properly, but can't apply changes. In examining my code, I do think I have a memory offset miscalculation for writing memory in multi-gpu systems (reading is OK). However, even after correcting this, I still can't apply the changes. After scratching my head a little more, I decided to test the SDK sample and that doesn't work neither. Afterburner says an external profile was applied, but no changes to the hardware are made (same result from both from the SDK sample and my stuff). Can you reproduce? Or am I just missing something here?

Thanks, I reproduced and fixed it. The problem is not specific to beta 14, it was introduced in beta 12 during profiles format change. The fix will be available in the next version.

Quote:

Originally Posted by stangowner

Also, I'd like to update the .NET library, remote server and mobile apps shortly for the 3 new settings added in v2. Can I emulate those yet, or do I need to wait? If so, can you send me a config to use?

You cannot emulate those things yet, wait for next gen hardware to arrive.

nuno_p · 02-21-2012, 12:35 | posts: 84 | Location: Portugal

Thanks.

I was waiting for this.

stangowner · 02-21-2012, 12:46 | posts: 562 | Location: MA

Quote:

Originally Posted by Unwinder

Hi Nick,
Thanks, I reproduced and fixed it. The problem is not specific to beta 14, it was introduced in beta 12 during profiles format change. The fix will be available in the next version.

You cannot emulate those things yet, wait for next gen hardware to arrive.

Thanks for the quick reply Alex!

AMD@OPA · 02-21-2012, 12:48 | posts: 14 | Location: Germany

Thanks!

erm · 02-21-2012, 16:42 | posts: 352 | Location: Italia

Thanks !

Unwinder N. 1 !

DavidGX · 02-21-2012, 17:04 | posts: 41 | Location: USA

Quote:

Originally Posted by Hilbert Hagedoorn

13 is bad luck, we have never released a build with 13 in it.

/facepalm

GhostXL · 02-21-2012, 17:06 | posts: 4,923 | Location: PA, USA

Hey I've lived in house number 13 on my block for over 20 years. I've been blessed every day, through hardships as well.

That superstitious stuff was always just that, superstitious stuff.

After all the US was originally 13 colonies!

Back on Topic,

Thanks for this release, will give it a run!

kmartburrito · 02-22-2012, 03:59 | posts: 3 | Location: Colorado

This version along with the 12.3 Preview drivers (Feb 14th) I'm finding is that while I messed around with things and got both 6950s to be at +20% power, that one card is only going to 800 / 1250 (or whatever is default, I can't remember) while the other is going to 840 / 1325 like I would expect.

I've gone in and checked that the EnableUlps reg keys are all set to 1 like I've always done, but just noticed it while playing a game and looking at Afterburner's line graphs afterwards.

I will say that the couple of games I played so far I'm impressed with the drivers, just wondering if it's truly not clocking both cores and memory freqs properly on both 6950s, or if it's just misreporting it. It shows in CCC correctly.

Anyone else with a crossfire setup seeing any of this?

johnnyw · 02-22-2012, 04:18 | posts: 4

Im having weird thing with this version and HD7950 + 12.2 pre cert drivers.

In some reason i cant be able to overclock single mhz from afterburner if i dont raise the power control to 20%. lets say i put 1000/1575 at stock volts from AB and launch any game/program my clocks are jumping all over the place ( throtthling ) but after i set it to 20% it works fine.

If i do same overclock from CCC i can leave powercontrol to stock 0% it dont do the throtthling. Not big deal really but just wondering what could cause that?

Unwinder · 02-22-2012, 05:58 | posts: 10,323 | Location: Taganrog, Russia

Quote:

Originally Posted by kmartburrito

This version along with the 12.3 Preview drivers (Feb 14th) I'm finding is that while I messed around with things and got both 6950s to be at +20% power, that one card is only going to 800 / 1250 (or whatever is default, I can't remember) while the other is going to 840 / 1325 like I would expect.

I've gone in and checked that the EnableUlps reg keys are all set to 1 like I've always done, but just noticed it while playing a game and looking at Afterburner's line graphs afterwards.

I will say that the couple of games I played so far I'm impressed with the drivers, just wondering if it's truly not clocking both cores and memory freqs properly on both 6950s, or if it's just misreporting it. It shows in CCC correctly.

Anyone else with a crossfire setup seeing any of this?

Is sync option ticked and do you look at idle or load clocks?

HarryYTM · 02-22-2012, 10:55 | posts: 27 | Location: Hong Kong

Bug report: Video capture timer bug on the OSD still not fixed, the timer would add 1 hour in each 6 minutes, that means 0:05:59, XXXMB, X.Xx XXms then become 1:06:00, XXXMB, X.Xx XXms in just one second.

Unwinder · 02-22-2012, 11:18 | posts: 10,323 | Location: Taganrog, Russia

Quote:

Originally Posted by HarryYTM

Bug report: Video capture timer bug on the OSD still not fixed, the timer would add 1 hour in each 6 minutes, that means 0:05:59, XXXMB, X.Xx XXms then become 1:06:00, XXXMB, X.Xx XXms in just one second.

It is not fixed because it has never been reported before. Will fix it, thanks.

OmegaRED · 02-22-2012, 17:32 | posts: 30 | Location: Ottawa, Canada

I'm getting a bug with this version with 2D/3D profiles on multiple GPU's. It keeps forcing 2D fan speeds on the 3D slot when I set both my GPU's 25%/Auto and then close it that changes to 25%/25% which is bad news for 3D gaming. Unlinking has no affect.

DStealth · **Memory**: KHX 3x2G@2.1Ghz 9-9-9-21

Hi Alex,
I'm having problems with the new build, after //XCL and then //RCL
My card(ref7970) is getting lower clocks than, if i hit reset botton ..strange
It's idling 300/150 now, before it was 500/150...but that's not the only problem,if we can even say it is

Is't lowering it's core clocks even in 3d in very low intervals, it's not on the limit OC or smth throttle related...tested several combinations, the same
Here is a Pic, is there any way to fix that abnormal behavior?

Only thinks changed in CFG after installing that build was those 2 settings:
[ATIADLHAL]
UnofficialOverclockingEULA = 1
UnofficialOverclockingMode = 1
And //XCL command applyed

Unwinder · 02-23-2012, 07:01 | posts: 10,323 | Location: Taganrog, Russia

Quote:

Originally Posted by OmegaRED

I'm getting a bug with this version with 2D/3D profiles on multiple GPU's. It keeps forcing 2D fan speeds on the 3D slot when I set both my GPU's 25%/Auto and then close it that changes to 25%/25% which is bad news for 3D gaming. Unlinking has no affect.

I'd like to see your profiles (contents of .\Profiles\VEN_.....cfg files).

Unwinder · 02-23-2012, 07:08 | posts: 10,323 | Location: Taganrog, Russia

Quote:

Originally Posted by DStealth

Hi Alex,
I'm having problems with the new build, after /xcp and then /rcp
My card(ref7970) is getting lower clocks than, if i hit reset botton ..strange
It's idling 300/150 now, before it was 500/150...but that's not the only problem,if we can even say it is

Is't lowering it's core clocks even in 3d in very low intervals, it's not on the limit OC or smth throttle related...tested several combinations, the same
Here is a Pic, is there any way to fix that abnormal behavior?
...
Only thinks changed in CFG after installing that build was those 2 settings:
[ATIADLHAL]
UnofficialOverclockingEULA = 1
UnofficialOverclockingMode = 1
And /rcp command applyed

See no problems besides classic PowerTune in action. Inclrease power limit to get rid of throttling. And please carefully read unofficial overclocking EULA which you had to type in into CFG instead of 1.