That's my personal decision.

heh ? so what are we gonna do in this Forum then ? Watching you explain to people how search would have solved their problem faster is hardly entertaining :3eyes:

heh ? so what are we gonna do in this Forum then ? Watching you explain to people how search would have solved their problem faster is hardly entertaining :3eyes:

As opposed to? answering the same questions all the time? Yeah search is good

If you think a bit and read a bit you'll find out that it is supposed to be so.

Beta 19 bug report: when 64-bit OSD is enabled and active, AB would open the 32-bit VFW codec config UI instead of 64-bit one. at least it happens with x264vfw 64-bit.

Look at that option: https://dl.dropboxusercontent.com/u/24826668/RTSS_properties.png

It doesn't affect that and it was clearly declared that 32-bit application (MSI AB) will be able to configure 32-bit VFW codecs only. That's by design.

Why brother it is beta or not as long as it works for you?? Why not stop arguing and then help Unwinder to nail out all the bugs instead which helps ending beta phase. Time-bomb was what you accepted since you install beta version of AB, if you don't like this term given by MSI or author of this program, please feel free to uninstall it, no one forced you to use beta AB.

MSI Afterburner (BETA) is supplied with my graphics card so I can use it properly as advertised by MSI. The beta is the only version that supports my card. When does the version of Gigabyte OC Guru supplied with YOUR graphics card expire?

How often Gigabyte give their clients major software updates with new features for free? Let me hint: never, genius. Seriously, stop that, you're one of few "smart" persons DIRECTLY responsible for stopping MSI AB public beta testing approach. Be proud of your achievement and please go to some different place destroying something else.

How often Gigabyte give their clients major software updates with new features for free? Let me hint: never, genius. Seriously, stop that, you're one of few "smart" persons DIRECTLY responsible for stopping MSI AB public beta testing approach. Be proud of your achievement and please go to some different place destroying something else.

I disagree. MSI are entirely responsible for whatever they release.

Some geniuses are unable to understand that there are no MSI reps here at Guru3D

Please don't feel offended when I comment on MSI Afterburner. I am criticizing MSI. I have said (as a lot of others have done) that MSI Afterburner is completely stable enough to not be beta. I don't understand why it is not. I am not asking and do not expect an answer from you Unwinder as I understand you do not represent MSI. PS. Last release of OC GURU was 10-4-14 🙂

Is it still Ukrainian software or already Russian? I believe Ukrainians don't have balls to fight against attacker.

NOT cool

MSI Afterburner is set to use the default clock settings on windows start up and fan at 65% but it isn't sticking.

Have you seen this? "Afterburner doesn't always apply overclock settings on boot? - Guru3D.com Forums" Seems like could be the same root cause.

I'm getting ctask error pop up running this. Still it runs fine.

I'm getting CTaskSchedulerInterface:AddTask failed with error code - 22 !. Afterburner will not Auto start when Windows load even though I applied it. I have to start manually. When I exit Afterburner that's the message I get. Some setting in Windows that im missing ?

Blame the driver, it is broken in other tools as well. http://obsproject.com/forum/threads/obs-nvenc-337-50-driver.13244/

We will investigate

Thanks a lot, Manuel!

Unwinder, did you already get a subscription to the closed beta, or will you wait until it is open to all devs?

Can you guys add voltage control for amd r9 270x? asus gpu tweak and trixx have but msi ab is better

The whiner's are basically people who primarily play console games. They have no understanding that if you opt-in to use a beta version, you can always go back. Beta numbers and stable numbers makes one feel incomplete and complete. They do not understand Beta versions mean "new" and "helpful" features, while sorting out bugs (if you are using a computer, you basically sign your soul away to coming into contact with bugs/errors). That being said, If the personal issue was related to the whiner's and MSI wanting their genitals to be stable and force you to release said stable version, does that mean you are submitting yourself to them? Screw them!... If you release said stable version and stop there (if you're under contract, then it's kind of an "I told you so" when you are dealing with big corporations), go back to RivaTuner and do what you like under your own terms!... "The Devil is in the Details" I respect the hell out of your work for what you have done with RivaTuner, Precision, and AB. But I knew that once your work was being involved into products for certain vendors, it meant the artist's mind is now locked up in a cage. Computing is so new that you can start something on your own and keep it your own while staying profitable. I'd pay for an up-to-date RivaTuner if I knew no one was holding you hostage. A paid version for beta access and free version that only contains stable releases (the way you weed the true supporters and customers over the whiner's while giving the whiner's something to chew on). MSI AB was the best for a reference graphics card and thats why out of precision and RivaTuner I have always been using AB. If only you could indefinitely go back to doing work for yourself and not for someone else's pleasure. I am sorry for bringing this up again, but there is nothing better out there to monitor the health of your gaming PC.

But you can try using HWiNFO to monitor+showing it on OSD>

Yes, that's a good combination. I use AB and HWINFO since a long time without any problems for desktop ... http://abload.de/thumb/desktopikqdw.jpg ... and in game. http://abload.de/thumb/gameg1ogk.jpg ablev

bug report: OSD is not showing in Daylight x64.

bug report: OSD is not showing in Daylight x64.

it works, you just cant use nvidia Ambient settings (the last settings. turn off the smoke and cloth setting to off and close game. re-open. boom OSD works. there is an issue with the Nvidia physX using different libraries (dx 10 and 11) at once. not sure unwinder would know. Similar issue happened with Call of duty Ghosts when trying to use the dynamic fur and Turbulence setting.