Sorry for necro-ing this post with such a long explanation too, I talked with OP and wanted to share here some info related to this "problem" just to close the lid once in for all.
This is a G-Sync problem (obviously) and not a problem with DirectX or the upgrade Rainmeter made for D2D.
What was happening?
When this post was made, G-Sync was still new and the technology wasn't that good. It still isn't good but it's doing stuff better now.
The problem boils down to G-Sync's "Presentation Mode"s and Nvidia not providing an option to disable Variable Refresh Rate (VRR) per application profiles.
On a monitor with G-Sync enabled, the application using G-Sync tries to match the FPS of the application using the VRR unless it has an obstruction that tells the G-Sync process "we have 2 things that render, don't cause a screen tear on either". If you have a game running at 144FPS and a window above it, a Rainmeter skin on Always on Top, it adapts to Rainmeter's FPS (which is roughly 60FPS), because of that obstruction, G-Sync will fallsback to the FPS of the window that obstructed over the game, so neither can get a screen tear, but in reality this just causes horrible lag spikes... but hey at least it doesn't tear anymore.
Funny enough, this problem happens at the Windows level too, more specifically, if you're playing a game in Borderless Fullscreen and a Windows Notification appears in the bottom right, the game's FPS tanks because some parts of the DWM run at 60FPS. Additionally, you don't even need Rainmeter to trigger this, you can just open Microsoft Terminal over your current game and your FPS tanks there too.
This was the story when this post was made, what happened since then?
G-Sync now has "Presentation Mode"s, if you run games in Borderless Fullscreen, as long as the games render-pipeline can get "enhanced" by Windows 11's "Fullscreen Optimizations" it should shift to "Presentation Mode 2" allowing G-Sync to work properly.
The situation has changed now, if you have a monitor with the Refresh Rate of 144HZ, a Game with G-Sync and the Max Fps of 100, and a Rainmeter skin with Always on Top (which is roughly 60FPS), G-Sync will now switch into "Presentation Mode 3", which will just disable G-Sync and force the monitor to the Max Refresh Rate (and the game magically gains 44fps as a bonus).
So the issue this post reported had disappeared, because now G-Sync just disables G-Sync when it can't do its job.
What can be done or can the devs do?
Well, since the issue is quite gone on newer stuff, nothing really... kinda.
These are the options (image below) that have to be changed in order for Rainmeter's application profile to force "Presentation Mode 3" for IF G-Sync fails and may revert back to the mode described in OP's post. These options can't be changed in the Nvidia Control Panel so you need a custom profile inspector to change it.
Requesting these changes to the application profile at the upper management level at Nvidia might be a bit tricky though... they might have already been made... but then again, since "Presentation Mode 3" exists, it's no longer a problem, just hope when the dice rolls, your GPU picks that.
![Image]()
That's all, sorry for the novel, the thing the post describes happens less or never in the newest G-Sync version.
This is a G-Sync problem (obviously) and not a problem with DirectX or the upgrade Rainmeter made for D2D.
What was happening?
When this post was made, G-Sync was still new and the technology wasn't that good. It still isn't good but it's doing stuff better now.
The problem boils down to G-Sync's "Presentation Mode"s and Nvidia not providing an option to disable Variable Refresh Rate (VRR) per application profiles.
On a monitor with G-Sync enabled, the application using G-Sync tries to match the FPS of the application using the VRR unless it has an obstruction that tells the G-Sync process "we have 2 things that render, don't cause a screen tear on either". If you have a game running at 144FPS and a window above it, a Rainmeter skin on Always on Top, it adapts to Rainmeter's FPS (which is roughly 60FPS), because of that obstruction, G-Sync will fallsback to the FPS of the window that obstructed over the game, so neither can get a screen tear, but in reality this just causes horrible lag spikes... but hey at least it doesn't tear anymore.
Funny enough, this problem happens at the Windows level too, more specifically, if you're playing a game in Borderless Fullscreen and a Windows Notification appears in the bottom right, the game's FPS tanks because some parts of the DWM run at 60FPS. Additionally, you don't even need Rainmeter to trigger this, you can just open Microsoft Terminal over your current game and your FPS tanks there too.
This was the story when this post was made, what happened since then?
G-Sync now has "Presentation Mode"s, if you run games in Borderless Fullscreen, as long as the games render-pipeline can get "enhanced" by Windows 11's "Fullscreen Optimizations" it should shift to "Presentation Mode 2" allowing G-Sync to work properly.
The situation has changed now, if you have a monitor with the Refresh Rate of 144HZ, a Game with G-Sync and the Max Fps of 100, and a Rainmeter skin with Always on Top (which is roughly 60FPS), G-Sync will now switch into "Presentation Mode 3", which will just disable G-Sync and force the monitor to the Max Refresh Rate (and the game magically gains 44fps as a bonus).
So the issue this post reported had disappeared, because now G-Sync just disables G-Sync when it can't do its job.
What can be done or can the devs do?
Well, since the issue is quite gone on newer stuff, nothing really... kinda.
These are the options (image below) that have to be changed in order for Rainmeter's application profile to force "Presentation Mode 3" for IF G-Sync fails and may revert back to the mode described in OP's post. These options can't be changed in the Nvidia Control Panel so you need a custom profile inspector to change it.
Requesting these changes to the application profile at the upper management level at Nvidia might be a bit tricky though... they might have already been made... but then again, since "Presentation Mode 3" exists, it's no longer a problem, just hope when the dice rolls, your GPU picks that.
That's all, sorry for the novel, the thing the post describes happens less or never in the newest G-Sync version.
Statistics: Posted by Jeff — November 5th, 2024, 5:38 pm — Replies 1 — Views 1987