NVIDIA 353.06, Kepler fix, ULMB CP toggle + G-SYNC VSYNC OFF

[Bishi]

Because if you hit max fps with vsync off you get tearing and if you hit it with vsync on you get input lag

[0134RY73]

*This because that tearing when you exceed 144hz is awful!

Yes, that's the point of the vsync off option. But a better choice imo is just to cap below max fps (135 for a 144 screen)

[lexlazootin]

Why would that be better?

because then you wont get frame tears and studders when going above 144fps

[PiERiT]

With these drivers, is it still necessary to turn off V-SYNC within games in order for G-SYNC to work? Or is that not necessary since they've seemingly been split into two separate settings?

[Bishi]

With these drivers, is it still necessary to turn off V-SYNC within games in order for G-SYNC to work? Or is that not necessary since they've seemingly been split into two separate settings?

If given the option it is best to turn off in game regardless of your driver setting. Driver settings usually override whatever you have set in game but they can cause problems in some instances.

[ciopenhauer]

Because if you hit max fps with vsync off you get tearing and if you hit it with vsync on you get input lag

I get about 300-500 FPS in CS:GO with G-sync on and V-sync off. I don't really notice any tearing because of the high fps count and being used to tearing in CS:GO anyway. Is it still better to use fps_max 135 for reduced input lag, or V-sync off with max_fps 0? Or are they equivalent?

[lexlazootin]

I get about 300-500 FPS in CS:GO with G-sync on and V-sync off. I don't really notice any tearing because of the high fps count and being used to tearing in CS:GO anyway. Is it still better to use fps_max 135 for reduced input lag, or V-sync off with max_fps 0? Or are they equivalent?

At higher frame rates frame tearing IS harder too see but if you just cap your fps to 140 you wont get frame tears making it a much more consistent experience. input lag should pretty much be the same.