Gamescope won't run whatever I do. #1612
Comments
|
What Kisak said here probably applies to this as well: #1557 (comment) I'd try launching Steam and then using Gamescope in the game's launch options like |
|
Hi, thank you for replying. Sorry, I forgot to mention it, but it's the same problem when I do it through launch options. Even running something like |
|
After the Steam client update yesterday I have been experiencing the same issue. Here are the results of running PID: 5390 (gamescopereaper) |
|
Im in a similar boat here, not sure if its exactly the same, but I saw @matte-schwartz reply and wanted to chime in. Im running Arch Linux with Hyprland with a Ryzen 5950X and RX6800XT, if I open Steam and try to run a game without gamescope in the launch arguments it launches. I like to use gamescope because it tends to run smoother, but when I put gamescope in the launch arguments it says launching in steam and crashes before generating a windows. Ive added all sorts combinations of launch argument including things like resolutions and refresh rates, telling it to --expose-wayland with and without specifying --backend wayland, and it will not launch. If I open up a terminal and launch the game through the command line it works fine. Its inconvenient but def not the end of the world, but Id love to get gamescope thru steam launch args working again. Ive also tried switching from vulkkan-radeon to amdvlk and back again, Im using steam-native-runtime, and Ive tried a with a variety of different proton layers. It was working fine a month ago, I havent made any major changes just basic system updates and now it doesnt work. If anyone has any other questions about my system or ideas feel free to @ me. |
|
So this won't help OP & probably won't help many of you, but just in case someone ends up here with the same specific circumstance I was in... My launch options in steam have read like this for months now without issue: The other day suddenly all of my games stopped launching with gamescope. I tried everything I could think of with no answer until I decided on a whim to add the "--" some(but not all) people seemed to have before %command%, like this: Suddenly everything started working again. Not really sure why it was working fine without it before but now suddenly stopped, but yeah... If even 1 person find this post helpful I figure it was worth mentioning. |
Ok that worked for me. I cant believe that was the difference but ok. |
hey, i am obvi not the person you're replying to but its happening to me too. heres a full log with that variable: |
That looks like a different issue to what I have. Possibly related to NVIDIA and maybe the same error OP has. |
Try adding Output of `WAYLAND_DEBUG=client prime-run gamescope -- vkcube`:Output of `ENABLE_GAMESCOPE_WSI=0 WAYLAND_DEBUG=client prime-run gamescope -- vkcube`: |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Is there an existing issue for this?
Are you using any gamescope patches or a forked version of gamescope?
Current Behavior
I can't use it. I've tried every fix I could find by searching online (like trying out modifiers like
--backend). Tried switching to X11, still no dice. I've been trying to get it working for a while now, and I am this close to giving up.What shows when I run Stardew Valley via terminal with
gamescope -- steam steam://rungameid/413150(but this applies to any other game):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: