Ok so I've been wondering if I even have g-sync configured properly at all. So I play some games where I get 165FPS all the time. This is how I configure gsync. Nvidia control panel have gsync on for only full screen and vsync on. I don't want my FPS to exceed 165FPS cause that will give me screen tear and I don't like that at all. So when my games reach 165FPS (normally 164.5-164.9) will I still use Gsync or will Vsync kick in and no longer using Gsync? I just want to get the full benefit of Gsync. I have MSI afterburner installed so will be able to cap it at lower FPS than 165 if i have to. I also noticed that the FPS limit in BF4 is much better than using MSI afterburner. So what should I do? OH forgot to mention I disable Vsync in games
You have it set up correctly. However I have never had any screen tearing when my FPS goes over 144hz on my Swift when I have vsync turned off.
but if i reach 165FPS will Gsync still be active. What I can read up is that you must capp your FPS 2-5FPS lower than your refresh rate to keep Vsync from enabling. Even if you disable Vsync in Nvidia control panel and limit your fps to 164-165FPS Gsync will turn off. so I don't know anymore. I also have the gsync indicator on as it doesn't bother me and then I'm sure Gsync works in games so maybe I should try with gsync off and try to get over 165fps to see if gsync indicator goes away cause then I know at least I can trust the G-sync indicator 100%.
The current setup is crap if you ask me. I liked it better before and it was generally simpler. You just had to enable G-sync and then turn off V-sync in NVCPL and all games. Done! You'd have G-sync on for your whole frequency range. Now you need to do like you've done, enable G-sync, then V-sync in NVCPL and also in most games to make sure you don't get tearing after 165fps which can occur although NVCPL says V-sync ON. I dont like games controlling V-sync since I'm afraid it overrides G-sync or just simply tampers with it somehow. Some games still give me slight stuttering which shouldn't occur.
I think this is a misconception. If you watch the framerate, gsync and vsync on limits the framerate to about 0.6 fps less than the monitors max refresh rate. This means that gsync is always on and never travels into vsync territory. You can confirm this by enabling the gsync indicator overlay; you will see that gsync never shuts off, if run this way.
See below. And you can confirm what i said by reading this review.. http://www.blurbusters.com/gsync/preview2/ At the refresh rate = vsync on. Cap FPS to a good bit lower than refresh rate and you'll see the input lag drops significantly. That tell's you vsync is on
I wish it was simple as enable gsync then have it work on the whole range but looks like I will have to set it at 160fps limit and that's still plenty to feel very smooth and have benefit of gsync. I've tried with gsync on vsync off and let my fps go above 165 and my refresh rate caps at 165hz but gsync indicator stays on no matter what fps I get below or above the gsync range
I too have obviously configured it wrong, vsync off everywhere (games + driver), Gsync on everywhere. Will have to put Vsync on via driver too today.
I think Nvidia should just tweak the drivers so that gsync will be on no matter what FPS you run as long as it's in my case 30-165hz. Maybe it's all in my head but I swear after setting my FPS limit to 160 my input lag is decreased and I can feel it's much better.
To be honest, I usually tweak my settings to get near my displays's refresh rate (and currently that usually means maxed), so I haven't had that input lag problem (or I'm simply not as good of a gamer so I wouldn't notice hehe). When I get somewhere above 144 fps in games (my display's max refresh rate), I try to use downsampling, usually via in game.
When I play bf4 on max except aa I can in many cases reach 165FPS but now I have 160fps and my fps is more consistent and like I said I feel my input lag has reduced. Maybe it's just me but I can't stand stutter, input lag and Screen tear. I don't understand how people can play without Vsync on 60hz monitor and still see screen tear. I tested on many different systems with differenet cpu, gpu and monitors and always see screen tear when vsync is not on. I know this is a bit off topic but just wanted to point that out. I thought I was getting the lowest input lag with gsync but now I was like gsync didn't work at it's best and when reaching 165fps my input lag was worse but now I think it's much better. Also figured out that actual Tick rate of the server can affect smoothness. For example my clan has it's own 60hz 10 player unranked server and it's just something about it that feels much better than normal server with same ping (even hosted at same data center) so input lag is also server dependent, engine dependant. That out of the way the whole point of this was to get the lowest input lag I can with my current setup so looks like it should be about +-5 fps lower than your monitor refresh rate when you have a gsync monitor. For me 160FPS and on 144hz Gsync it's about 140FPS
Well I haven't seen screen tearing since I've got my Gsync monitor at all, the rest I've ousted... can't imagine having played BF4 with 35 fps before I got my new rig Yes I too think that the engine, the server, and the infamous netcode make great differences... sadly I've come to accept the usual Battlefield / frostbyte engine problems, and even Overwatch's... it's like they can't make proper netcode anymore these days. Best would probably be csgo (which I don't play) and MOBAs I guess. Will have to try and put Vsync on, but usually BF4 lands somewhere around 140fps maxed at 1440p for me anyway, Overwatch too (tweaked it via in game rendering resolution to land there).
For me g-sync works best when v-sync is active and put that shoulder over max refresh rate. G-sync + fps cap indeed in some games (like Assetto Corsa) cause occasional tearing, just my 2 cents.
If you search internet on the usage of Vsync with Gsync... almost every person says a different thing. What I do is enable Gsync (with Vsync disabled) and frame limit to 144 (or slightly lower). You can use applications like RivaTunner or nVIDIA Inspector to set and apply frame limit. Here's a good read on Gsync & input lag. http://www.blurbusters.com/gsync/preview2/
That article is the main reason why I just have a frame limiter on 160fps. I only found out about that article after posting here. 160hz vs 165hz I can't really see the difference and on the posittive side of things the games where my fps can peak at 160 I then have lower gpu temps as well so in a way it's a win for me.
That's one thing too I was wondering about, if you limit your fps either through the inspector or via vsync, does it actually save power? Or does your GPU just process data and build frames that are afterwards discarded?
Through Gsync or vsync it saves power, the GPU waits for the correct time to deliver each frame, hence the increase in input latency when using vsync.
Indeed. However, input latency introduced by Gsync should be extremely minimal. Anyway, what I usually do when I play games like Counter Strike: Global Offensive is I set ULMB (rather than GSync) in NVCP and apply frame limit in CS:GO to 128 (fps_max 128 cvar). (Since max. tick rate CS:GO supports is 128 tick rate).
That article was written before Nvidia implemented the vsync with Gsync setting. The way you're supposed to run is with Gsync and vsync enabled. I have no issues running like this, ymmv