Microsoft adds Variable Refresh Rate For Games that lack Support

You need to go to System app/Display then Graphics Setting, it should pop up.

 

Let me toss some love Microsoft's way. This may not work properly but the fact that they are even bothering to make gaming better makes me happy.

 

Kill forced VSync/double/triple buffering. And similar things which may prevent game from actually delivering as much as it can within given HW limits.
Now, some of things can be overridden by drivers. But maybe intel does not do that. Thing is that this adds another man in the middle. Which may be good for some things and bad for another.

Like, when people used direct sound to inject ESP overlays to games. It is another place which may be used for game hacking. And another place where anticheat may take a while to be able to detect hacks. (If they can detect them at all.)

 

Can I use VRR on HDMI now as a Nvidia owner?

 

No option here.
looks to be for the IGPU

 

nope you need display port for freesync with nvidia.
no support for freesync over hdmi with nvidia you need a AMD gpu for that

I might be wrong but i dont think so.

 

I just want to ask, it (VRR) probably needs HDMI 2+ as well, correct?

 

Did anyone find any game that utilizes this option with success?

 

Except id doesn't work as you say: the DXGI_SWAP_CHAIN_FLAG_ALLOW_TEARING flag cannot be injected in the DXGI swap chain descriptor on every DX11 application since it doesn't work with all DXGI version, while a non-UWP DX11 application can be built with any DXGI version. This means that forcing DXGI_PRESENT_ALLOW_TEARING in DXGI Present() will not work with applications built with older DXGI versions. The only exception are the UWP which do not support older DXGI version, which means forcing DXGI_PRESENT_ALLOW_TEARING flag is trivial. Yes, to make VRR works you need both flags.
Finally, DXGI_SWAP_CHAIN_FLAG_ALLOW_TEARING will work only with FLIP swap effects, and not with BitBlt effects which can be used outside UWP. Also, FLIP swap effects do not work with Windows 7: DXGI_SWAP_EFFECT_FLIP_SEQUENTIAL is supported on Windows 8 and forward and DXGI_SWAP_EFFECT_FLIP_DISCARD works only on Windows 10: this means FLIP swap effects are not pretty common on applications meant to run on older version of Windows too.
So yes, all this was made only for a well defined subset of DX11 applications: those do not use traditional fullscreen calls with Present(0,0) (traditional fullscreen and present(0,0) calls already produce tearing that can be feed VRR systems and that are not supported in UWP) and those meant to run using FLIP effects only (which is the only effect supported in UWP)..... So we have NOT(NOT UWP) intersect with UWP... which is... UWP intersect with UWP... which is... UWP.

EDIT:
Added sources:
https://docs.microsoft.com/en-us/windows/desktop/api/dxgi/ne-dxgi-dxgi_swap_chain_flag
https://docs.microsoft.com/en-us/windows/desktop/direct3ddxgi/dxgi-present
https://docs.microsoft.com/en-us/windows/desktop/api/DXGI/ne-dxgi-dxgi_swap_effect
https://docs.microsoft.com/en-us/windows/desktop/api/dxgi/nf-dxgi-idxgiswapchain-present

 

I don't see the option and I have all requirements :
Windows 10 1903 18362.145
ASUS PG278Q (Gsync)
430.86
GTX 1080 Ti

 

I don't either. People are saying you need 435.27 to see the new option.