Monitor reported refresh rate vs system [Technical LFC Debugging for VRR]

Talk about NVIDIA G-SYNC, a variable refresh rate (VRR) technology. G-SYNC eliminates stutters, tearing, and reduces input lag. List of G-SYNC Monitors.
wtfisgoingon
Posts: 6
Joined: 08 Nov 2021, 11:11

Re: Monitor reported refresh rate vs system

Post by wtfisgoingon » 12 Nov 2021, 16:50

RealNC wrote:
09 Nov 2021, 12:20
wtfisgoingon wrote:
08 Nov 2021, 11:59
I have more details I can provide if anyone wants them but right now after not being able to use G-Sync I really just want to spend all day playing with it :)
Thanks for taking the time to post this. You might want to report this to nvidia:

https://nvidia.custhelp.com/app/answers ... -to-nvidia
Thanks I will do that!

wtfisgoingon
Posts: 6
Joined: 08 Nov 2021, 11:11

Re: Monitor reported refresh rate vs system [Technical LFC Debugging for VRR]

Post by wtfisgoingon » 12 Nov 2021, 16:54

Another couple of updates:

1) I can untick then retick the box while the game is running and it will still fix it. I'm not sure if this is a new thing or because of the last Win 10 update from a couple of days ago because I hadn't ever bothered to try doing it this way. All the other times I would shut down the game, untick appy, retick apply, then start game.

2) This exact behavior happens on my G-Sync compatible monitor (HP 25x) when I allow the monitor to be put into sleep mode and then try to use it afterwards. I had noticed that using it after it being in sleep mode would make it "feel" weird so a couple of years ago I got in the habit of always shutting the monitor off manually to avoid this. I wondered if this was perhaps the same thing happening so I tested allowing it to go into sleep mode and then doing the untick apply retick apply to see if it would correct it and it does.

User avatar
Chief Blur Buster
Site Admin
Posts: 9829
Joined: 05 Dec 2013, 15:44
Location: Toronto / Hamilton, Ontario, Canada
Contact:

Re: Monitor reported refresh rate vs system [Technical LFC Debugging for VRR]

Post by Chief Blur Buster » 16 Nov 2021, 15:01

I wonder if there's an API that can do the equivalent of untick/reticking the box.
As a workaround for these types of driver bugs.
Head of Blur Busters - BlurBusters.com | TestUFO.com | Follow @BlurBusters on Twitter

       To support Blur Busters:
       • Official List of Best Gaming Monitors
       • List of G-SYNC Monitors
       • List of FreeSync Monitors
       • List of Ultrawide Monitors

wtfisgoingon
Posts: 6
Joined: 08 Nov 2021, 11:11

Re: Monitor reported refresh rate vs system [Technical LFC Debugging for VRR]

Post by wtfisgoingon » 16 Nov 2021, 16:47

Chief Blur Buster wrote:
16 Nov 2021, 15:01
I wonder if there's an API that can do the equivalent of untick/reticking the box.
As a workaround for these types of driver bugs.
I wasn't 100% sure if I should put this here or make a new post..

I'm making a video to submit to Nvidia as well as to use to help out others with the same issue.

I'm wondering if anyone interested would mind watching it and letting me know if there is anything else I could add or change or do to improve the video such as other or different RTSS / Afterburner settings or any other program I could run at the same time to show better stats and things like that.

In the video I start recording after a full restart and then load up the game I play the most (although all of these exact same things happen on the other 5 or so games I've tried it on) and let it sit for a few seconds after getting to main menu then I change to different menus because they always create an FPS drop.

Then I alt-tab and shut down RTSS, wait a couple of seconds then restart it and alt-tab back to the game to show that nothing changes other than "Sync Timeout" which will change on each startup of RTSS & while things are "Wonky" this number will always change and varies wildly between ~6.930ms - 24.756ms When things are working normally this number will still change but only very slightly as it will always be within ~6.930ms - 6.960ms. These changes also line up with what the OSD & "info" button on my monitor reports.

Then again after switching between a few menus and pausing a few seconds in between I alt-tab and check & then uncheck the box then alt-tab back into the game and switch between menus & alt-tab out to shut down RTSS then restart it etc to show the differences.

Here is a link to the video: https://youtu.be/MHiHR71DxI4

Some notes:

Every setting is identical the only thing altered is unticking the box, clicking apply, reticking the box, clicking apply. I get the exact same results if I shut down the game then do those steps and then restart the game as I do if I leave the game running so to keep the video short I just left the game running.

If I restart my system things are always "Wonky" until I untick the box apply it and retick the box however after doing this provided that I do not restart my system I can stop & play the same game or other games and things work normally. Again, this happens 100% of the time.. on system startup things are always "Wonky" and after unticking/reticking things will work normally regardless of how many hours pass or how many games I play, movies I watch etc until I restart and then it's "Wonky" again.

I know the OSD & the "info" button on a monitor isn't exactly accurate but I thought it was worth mentioning that when things are wonky the OSD fluctuates wildly between 40-144Hz so quickly it isn't readable & the "info" button will always report a different refresh rate between 40-144Hz each time it's used. When things are normal the OSD always displays a solid 144Hz & the "info" button always reports 144Hz. This happens 100% of the time, regardless of my FPS, it doesn't matter if it is steady or constantly fluctuating.

Using FSE vs Borderless Fullscreen doesn't change anything other than "Present Latency" is higher at all times while using FSE.
In FSE it is constantly ~0.160 ms and in Borderless Fullscreen it is constantly ~0.080 ms. I know this number normally fluctuates somewhat but after a few hours of playing while keeping on eye using both FSE and Borderless Fullscreen it's very obvious to me that FSE close to double vs Borderless Fullscreen which I found fairly easy to notice since in Borderless Fullscreen it very rarely goes over 0.100ms and in FSE it is always well over 0.100ms and constantly hovers around 0.160ms.

Post Reply