Topic Title: 13.8 beta catalyst drivers are junk!!
Topic Summary:
Created On: 08/12/2013 01:21 PM
Status: Post and Reply
Linear : Threading : Single : Branch
Search Topic Search Topic
Topic Tools Topic Tools
View similar topics View similar topics
View topic in raw text format. Print this topic.
 08/12/2013 01:21 PM
User is offline View Users Profile Print this message

Author Icon

Posts: 53
Joined: 07/21/2013

Hey guys, after installing the 13.8 beta drivers i notice terrible preformance and now for some reason v-sync is locking my fps in every game to 30fps!!! i have ran the unigine heaven benchmark and the scored were beyond terrible on the 13.8 drivers, so my suggestion to all of you is stick with the 13.6 beta 2 drivers!!!!!!

 08/12/2013 02:40 PM
User is offline View Users Profile Print this message

Author Icon
Ninja Zombie Killer

Posts: 4905
Joined: 12/27/2008

I have no issues with it. Could you post system specs? (I suspect a 7k card, as usual...)


CPU: AMD Phenom II X4 810 @ 3120MHz | RAM: Kingmax 2x2GB DDR2 800 @ 833MHz| MoBo: MSI K9A2 CF v1.0 (BIOS: 1.D)| GPU: Asus HD 6850 1024MB (DirectCu) @ 835/1135MHz | Display: L24FHD | PSU: PC Power & Cooling Silencer 750 Quad | OS: MS Windows 3.11 Pro x64

 08/14/2013 04:24 PM
User is offline View Users Profile Print this message

Author Icon

Posts: 7
Joined: 08/14/2013

masterx, i've seen that issue with v-sync being limited to 30fps on every release of drivers by both nvidia and amd, on multiple versions of pc hardware... it's never worked better than that for me.
 08/14/2013 06:05 PM
User is offline View Users Profile Print this message

Author Icon
80 Column Mind

Posts: 13566
Joined: 04/17/2008

I see no subjective difference between 13.4 WHQL and 13.8 beta, no noticeable increase in FPS, no increase in consistency, which is not surprising because the 13.8 set was intended primarily for Crossfire users.

As for V-sync, I have noticed for many years that on some games if your FPS does not stay consistently above 60 that it will lock it to 30 instead, which has the same result of keeping it as consistent as possible.

AMD FX-8350 w/ Corsair H105, ASUS Sabertooth 990FX Gen3/R2, 8GiB G.SKILL DDR3-2133, XFX HD 7970 GHz Edition, 1TB Samsung 850 Evo, 256GB OCZ Vector, Creative X-Fi Titanium w/ Creative Gigaworks S750, SeaSonic X750, Corsair C70, HP ZR2440w, Win 7 Ult Ed x64
 08/15/2013 01:30 AM
User is offline View Users Profile Print this message

Author Icon
Alpha Geek

Posts: 1567
Joined: 07/13/2009

If the game doesn't support triple buffering, and you don't force it with something like D3DOverrider or RadeonPro, then vsync will cause your frame rate to drop from 60 to 30 when your frame time is larger than 16.67ms (for a 60Hz refresh rate).

When you use only double buffering (the default), there are two render buffers, one of which is designated as the frame buffer (the piece of memory that holds the information drawn on the monitor).  The frame buffer is read-only throughout the refresh interval (16.67ms for a 60Hz display).  So the GPU can render only to the one free buffer. 

The vertical blanking interval, the small bit of time between when one screen refresh ends and the next begins, is the only time when the buffers can be swapped.  If the free buffer is not yet a complete frame (the frame rendering time exceeded 16.67ms), there's no swap, and the previous frame is drawn again.  Now in the second refresh interval since the frame began rendering, the GPU might finish quite early.  Say it takes just 17ms to render the frame.  Now it has to sit there doing nothing, because the framebuffer is still locked, and the render buffer is complete.  There's nowhere else to begin rendering the next frame to.  So after the second blanking interval, 33.33ms after the frame rendering began, you see the latest frame.  And the GPU starts from scratch on the next one.  Since it can't finish it inside 16.67ms, you again wait until 33.33ms later to see the new frame.  That's why it goes from 60fps (1000ms/16.67ms per frame) to 30fps (1000ms/33.33ms per frame).

With triple buffering, there's an additional render buffer.  Now in the case above, you'll still wait 33.33ms for the first frame, but after the GPU finishes that frame, and it's waiting for the VBI to swap the framebuffer with the completed render buffer, it has that other buffer available to render to.  So instead of sitting idle for 16.33ms, it's working on the next frame, which will be complete less than a millisecond into the next refresh interval, ready to display.  At which point it's working on the next frame, which will also be complete in the next refresh interval, and so on.

So a 17ms frame time (real frame times are never so constant, of course) would results in 30fps with double buffering, and 58.8fps with triple buffering.  What that translates to is basically one refresh interval each second (out of 60) showing the same frame instead of a new frame.

Increase the render time, and the result is more frequent duplicate frames, with any number between 60 and 30 frames rendered and displayed in each second. 

So force triple buffering, or turn off vsync and live with the hideous screen tearing that results.  At least if your frame rate is below the refresh rate, there will only be one seam on the screen at any one instant.

93436 users are registered to the AMD Support and Game forum.
There are currently 3 users logged in.

FuseTalk Hosting Executive Plan v3.2 - © 1999-2015 FuseTalk Inc. All rights reserved.