• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

update: new geforce beta drivers 301.25

Page 2 - Seeking answers? Join the AnandTech community: where nearly half-a-million members share solutions and discuss the latest tech.
When my FPS is at or below my refresh rate of 60 Hz, I never get tearing. Are we talking about the same thing here, tearing when FPS surpasses display refresh rate?
 
chimaxi83 said:
When my FPS is at or below my refresh rate of 60 Hz, I never get tearing. Are we talking about the same thing here, tearing when FPS surpasses display refresh rate?
Click to expand...
that is 100% false. tearing can and does occur at ANY framerate when vsync is off. anybody claiming they see no tearing below refresh rate is blind and/or has no idea what they are talking about. of course every game is different and tearing may not be bad in some cases while driving you nuts in another. in my experience the worst tearing I have seen has always been in the games with the lowest framerates though.
 
Last edited:
All that the adaptive vsync does is disable vsync below 60fps and enables it above 60fps.

I prefer just keeping vsync on, personally. I hate the tearing more than I notice the input lag.
 
toyota said:
that is 100% false. tearing can and does occur at ANY framerate when vsync is off. anybody claiming they see no tearing below refresh rate is blind and/or has no idea what they are talking about. of course every game is different and tearing may not be bad in some cases while driving you nuts in another. in my experience the worst tearing I have seen has always been in the games with the lowest framerates though.
Click to expand...

I'd agree with this. I cannot stand playing any game with vsync disabled, it is very distracting.
 
toyota said:
that is 100% false. tearing can and does occur at ANY framerate when vsync is off. anybody claiming they see no tearing below refresh rate is blind and/or has no idea what they are talking about. of course every game is different and tearing may not be bad in some cases while driving you nuts in another. in my experience the worst tearing I have seen has always been in the games with the lowest framerates though.
Click to expand...

lol, why do you try and act like such a dick in all your posts? I don't get it, inferiority complex? 😕

Anyway, I know what tearing looks like, I'm not a fucking idiot. Here, let me reword it and spoon feed it to you. The only time I NOTICE tearing is when my FPS is above my refresh rate, i.e. greater than 60. Using Vsync to lock it to 60, or console command to limit it to 60, or when performance drops my FPS below 60, causes my eyes to no longer notice tearing.

Better now? I'm going to go lock my FPS to 50 or 55 and see what it looks like in BF3, I've never locked it at a lower limit.

Ditch the attitude.
-ViRGE
 
Last edited by a moderator:
SickBeast said:
All that the adaptive vsync does is disable vsync below 60fps and enables it above 60fps.

I prefer just keeping vsync on, personally. I hate the tearing more than I notice the input lag.
Click to expand...
it depends on the game. if its dropping below 60 fps most of the time then that choppiness when vsync is on is worse than tearing to me in most cases. I prefer to use vsync but I always just take it on a game by game basis.
 
Last edited:
chimaxi83 said:
lol, why do you try and act like such a dick in all your posts? I don't get it, inferiority complex? 😕

Anyway, I know what tearing looks like, I'm not a fucking idiot. Here, let me reword it and spoon feed it to you. The only time I NOTICE tearing is when my FPS is above my refresh rate, i.e. greater than 60. Using Vsync to lock it to 60, or console command to limit it to 60, or when performance drops my FPS below 60, causes my eyes to no longer notice tearing.

Better now? I'm going to go lock my FPS to 50 or 55 and see what it looks like in BF3, I've never locked it at a lower limit.
Click to expand...
because topics like this have been discussed to death. I get so tired of some people claiming that tearing only occurs above refresh rate when that is absolutely not true.

and you just said "When my FPS is at or below my refresh rate of 60 Hz, I never get tearing " and "Are we talking about the same thing here, tearing when FPS surpasses display refresh rate?" which showed that you were claiming tearing only occurs above refresh rate.
 
Last edited:
toyota said:
yes you will still get tearing with adaptive vsnyc when it drops below your refresh rate. and since your refresh rate is 120hz then you will still get the same amount of tearing in demanding games since there is no way you will be close to 120fps.

and I thought all 120hz monitor owners claimed they got little to no tearing?
Click to expand...

LOL, they do! Many people (online) have said 120Hz monitors don't need vsync, because even if a game does go above 120FPS, tearing is much less noticeable overall compared to a 60Hz display. Not true. There is a noticeable difference when vsync is enabled.

I think I'll just stick with using vsync + triple buffering. I've never noticed input lag. I'm not saying it isn't there, but I'll take it over tearing. I already have to deal with minimal network lag (don't we all?), so an extra frame of input lag won't hurt me.
 
Tearing is going to happen any time the buffer is flipped to display the new frame while that buffer is being updated. (which can happen any time vsync is off)

It is usually harder to notice at lower framerates (for me, I don't know if this is an absolute), but yes, it will happen unless vsync is on.

I use adaptive vsync, and occasionally I'll notice tearing (when under 60 fps), but it appears to be much less apparent than tearing with vysnc off over the refresh rate. I'm not sure why that is.
 
Last edited:
ViRGE said:
I'm afraid you don't have that quite right. "Bad" triple buffering without v-sync still adds input lag and at the same time allows tearing. The point of triple buffering (well, "good" TB at least) is that you can run a game with v-sync without stalling the GPU due to a full back buffer, and with lower average input lag than double buffering with v-sync. If you turn off v-sync, you've completely defanged triple buffering - why have a 3rd buffer if you're just going to immediately buffer swap anyhow?
Click to expand...

On 60Hz monitors triple buffering would add another 16ms of input lag, which is not bad for most single-player games (or any online games that do not rely on as little "ping" as possible).

Usually, turning off vsync means that there's no triple buffering (not even the "bad" triple buffering), even in many DX10/11 games that automatically call for triple buffer whenever vsync is enabled. In the old days, many games would offer TB as an option in the graphics settings.

I would say that adaptive vsync benefits the SLI gamers the most since Alternate Frame Rendering usually does not properly do true triple buffering anyways. AFR already calls for 4 buffers (imagine the input lag) with simple vsync, and true triple buffering does not work as seamlessly in many games. For example, in Source games that offer TB as an in-game option, it would be "pseudo" TB where the frame rate drops from 85 fps to 60, then to 45, then 30.. a very strange phenomenon that is not really any better than double-buffered vsync.

Even though double-buffered vsync theoretically adds only between 0-16ms of lag to a 60Hz screen compared against disabled vsync (in which some areas of the screen is updated faster than the tearing part which is updated up to 16ms later), vsync itself usually detracts from the "ideal" responsiveness of input devices (especially the mouse) - which is rather perceivable in the majority of games out there. To see if it helps, try forcing the number of max prerendered frames in the CP from default 3 to 2 or 1 for better responsiveness with vsync. If the setting of 0 still does not improve the responsiveness of your mouse, then it's probably better to just disable vsync altogether if the tearing is not too unbearable (which unfortunately usually is the case with 60Hz panels).

On my Sony GDM-FW900 which can do all kinds of refresh rates, even overclocked to 2560x1600 @ 69 Hz, I play many online fps shooters at 1920x1200 @ 90Hz. As long as the frame rate in the game is also 90fps most of the time (EDIT: manually locking it at 90 fps), the tearing is rather minimal. The output seems to already be "synchronized" fairly well in that it does not really need vysnc, and the responsiveness is as good as it gets without having to deal with the input lag and response times of LCD monitors.
 
Last edited:
Torchlight has an issue with lighting if enabled on a GF 560 Ti where there weren't issues prior. Haven't looked too much into it.
 
I've always played with vsync disabled and my 470s overclocked with my i5 running 5GHz or higher.

Depending on the game (BFBC2 for example was a game I played a lot when I first put together my system) I could see fps upward of 180 fps on a 60Hz screen, the only game I ever had some minor tearing issues with ever was WoW. That was horizontal screen tearing when running up inclined terrain.

What kind of monitors are people running? It seems odd my cheap ASUS isn't having issues dealing with fps that can triple the refresh rate.
 
Last edited:
you must be one of the lucky few that does not really notice or is not bothered by tearing. for some games its not bad but other it can drive me nuts. the monitor may make a difference but its mostly down to the game itself.
 
So which option in BF3 enables fxaa ? I have post AA on high and the only other type of AA I see is MSAA 2x and 4x which both do terrible things to performance. No option for FXAA showing though ...
 
vsync+triplebuffering+slightly below the vsync rate frame cap = smooth

The only time I NOTICE tearing is when my FPS is above my refresh rate, i.e. greater than 60.
Click to expand...
best get your eyes checked.

On 60Hz monitors triple buffering would add another 16ms of input lag, which is not bad for most single-player games (or any online games that do not rely on as little "ping" as possible).
Click to expand...

No triplebuffering does not add 16ms, at the worst its an additional 4ms
 
Last edited:
chimaxi83 said:
My vision is fine, but thanks for your uselessness :thumbup:
Click to expand...
sorry but your vision is not good if you don't ever see tearing below 60 fps. did you even look at the video I linked too? if you cant see the obvious tearing there then I dont see how any other graphical setting would be noticeable to you either.
 
I almost never get tearing. Or see it. Other than a recent Star Wars TFU game.
I also play mainly driving games?
 
Anarchist420 said:
What happened to the ability to force regular AA (SGSSAA or MSAA) with all DX10 UT games? I heard it wasn't possible starting with a certain series of drivers (I forgot which ones)... so was it fixed with the 301s?
Click to expand...
I’ve never had that problem or even heard of it.
 
You must log in or register to reply here.

TRENDING THREADS

Back
Top