Thanks Unwinder. Always the best and innovative with the Afterburner.

I download beta 10 because 4.4 11 didnt work on my system. Beta 4.4 10 ran but fan curve didnt work I looked at my gpu temp it was 82c my jaw dropped WTF. Im still a bit shaken up from it. reinstalled 4.3

There are no changes in fan control implementation between 4.3.0 and 4.4.0. You did nothing with a downgrade.

I've also noticed the same thing as @Sixtyfps. The fan curve that worked fine in 4.3.0 didn't work in 4.4.0 on my (mobile) GTX 1080 (it showed the proper curve, but it didn't seem to work as the voltage was up and the clocks were at non-curve level). I reset to defaults and set the curve fresh in 4.4.0 beta 11 and it works fine again. Perhaps it has to do with the settings not transferring over properly if you update from 4.3.0 to 4.4.0 Beta 11 for some reason?

No. I have nothing to add to what I've said before. Just stay at 4.3.0 if you beleive that 4.4.0 is broken.

Can you add option to change OSD color graph in future versions?

http://forums.guru3d.com/showpost.php?p=5445730&postcount=506

Rainbow Six Siege overlay is still not working with this AB beta. It did say in the news article you guys worked with Ubisoft to get the OSD better supported, so maybe in the final version ?

Please read beta development thread. It was asked and answered a lot of times there.

look nice and intresting, not sure how usefull it would be for me though, I rarely use this these days,

Now we have something that might be able to compete with digital foundry's testing.

Loving the new features. Thanks Unwinder for your hard work with A/B i couldnt live without it.

I love this feature !!!! because i can check how visual setting affect the performance of a game. Specially frame-times. Just one suggestion can you add more steps in the adjustment of slider "on-screen display zoom" ? Because when i'm running custom resolution(downscaling). I can't precise adjust the size of the OSD. I had to manually edit the config file

I love this feature !!!! because i can check how visual setting affect the performance of a game. Specially frame-times. Just one suggestion can you add more steps in the adjustment of slider "on-screen display zoom" ? Because when i'm running custom resolution(downscaling). I can't precise adjust the size of the OSD. I had to manually edit the config file

Already implemented, please check RTSS release notes:

• Improved font size adjustment for raster 3D On-Screen Display rendering mode. Base font size (i.e. font size for 1x zooming ratio) is no longer hardcoded inside the profile, now you can adjust it directly in font selection window. After selecting the base font size you may still apply fixed 1x-8x zooming ratio to it on the fly using On-Screen Display zoom adjustment slider

Sorry for the newbie question but is there a simple way to change the voltage for the power states similar to how you do it in Wattman? I just lower the last two power states of my RX480 in Wattman to get some undervolting going but I would rather only use Afterburner. I know that you can unlock the voltage there but it was rather complicated to edit since it was much more detailed. Also I never managed to enable the CTRL+F Voltage curve. How exactly do you enable this? Any help would be appreciated.

MSI AB is not using Wattman API for voltage control on RX 4x0 series. Wattman voltage limits are pretty low so direct access to GPU on-die SMC is being used instead. SMC voltage offset is applied to all P-states at once. And V/F curve is for NVIDIA Pascal GPUs only.

This version seems to better in every way, even if its on Beta. The problem is that I dont see the frame rate decimals anymore, for example, 37.5 is now 37, 59.89 is now 59, I tend to limit my games frame rate via the Profiles folder from RivaTuner since I can tune the numbers better, but now I dont see the decimal. Any help on how to get it back on MSI Afterburner options?

The .\Profiles\Global file. IntegerFramerate=1 just set it to 0 and it should change how that displays. (Integer to float.) Should be in the changelog for the software but it might be buried a bit in the ongoing RTSS 6.7.0 (Now 7.0.0) beta topic in the Rivatuner forum section. 🙂 EDIT: If it's not part of the user "Global" files you can just copy the setting from the .\ProfileTemplates\Global file, that one will be overwritten when RTSS is updated thus copying the setting to the user file prevents any changes from being lost if it had been edited directly.

Nice software. However, I have given up on overclocking or under clocking my R9 Fury cards, it was just to much of a hassle. They run fine on their own as they are anyways.

Bios OCing goes a long way for our Fury's

The .\Profiles\Global file. IntegerFramerate=1 just set it to 0 and it should change how that displays. (Integer to float.) Should be in the changelog for the software but it might be buried a bit in the ongoing RTSS 6.7.0 (Now 7.0.0) beta topic in the Rivatuner forum section. 🙂 EDIT: If it's not part of the user "Global" files you can just copy the setting from the .\ProfileTemplates\Global file, that one will be overwritten when RTSS is updated thus copying the setting to the user file prevents any changes from being lost if it had been edited directly.

No need to edit it directly, there is an option for toggling integer/FP framerate output in RTSS properties.

Oh I must have missed that but that's easier then, shows how often I check the config settings in the actual software compared to just diving into the file heh. 🙂

This is good!

No need to edit it directly, there is an option for toggling integer/FP framerate output in RTSS properties.

I need your help and who better to ask than the creator of RivaTuner? I have the Witcher 3 (legit game by the way) and my computer, even if it can hold 60 fps, is not always possible in the game, my monitor is 75 Hz or 75.004 for more precise numbers, I discovered that the game works wonderfully and very smooth with nVidia half refresh rate at 37.5 fps, not single fps drop. I used RivaTuner to get correct frame time, I did this: [Framerate] Limit=37504 LimitDenominator=1000 The game works wonderful, except when the frame decimals start to fight each other; when in the game, it goes 37.5, 37.4, 37.5, 37.4 and it does create some small stutters from time to time, I have found out that 37.4 26.6 ms seems to works better (it should not, but it does): [Framerate] Limit=37499 LimitDenominator=1000 That way, the frame rate is 37.4 all of the time, but I think the image is not a 100% stable, seems to have extremely small stutters, maybe its just me seeing things, but I think its there. At 37504 is 100% smooth except when the frame time decides to fight with 37.4, then 37.5, this is completely random and can happen at any moment. How can this be solved? Witcher 3 is the only game that presents this issue or at least, very, very often, I have seen it in other games, but like 1 or 2 times every 5 minutes, Witcher 3 is often, happens at any place. Can you help me?