• Competitor rules

    Please remember that any mention of competitors, hinting at competitors or offering to provide details of competitors will result in an account suspension. The full rules can be found under the 'Terms and Rules' link in the bottom right corner of your screen. Just don't mention competitors in any way, shape or form and you'll be OK.

AMD Working on "Dynamic Frame Rate Control" Feature

Well considering forcing V-snc doesn't work reliably in the driver I wouldn't hold your breath on this actually working and being reliable.

Forcing V-snc in the driver on AMD does not work for DX since Vista, its for OpenGL only, frame limiter is not Vsync.

Vsync was changed rather a lot when Vista & Win7 came out. Before then the OS desktop was not vsync'd so it was a lot easier to alter the vsync state for apps since you didn't have the desktop manager in the background screwing things up. Microsoft also said that they didn't want vsync to alter Aero so they made it more difficult too. Both RadeonPro and ATI Tray tools and other things like that use hacks which go against what is the the WDDM spec. Nvidia also do this so their drivers shouldn't be WHQL certified IMO.

Forcing Vsync on or off globally can bugger things up for quite a few apps which is why AMD did not go the same route as Nvidia and ignore the WDDM spec & Microsoft guidelines. Now that there will be app specific profiles there should be no reason to not allow it to be forced on or off for a particular app so I have asked AMD to take another look at it which hopefully they will do.
http://www.rage3d.com/board/showthread.php?t=33984337&highlight=Vsync
 
I couldn't game without a FPS limiter as I often lock to 30fps when I can't hit 60 and I want the absolute maximum settings. I find myself doing it more and more with newer releases that need ridiculous power to hit 60 at the higher settings. Can't stand tearing (AT ALL) and V-Sync below 60 feels like 15fps. I honestly don't know how people game at anything that isn't 30 or 60. How they stand the judder and micro-stutter I will never know.
 
I've wanted AMD to do something like this for a while, a kind of equivalent for NVidia's "Adaptive V-Sync".

I'm interested to know if there's anything more to it than a simple frame rate limiter though.
 
I couldn't game without a FPS limiter as I often lock to 30fps when I can't hit 60 and I want the absolute maximum settings. I find myself doing it more and more with newer releases that need ridiculous power to hit 60 at the higher settings. Can't stand tearing (AT ALL) and V-Sync below 60 feels like 15fps. I honestly don't know how people game at anything that isn't 30 or 60. How they stand the judder and micro-stutter I will never know.

Sounds like you need gsync/freesync in your life :)
 
Sounds like you need gsync/freesync in your life :)
I think we all do!

I hate tearing too, though I think if you can maintain 60fps 90% of the time adaptive vsync is not a bad compromise in the mean time. I notice tearing most not much is happening, less likely to notice when it's all blowing up around me and the rate drops.

Running monitor at 50hz is another compromise I have tried out, still fairly fluid.
 
coming from my 560ti to this 270x im really missing adaptive vsync. in a lot of games i like vsync on but there are times the card cant do 60fps but could manage 55fps and suffers the vsync penalty. but adaptive vsync is fantastic. if amd can implement that then my next gpu purchase would not be a guaranteed nvidia card.
 
The days of having to disable ULPS are gone with Hawaii. It can still be beneficial from a performance, monitoring and overclocking perspective to disable it though. However it's not essential in some cases like it used to be on Tahiti.
 
Two things I'm interested in: Will this function properly with overclocked cards? Presumably it'll just flop down to 2D clocks at low load points, so shouldn't be an issue, but we'll see if that is the case.

Also, considering clocks jumping around can cause stability issues, will we be able to disable it?
 
The days of having to disable ULPS are gone with Hawaii. It can still be beneficial from a performance, monitoring and overclocking perspective to disable it though. However it's not essential in some cases like it used to be on Tahiti.

Define gone, because half the community would disagree with you there. If you're having to disable it for rudimentary purposes then there is still problems with it. Ones that are easily avoided, but that doesn't make it somehow a non issue. Clock jumping is still very much an annoyance without user intervention. Simple things like this may benefit from such technologies was my initial point
 
Last edited:
Back
Top Bottom