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

Gamescope will not run anything #1757

Open
2 of 6 tasks
CoderMonkey1956 opened this issue Feb 26, 2025 · 1 comment
Open
2 of 6 tasks

Gamescope will not run anything #1757

CoderMonkey1956 opened this issue Feb 26, 2025 · 1 comment

Comments

@CoderMonkey1956
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

So i'm trying to get gamescope working with Prism Launcher (just an experiment lol) but I have encountered an issue. How can I fix this (happens with flatpak and native)

"gamescope -w 1280 -h 720 -W 1280 -H 800 -F fsr --" in prism launcher (not a main concern, could be a PL issue) PL.txt

"gamescope -- steam" in Konsole Konsole.txt

Steps To Reproduce

  1. Try to use a custom gamescope command

Hardware information

- Distro: SteamOS 3.6.22
- CPU: AMD Custom APU 0405 (steam deck lcd 256gb)
- GPU: AMD Custom GPU 0405
- Driver Version: Mesa 24.1.0-devel

Software information

- Desktop environment: KDE (steam deck)
- Session type: x11
- Gamescope version: 3.15.15 (gcc 13.2.1)
- Gamescope launch command(s): see current behavior

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

idk what gamescope backed im on

@Quantumdit
Copy link

Quantumdit commented Feb 26, 2025

Not a maintainer, but it looks like like this might be a duplicate of #1218? I see the table_len > 0 error that seems to be indicative of that issue. If so, it's supposed to be fixed next release (1.16.2).

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