You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Are you using any gamescope patches or a forked version of gamescope?
The issue occurs on upstream gamescope without any modifications
Current Behavior
Hello,
I noticed that mangoapp affects the way adaptive sync works, although setting is not configured in the mangohud config.
What can be noticed is that Refreshrate jumps above 200 sometimes although VRR/adaptive sync is enabled, If you tell me how to provide proper graphs of refresh rate behaviour, I can visualize it.
When removing --mangoapp from the gamescope options, the behaviour of VRR is as expected, leaving the refreshrate very close to the current fps.
Steps To Reproduce
Launch anygame with gamescope --adaptive-sync --mangoapp
check actual refreshrate of your monitor (e.g. in the OSD) while gaming
this is a longstanding known issue. you can try gamescopectl adaptive_sync_ignore_overlay 1 (or whatever the exact command is, check gamescopectl help while Gamescope is running for the full list) to see if that helps. We've been tracking the general nested VRR issues here: #1617. It's not NVIDIA specific.
Is there an existing issue for this?
Are you using any gamescope patches or a forked version of gamescope?
Current Behavior
Hello,
I noticed that mangoapp affects the way adaptive sync works, although setting is not configured in the mangohud config.
What can be noticed is that Refreshrate jumps above 200 sometimes although VRR/adaptive sync is enabled, If you tell me how to provide proper graphs of refresh rate behaviour, I can visualize it.
When removing --mangoapp from the gamescope options, the behaviour of VRR is as expected, leaving the refreshrate very close to the current fps.
Steps To Reproduce
Hardware information
Software information
Which gamescope backends have the issue you are reporting?
Logging, screenshots, or anything else
No response
The text was updated successfully, but these errors were encountered: