1 g-sync & v-sync cannot be enabled at the same time (example i had to turn off g-sync because it was keeping my fps locked at 60). granted my TV does not support g-sync anyways (this is simply based on my personal experience do not take it to mean that vsync is not compatible with gsync)

2 when using g-sync, v-sync or freesync, it is essential to make sure that your fps is not being locked through a program like nvidia profile inspector (not sure what the amd equivalent is). otherwise your fps will remain locked even if using sse display tweaks or enb series (to clarify it is ok to cap the fps but you want to avoid locking that fps to your refresh rate, it should also be noted that screen tearing may only occur when reaching a certain amount of fps in games, for example if you see screen tearing at above 120 fps then you should cap your fps to 120 or simply lower it by 10 each time until the screen tearing stops occurring)

3 the driver settings for your graphics card will often overwrite your program settings, the solution is to make sure that your program settings and driver setting match each other so that hey are not fighting with each other (for example super sampling does not play nice with some games mainly directx 11 games if i remember correctly, personally i tend to default to 16xq csaa with transparency supersampling and multisampling set to off but that is simply my prefence)

4 if using two mods like enb and sse display tweaks then you will need to make sure that the fps is only capped through sse display tweaks and not through the enb (make sure your fps is not being capped inside your skse ini either, basically you want all control over your fps to be handed off to sse display tweaks).


ok so i have decided to update this article because there are some who are having issues with screen tearing while using gsync or freesync, so lets list out the problems and some of the causes

1 using a freesync monitor for gsync or vise versa, some monitors do not play nicely with gsync if they are built for freesync then you will need to make sure that freesync is enabled for nvidia (side note using freesync monitors with gsync crads is known for being buggy in some areas)

2 if using freesync or gsync make for sure that you are using displayport and noot hdmi otherwise gsync or freesync will not activate, if you have a monitor that only supports hdmi then you will be stuck with using vsync

3 if you are using nvidia profile inspector then make sure that you are using the version that comes from orbmu2k on github because the other version has not been updated in a long time and is missing several options

4 in nvidia profile inspector the frame rate limiter, maximum pre rendered frames, prefered refresh rate, and triple buffering are shared settings for both vsync and gsync. gsync and vsync are listed under the same section in the program because some of the settings that are used are shared between the two and should be adjusted for the monitor that you are using and the game that you playing whether it is skyrim or some other game

5 which brings me to the last point which is if you are still getting screen tearing while using gsync or freesync then it may be necessary to cap the frame rate or check to make sure that gsync and freesync are actually working and not simply falling back to vsync because gsync and vsync are failing to activate (side note this last scenario is very probable if using a enb or reshade since some of their settings can cause gsync, freesync or vsync to become deactivated)

(bonus tip set your texture filtering lod bias settings to to -1.0000 or  -2.0000 for a sharper image or for a blurier image set it to +1.000 iwould not go above this as it seems to produce really bad results and texture filtering negative lod bias will need to be set to clamp for the best results.)

thought i would through in that little tidbit since a lot people do not know what the lod bias is actually used for and i generally prefer to have my anisotropic filtering setting set to 4x or 8x when using the lod bias
 

on a side note there are a few people that have suggested that gsync and vsync should be used together, this likely comes from the fact that when gsync was first created it was often used with vsync. however i was under the impression that the use of the two together had been phased out but this might not be the case and i may very well be wrong in my assumption. therefore i have no official opinion on the matter until i can find documentation proving that they do or do not work together