bdary
I recently switched from PrecX and went with the latest AB beta release.  The frame limiter feature has been working flawlessly.  I leave AB running along with Riva tuner.  And it even supports 64bit games...

Never mind ... I am reading challenged.
 

It's the "Frame Limiter" in the Riva Tuner that I started using recently.  There is no Frame rate target in AB that I've seen.  I just looked back at my last post to make sure I didn't type wrong...
 
BTW, I'm using version 3.0 Beta 18 right from GURU3D.com >> http://www.guru3d.com/files_get/msi_afterburner_beta_download,20.html
 

I had the same problem as Jarv0 and followed all the tips recommend in this forum. Un-Installing GeForce Experience was the only thing here that was able to get my "Target Frame Rate" to load on startup like it should have done in the first place
 
Good luck Jarv0 !

I don't think this is anything to do with evga precision. I think the programs just flips the switch for the drivers to do it. It's the nvidia drivers that are buggy. I don't even use evga pricision of riva tuner. I use nvidia inspector, which just tells the drivers to limit the frame rate.
 
I would just use another non-driver level frame rate capper like dxtory or rivatuner, but the timing of such cappers isn't very precise and can cause the illusion of a kind of stuttering in tomb raider, in particular. The nvidia driver level capping is excellent (single tear licking up screen, rather than multiple tears and bands of 30 fps within 60 fps frame rate which is what you get with dxtory etc). Alas the driver level capping keeps switching off after about 15 minutes, like someone else said..
 
Anyway, a driver that works with frame rate limiter is driver 327.23 (Maybe some after that, but I think from september driver onwards, it's all broke) you can also cap lower than the refresh, without vsync disabling too.
 
I am taking wild guess that this whole frame rate limiter not working and vsync not working  with frame rate limiter, is actually something to do with drivers support for G-Sync, but I'm probably wrong. I just can't think of a reason that this sort of thing would not work, especially the standard vsync disabled by capping at or lower than refresh (there's just no reason when they already had that nailed with adaptive vsync, if people wanted it. Why on earth make that not work and act like it's a functional feature, when it's clearly not and simply takes features away from advanced users?)

i cant seem to get the Frame Target working correctly (at all)
 
like if im in Dishonored,
frame target activated to 60fps
the clock speed makes no changes, stays at like 1100mhz @60fps
 
if i manually subtract 1000mhz(the max amount)  for a speed of 324mhz or so i still run 60fps perfectly fine
 
how do i set up my system, so that i run the lowest  workload possible for a streamlined 60 fps?
 
from what i read. Frame Target, was supposed to dynamically change the core clocks up and down 
so it ramps up the card if i cant hit my set limit
backs off the card if i can play at said limit no issue
 
with evga precision x even the osd is hit or miss for no apparent reason,
sometimes it works sometimes it doesnt