I’ve been running with r.VSync=0 since forever. The game has an FPS lock in place still. You want proof? Do it yourself. There’s separate .ini settings to disable/modify the FPS limit. I will show an example below.
Adaptive v-sync only enables v-sync when the game is hitting 60 FPS or more.
This game (with default FPS lock) isn’t hitting 60 FPS or more but rather 60 FPS or less. The distinction is important because it’s the difference between adaptive v-sync detecting performance and enabling/disabling v-sync. In this case, v-sync is rarely getting enabled and you see frame tearing as a result.
To get adaptive sync to work properly, you need to force the FPS limit off or increase it.
To turn it off:
Or to increase it:
Where you substitute the bolded value in UpperBound=(Type=“ERangeBoundTypes::Exclusive”,Value=60) with something higher than 60. I also recommend changing the lower bound value to 5 as it helps out people with borderline performance a bit.
This will speed your game up but if you have a 60hz monitor and enable adaptive sync it will be forced down to 60 with no tearing.
The above procedure of disabling the FPS limit and enabling adaptive v-sync through the NVCP is actually a good way to reduce the severity of frame drops on crappier PC’s. The game will run full speed as normal but when you drop frames, instead of slowing the whole game down to 30 FPS momentarily with regular v-sync, v-sync will temporarily turn off and you will only drop a few.
People on 144hz/non-60hz monitors should just be disabling v-sync. The tearing is not as apparent on the higher refresh rate and input lag is way better. Alternatively they can run on 120hz mode or some other even multiple of 60 to use with any v-sync method.