On the old board it was always recommended to leave v-sync on in the nvidia CP, and v-sync off in game; the reason for this was because v-sync in the nvidia cp added some additional functionality to g-sync (don't remember why exactly, frame pacing?).
You are not required to disable V-Sync in-game.
It's just that some games behave differently when you have their V-Sync option enabled or disabled, even if it's forced on via the NVIDIA Control Panel.
For most games, there will be no difference whether it's enabled or disabled in their options. For some it will be better one way or the other.
It's most likely that if it matters, the best option will be to disable it in-game, so some people suggest doing that by default.
Probably not by a large margin, but limiting FPS with a 3rd party program apparantly always introduces a bit a input lag.
From Best to Worst:
1. in-game limiter
2. riva-tuner
3. nvidia control panel/nvidia inspector
This is correct, but the difference between an in-game limiter and RTSS is essentially negligible - half a frame at most, while NVIDIA's driver-based framerate limiter (accessed via Inspector) has as much latency as V-Sync and should be avoided at all costs.
Not all games have a well-implemented framerate limiter, so it may still be preferable to use RTSS even if they have the option, since it will provide consistent results.
* Fallout: New Vegas - Another janky mess. Fresh install without the New Vegas stutter remover mod and while it still isn't the smoothest game i've seen, it's certainly playable. Great surprise.
You should still keep NVSR enabled. If I remember correctly, the issue is that the game runs at a fixed 64Hz tickrate by default, which the stutter remover fixes. Without NVSR, you would have to cap it to 64 FPS.
Since most displays are 60Hz, you can imagine why the game using a 64Hz tickrate causes stuttering.
Now for the one with the questions:
* Assassins Creed: Origins - Now this one is strange. Unlocked framerate doesn't feel smooth like what i've experienced with Tomb Raider.
Locking the game to 60FPS with both the in-game framerate lock AND Riva-tuner fixes most of the micro-stuttering but it's still hitchy.
Anyone here who has experience with Origins and G-Sync?
G-Sync can only fix stuttering issues caused by frame presentation. If the stuttering is caused by disk access or something else, it can't fix that.
Often, games where the framerate is limited due to the CPU (resulting in low GPU usage) don't feel quite as smooth with G-Sync as games which are GPU-limited. (GPU working at 99%)
I don't have the game, but Origins is notorious for being hard on the CPU, which is likely the reason that G-Sync doesn't feel quite as smooth as the other games you've tried.
As you've found out, implementing a framerate limiter can help, since a lower framerate target can prevent the game from hitting the limits of your CPU.
What I generally suggest is that people set a global FPS limit in RTSS that is 3 FPS lower than the monitor's maximum refresh rate, and optionally add profiles for games where you want different behavior, like adding a 60 FPS cap to "AssassinsCreedOrigins.exe" or whatever the game uses.
P.S. You can just type the executable name (if you know it) instead of actually navigating to the file path when adding profiles to RTSS. Can save a bit of time.
