The 290 is quiet with vsync on!

[d_brennen]

Frame limiting > Vsync

 

[vUNREALv]

Vsync has its place but I feel its not viable in online fps games as it introduces too much input delay.

Frame limiting just seems a better option to me.

For the guy talking about adaptive vsync on nvidia, amd cards can do it but we use radeon pro which has every option going for vsync/frame limiting.

 

[VincentHanna]

You won't get tearing below your screen's refresh rate even without Vsync..

Tearing = Drawing more frames than your screen can handle, resulting in some frames shown only as "fractions"

Low FPS is just.. lag, no tearing.

I believe that is incorrect.

With V-sync on, I thought anything lower than 60fps will drop to the next synced ratio of 30fps/hz, hence the sudden stuttering.

Adaptive V-sync stops tearing above 60fps, but then introduces it between 30 and 60fps because it's no longer synced to your display.

See here:https://forums.geforce.com/default/topic/520049/adaptive-vsync-is-a-big-fat-lie/

 

[BaDBoY_uK]

Thanks for the info. It will help some people but not all. For example, I love 144Hz

Pay no attention to some of the elitist GCARD Forum people

 

[Dash RipRock]

You won't get tearing below your screen's refresh rate even without Vsync..

Tearing = Drawing more frames than your screen can handle, resulting in some frames shown only as "fractions"

Low FPS is just.. lag, no tearing.

You will see tearing below ,above and exactly at the frame rate of your monitor whenever you don't have vsync on.Just because you render 60 fps with vsync off doesn't mean that every frame arrived in 1/60 th of a second to your monitor.

Think of it like a 60 metre sprint .....one guy runs at exact 1 metre strides and does it in 10 seconds=vsync on

The second guy takes random stride lengths varying from say 0.8 M to 1.2 m but also does it in 10 seconds=vsync off

There will be instances were the stride patterns match (screen refresh corresponds to a frame being delivered) but the vast majority of the time the strides (frames) will not be in sync,thus we get tearing.we have the same result 60 metres in 10 seconds and 60 frames in one second......but as you can see both would look different.

So knowing all this whenever you start seeing frame rates above or below you inevitably get tearing.Just look at any euro gamer Df article comparing the consoles whenever they(frequently ) drop below vsync frame cap,tearing all over the gaff.

Now how noticeable this is obviously down to the individual and the game and is maybe a separate debate.But it's erroneous to believe that no tearing exists below,above or exactly on the refresh rate of your monitor whenever vsync is not used

 

[kunoichia]

Give it a rest man come on. He's trying to help people.

OCUK gfx section in a nutshell. Fanboys and rude people.

 

[VincentHanna]

Console developers seem to have a way of pushing the tearing in to a top corner of the screen though (from DF articles) to a place you can't usually see due to overscanning.

Why can't they do this on PC's?

 

[Dash RipRock]

Console developers seem to have a way of pushing the tearing in to a top corner of the screen though (from DF articles) to a place you can't usually see due to overscanning.

Why can't they do this on PC's?

Probably because of console fixed architecture ....you know when your engines under stress at certain parts of a game so it's easier to predict a frame delivery that won't be as visible to the user.With a pc we can have broadly similar systems and still get wildly varying frame rates depending on drivers,heat throttling,detail settings,resolution etc etc,the variation is endless so more difficult to decide were a tear will occur and how visible it will be to the user.