Hi there guys, I recently downloaded the latest Nvidia Profile Inspector, but I'm having a lot of trouble getting the 1/2 Refresh Rate Vsync to work. For some context, I'm on the latest build of Windows 10 and my Nvidia Drivers are fully up to date via (Nividia GeForce driver downloads/installation). I've tested DOOM (2016) and Dark Souls III along with some other titles and no games I've tried applying the 1/2 Refresh Vsync work correctly -- all launch and run at 60 fps. To verify this, I've run Rivatuner Statistics Server (without a framerate cap) to view what fps the games run at. When I look at the games in question in the Nvidia control panel, the Vsync section for each game reads "Custom" so it does appear the 1/2 Refresh Vsync is getting applied, but the game is ignoring it and it doesn't work. I've tried resetting back to the default Nvidia Control Panel settings then only setting the 1/2 Refresh Vsync, but that doesn't work either. It's bizarre because previously the 1/2 Refresh Vsync seemed to be working then suddenly it just stopped. Has anybody else experienced this issue or know a way to fix it or is this just a problem that exists right now that will be rectified down the line? Thank you for your help and time, I appreciate it. - Stephen Enzor P. S. I'm aware from reading online that a reboot used to fix this issue or disabling full-screen optimizations perhaps, but neither has fixed the problem for me. 1/2 Refresh Vsync in Nvidia Profile Inspector simply doesn't work for me despite my efforts thus far. Thanks again for your time, any information regarding this issue would be greatly appreciated. UPDATE: It would seem that the more official "Adaptive Vsync (Half-Refresh Rate)" from the Nvidia Control Panel is also failing to work since when it's forced, games continue to launch at 60 fps. In light of this, I'm beginning to wonder if this is an issue with the latest builds of Windows 10 or the most modern Nvidia Drivers -- though I'd be more inclined to suspect Windows 10 as Nvidia has this option officially in it's Control Panel. I had read somewhere that in the past there was some issue with a display driver, but I'm not really certain what's going wrong atm. Thanks again for your time.