MSI Afterburner 2.2.0 Beta 9 (2011-11-24)

great job! thx Unwinder !

 

Just two words: it works. :thumbup:

 

Unwinder, forgive my noob question

there's a way to set individual applications and not globally?

 

Thanks, this is the perfect Christmas present. Also, I can finally tell people to stop installing dxtory just to limit the framerate.

 

:nerd: Indeed I tried to configure the individual game profile and works well !!! Thanks !!!

 

I extracted the .RAR into MSI Afterburner's folder, and this is what I get when I try to launch the program now;



I have also tried uninstalling, and installing it again, and same issue persists.

Any ideas?

 

Extract it to the OSD server's directory. Default path for that is: C:\Program Files (x86)\MSI Afterburner\Bundle\OSDServer

 

Hmm i have weird problem with this latest beta. If i use osd my framerate drops after 10-15mins of gaming. Like as an example if i play f1 2011 at start of the game i get 90fps but suddenly after 10-15mins fps has dropped to around 70. Without AB running in backround i dont get that fps drop so anyone has idea what could reason for that to happen?

 

Ouch! Thanks a lot!

 

This works like a beast! Steady 62fps all the time in Battlefield 3 maxed out, a lot smoother than using the in-game fps limiter (which would stutter like crazy) or bandicam (which would freeze my game as soon as I enabled the fps limiter).

Thank you guys! Love it! no more wasting GPU usage, heat, or noise when I don't need it!

 

I must admit, I'm slightly confused here...... What are the benefits by limiting your frame-rate with Afterburner than by lets say using d3do to enable Vsync and Triple Buffer? Or am I supposed to use Afterburner's frame-rate limiter and d3do's TB? Or is d3do suddenly "bad"?

All in all the OSD functions work like a charm Just not sure of the benefits of using them over something else. (sorry for my noobness )

 

A simple google search would answer your question about the difference between vsync and a framerate cap. There's no such thing as d3doverrider suddenly being bad. These are two entirely different things that address different issues. I'm not going to reward your laziness with a long comprehensive answer.

 

*sigh* I know the difference between Vsync (telling the graphics card it can only update after the monitor refreshes, therefore eliminating tearing) and a frame-rate cap. I was simply asking if there were benefits using one over the other (or if its possible to use both)

I have always been a person to use Vsync with Triple-Buffer enabled through D3DO, came across this new feature in Afterburner, and wondered if it was something that could be more beneficial to me than my current method.

Its interesting though that you refer me to search for something in a search engine when the main purpose of a forum (which last I knew this still was) is a place to gather and share information on subjects to which the forum pertains to. (in this case the beta frame-rate limiter now available for Afterburner)



Related Note: Was playing around with the frame-rate cap and did notice that, at least for me, Section 8: Prejudice did not want to launch if ran with the beta OSD files present. (could have been D3DO however, might have forgotten to shut it off, need to do more testing)

 

All the information you'd need about framerate caps are already here.

 

ok fine, well, if anyone else is curious, from what i gathered the main downside to Vsync is it introduces input lag (even though I have yet to notice) and the frame-rate cap does not introduce any extra lag however may not fully eliminate tearing.

I guess now the question is will this limiter become obsolete when NV finally releases its in-driver limiter.

 

So then if you don't video capture, you don't really need/want to stop using what you were using? (in my case D3DO) I did like being able to limit FPS to 45 to help with cooling, but did not like the occasional tearing that occurred. (but it was much better than having no limit at all)

Well, I guess I'll just continue to use D3DO for now and pray that the latency that Vsync can possibly bring doesn't rear its ugly head. Too bad there is no way to limit Vsync (like telling Vsync instead of capping at 60 to cap at 45 or something)

(UPDATE: Im sticking with the frame-limiter for now, got addicted to using the OSD and like the readout on my G15 keyboard, just can't seem to use D3DO and the OSD program at the same time, at least in S8: Prejudice, the game just refuses to launch. Havn't tried any other games yet however. Happens with the OSD program that came with 2.2.0 Beta 9 and the frame-limiter beta version)

Too bad about NV's version only overriding OpenGL, that severely limits functions in the CP.

To keep the thread on topic: Other than some noobish confusion on my part, I have had no issues with Beta 9 (other than the update described above) Can't wait till 2.2.0 comes out of beta, or Beta 10 comes :nerd:

Thanks Unwinder for the info!

UPDATE 2: with the beta RTSS.exe, I cannot seem to turn off the OSD program (well, I can close it, but then it just comes right back) without killing the Afterburner process as well, not sure if this is intended or not. Prior to installing the OSD beta I could close it fine.

 

Although we don't get along, this is seriously nice work

Well done!