Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Adaptive sync affected by mangoapp in gamescope #1724

Open
3 of 6 tasks
dinotheextinct opened this issue Jan 27, 2025 · 1 comment
Open
3 of 6 tasks

Adaptive sync affected by mangoapp in gamescope #1724

dinotheextinct opened this issue Jan 27, 2025 · 1 comment

Comments

@dinotheextinct
Copy link

Is there an existing issue for this?

  • I have searched the existing issues

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

  1. Launch anygame with gamescope --adaptive-sync --mangoapp
  2. check actual refreshrate of your monitor (e.g. in the OSD) while gaming
  3. notice spiky behaviour

Hardware information

- Distro: 
NAME="openSUSE Tumbleweed"
# VERSION="20250125"
ID="opensuse-tumbleweed"
ID_LIKE="opensuse suse"
VERSION_ID="20250125"
PRETTY_NAME="openSUSE Tumbleweed"
ANSI_COLOR="0;32"
# CPE 2.3 format, boo#1217921
CPE_NAME="cpe:2.3:o:opensuse:tumbleweed:20250125:*:*:*:*:*:*:*"
#CPE 2.2 format
#CPE_NAME="cpe:/o:opensuse:tumbleweed:20250125"
BUG_REPORT_URL="https://bugzilla.opensuse.org"
SUPPORT_URL="https://bugs.opensuse.org"
HOME_URL="https://www.opensuse.org"
DOCUMENTATION_URL="https://en.opensuse.org/Portal:Tumbleweed"v
LOGO="distributor-logo-Tumbleweed"
- CPU: 
PU: 6-core AMD Ryzen 5 5600X (-MT MCP-) speed/min/max: 3597/550/4651 MHz
Kernel: 6.13.0-1-default x86_64 Up: 4h 3m Mem: 13.33/31.25 GiB (42.7%)
Storage: 4.55 TiB (75.8% used) Procs: 550 Shell: fish inxi: 3.3.37
- GPU: AMD Radeon RX 7900 XT (RADV NAVI31)
- Driver Version: Mesa 24.3.4 (LLVM 19.1.7)

Software information

- Desktop environment: KDE 6.2.5
- Session type: wayland
- Gamescope version: [gamescope] [Info]  console: gamescope version  (gcc 14.2.1
- Gamescope launch command(s): gamescope -W 3840 -H 2160 -f --force-grab-cursor --adaptive-sync --hdr-enabled --mangoapp

Which gamescope backends have the issue you are reporting?

  • Wayland (default for nested gamescope)
  • DRM (default for embedded gamescope, i.e. gamescope-session)
  • SDL
  • OpenVR

Logging, screenshots, or anything else

No response

@matte-schwartz
Copy link

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants