Thoughts on NV Adaptive Vsync

[Zanovar]

Your Propaganda will not fool me

 

[Zanovar]

It's garbage in my experience.

A technology that was supposed to deliver a 'smoother' gaming experience, that in actuality delivers a stuttering mess. Normal vsync is better and 'smoother' in experience.

That says it all for adaptive vsync. It doesn't work.

How is sli working for you...?
Do you talk?,i wont bite.

 

[SirPauly]

It's garbage in my experience.

A technology that was supposed to deliver a 'smoother' gaming experience, that in actuality delivers a stuttering mess. Normal vsync is better and 'smoother' in experience.

That says it all for adaptive vsync. It doesn't work.

No offense but where is your proof? Because you say so?

Clearly HardOCP did an investigation and offered a strong, favoring conclusion based on their investigations with tangible data. I'm not saying the feature is for everyone but garbage? Broken?

 

[Gordon Freemen]

No offense but where is your proof? Because you say so?

Clearly HardOCP did an investigation and offered a strong, favoring conclusion based on their investigations with tangible data. I'm not saying the feature is for everyone but garbage? Broken?

Many other people agree including me ADvsync does not work it's busted.

 

[Zanovar]

Many other people agree including me ADvsync does not work it's busted.

Its seems to be working for me whats your problem,.risen 2,Alan wake,tropico 4,swords of the stars and many others...

 

[Gordon Freemen]

Its seems to be working for me whats your problem,.risen 2,Alan wake,tropico 4,swords of the stars and many others...

 

[Gordon Freemen]

Its seems to be working for me whats your problem,.risen 2,Alan wake,tropico 4,swords of the stars and many others...

Placebo much ? Or it could be game dependant I don't know but the games I own and play it is a fail mess on so I don't bother with it.

 

[Zanovar]

Placebo much ?

Placebo?*laughfing my fooking head off*.nope ill leave the placebos to you gordon.*winks*

 

[cmdrdredd]

It works, for what it was designed to do. It turns on vsync when you're above your refresh rate to eliminate tearing there and turns it off to avoid the big 30fps drop you get from regular vsync. It said nothing about eliminating tearing during this time, it says to help keep the framerate smooth.

Do some research on vsync. When the fps drops, it doesn't drop 5 or 10. It drops to 30, then 20, then 15(multiples of 60). That's when you get gameplay that isn't smooth. With DirectX Microsoft forbids using triple buffering at the driver level and instead relies on the game developer to enable triple buffering. Triple buffering eliminates the large fps drop and assists with input lag a bit. Very few DirectX titles have this built in (I know Deus Ex: Human Revolution does). You can try to use Direct3D Overrider but with some games (Skyrim with ENB mod installed) it causes the game to crash. So you are stuck with three options. First you can disable vsync entirely and have zero input lag but experience screen tearing with a smooth framerate though. Turn vsync on and get no screen tearing but have input lag with the drawback of getting large FPS drops. Turn on adaptive vsync and get some tearing(less than vsync off), input lag, but no large fps drops.

 

[PowerK]

Adaptive V-sync works fine. With previous drivers (eg. v301.42 WHQL and before), they had stuttering bugs with certain setups according to ManuelG @ nVIDIA forums. However, with the latest v304.48 beta, these problems were ironed out, AFAIK.

At least, the adaptive v-sync has been working fine for me. Love it.

 

[Grooveriding]

No offense but where is your proof? Because you say so?

Clearly HardOCP did an investigation and offered a strong, favoring conclusion based on their investigations with tangible data. I'm not saying the feature is for everyone but garbage? Broken?

Proof is on my monitor. Adaptive vsync on, stutter and jitter locked @ 60fps. Normal vsync, smooth locked @ 60fps.

http://forums.nvidia.com

Nvidia forums are full of complaints and the same experiences. Another gimmicky half assed feature.

 

[Zanovar]

We need a list of games this happens with.fifa 2012 is bad for it i think(according to friends i dont play the game).is it lots of games though?this is frames dropping to55-60 btw.

 

[SirPauly]

Proof is on my monitor. Adaptive vsync on, stutter and jitter locked @ 60fps. Normal vsync, smooth locked @ 60fps.

http://forums.nvidia.com

Nvidia forums are full of complaints and the same experiences. Another gimmicky half assed feature.

I guess that latest drivers didn't solve anything for you on the bug. Instead of offering constructive views it's down to petty blanket views like garbage or another gimmicky half-a**ed feature.

I was hoping for some actual first hand data or investigation similar to what HardOCP or TechReport did instead of the proof is on my monitor and vocal claims.

 

[SirPauly]

Maybe these newer drivers may iron out some problems some gamers may still be having:

http://www.nvidia.com/object/win8-win7-winvista-64bit-304.79-beta-driver.html

 

[PrincessFrosty]

i realize it turns vsync off below 60fps, but for me (and i thought everyone?) tearing only occurs when you have more frames than your monitors refresh rate.

IE - below 60fps = no tearing.

No! This is a common misconception about tearing.

Tearing occurs at ALL frame rates if you're not running v-sync, without exception, even if you cap your frame rate at your refresh rate you'll still get tearing. Having said that tearing is easier to see as the frame rate gets faster because you get tear lines more frequently.

-With an FPS lower than your refresh rate tearing may only occur once every N frames, a frame rate of 1/2 your refresh rate you'd expect tearing about 1 in every 2 frames, 1/3rd of your refresh rate approximately once in every 3 frame, etc.
-As you approach a frame rate approximately equal to your refresh rate you'd expect approximately 1 tear every frame.
-Frame rates higher than your refresh rate will likely tear every frame and start to tear multiple times per frame. When your frame rate is 2x your refresh rate you'd expect 2 tear lines per frame, with a frame rate of 3x your refresh rate you'd expect about 3 tear lines per frame, etc.

(this isn't exact, it depends how much time your monitor spends drawing the refresh and how much down time it has in between doing that and starting the next frame, but the rule of thumb still works, double the frame rate = double the tearing)

People are sensitive to tearing to different degrees, the frame rate at which it becomes an issue can be vastly different from person to person, but generally speaking the higher the frame rate the easier it is to see and the more bothersome it can be.

 

[toyota]

No! This is a common misconception about tearing.

Tearing occurs at ALL frame rates if you're not running v-sync, without exception, even if you cap your frame rate at your refresh rate you'll still get tearing. Having said that tearing is easier to see as the frame rate gets faster because you get tear lines more frequently.

-With an FPS lower than your refresh rate tearing may only occur once every N frames, a frame rate of 1/2 your refresh rate you'd expect tearing about 1 in every 2 frames, 1/3rd of your refresh rate approximately once in every 3 frame, etc.
-As you approach a frame rate approximately equal to your refresh rate you'd expect approximately 1 tear every frame.
-Frame rates higher than your refresh rate will likely tear every frame and start to tear multiple times per frame. When your frame rate is 2x your refresh rate you'd expect 2 tear lines per frame, with a frame rate of 3x your refresh rate you'd expect about 3 tear lines per frame, etc.

(this isn't exact, it depends how much time your monitor spends drawing the refresh and how much down time it has in between doing that and starting the next frame, but the rule of thumb still works, double the frame rate = double the tearing)

People are sensitive to tearing to different degrees, the frame rate at which it becomes an issue can be vastly different from person to person, but generally speaking the higher the frame rate the easier it is to see and the more bothersome it can be.

that is simply not true in practice. EVERY game is different and some can actually tear worse at low framerates than at a high framerate. CSS has almost no noticeable tearing at 200-250 fps where Metro 2033 drives me bonkers with tearing at 30-40 fps.

 

[railven]

All I want to add to this is, prior to the current driver posted here - Adaptive V-sync was a hit or miss. I've read countless posts (and experienced it myself on my EVGA GTX 680) of stuttering that was only solved by turning it off, which to me is an issue when it is a bullet point on the box.

I'll be giving these drivers a whirl and hopefully all the v-sync issues associated with the 6-series are fixed, because after paying what I did (and constantly reading AMD drivers are garbage rhetoric) it really sucks to have to sit through tearing because the v-sync (something you've relied on for years) suddenly isn't working as expected.

 

[SirPauly]

The new drivers offer a potential garbage, hit or miss, broken, gimmicky half-a**ed feature called TXAA. Curious to see this first hand, investigate it and read views pros-and-cons.

 

[Destiny]

I tried adaptive V-Sync a few times... had input lag due to my monitors and made me look like a noob flying jets in BF3... turned if off... all better... I never play with V-sync on and I'm fine with the screen tearing because it is still playable... I just tried it so I can contribute my thoughts to this thread...

 

[PrincessFrosty]

that is simply not true in practice. EVERY game is different and some can actually tear worse at low framerates than at a high framerate. CSS has almost no noticeable tearing at 200-250 fps where Metro 2033 drives me bonkers with tearing at 30-40 fps.

I gave a technical description of tearing which is accurate.

What you're talking about is perception of tearing which is effected by other things like how fast scenes change in the game you're playing, how similar the environments are, the maximum engine tick rate, and things like that.

Them things don't affect the frequency of tearing, merely your ability to perceive it.

 

[railven]

The new drivers offer a potential garbage, hit or miss, broken, gimmicky half-a**ed feature called TXAA. Curious to see this first hand, investigate it and read views pros-and-cons.

Curious, which games are TXAA ready? Is there a site with a list, if you happen to know?

 

[SirPauly]

I did receive a beta key for Secret World -- so I could investigate TXAA first hand -- in motion -- in worse case examples -- but sadly, it wasn't ready for prime time and the setting was greyed out. To my surprise though, the title was actually quite good -- original and glad I did try it out.

There has been the Secret World title and this slide:

http://www.pcper.com/image/view/11914?return=node/53903

 

[railven]

I did receive a beta key for Secret World -- so I could investigate TXAA first hand -- in motion -- in worse case examples -- but sadly, it wasn't ready for prime time and the setting was greyed out. To my surprise though, the title was actually quite good -- original and glad I did try it out.

There has been the Secret World title and this slide:

http://www.pcper.com/image/view/11914?return=node%2F53903

Is Secret World the first title to use TXAA? Can they patch that into existing titles or does it have to be something built into the code from the ground up?

With Borderlands 2 around the corner, I'm hoping a Demo with TXAA drops soon, be nice to see if this is a good alternative to high-taxing AA options since MLAA/FXAA are definitely not it.

 

[SirPauly]

I believe it is. Really not sure on the coding aspects and what it may curtail. The key to me is at least IHV's acknowledge noise artifacts while moving and still trying to innovate to improve quality. FXAA and MLAA are wonderful for compatibility and still welcomed but for me, quality while moving has always been paramount.

Very curious.