-
Notifications
You must be signed in to change notification settings - Fork 236
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 windows invisible for Steam games #1707
Comments
Have you tried without |
Exact same problem. When I launch my games, their windows don't appear and aren't registered by my compositor. I can still hear their audio just fine. Nothing more happens before the Looking at my logs, I thought it would be somehow a library/dependency issue, according to this line:
So I rolled back Maybe not a compositor issue either, since mine is different.
Maybe related: #1673 (comment) (same error appears in my log) Output of
There are some localized messages even though I'm running with |
You can only use -e if Steam is also launched inside Gamescope |
I could've sworn that I'd tried without the Unfortunately I won't be available at my desktop until next week to triple check that. |
I can add that I've been using It always worked fine, I even think it was useful for making the Steam overlay work. Is this related to the issue though? |
It was relevant because I've definitely seen |
Okay. Problem solved on my end. Yet another API/ABI breakage. I had I can't fully test with Steam yet because I've got another very bad issue with Mesa drivers. However I think that was another entirely unrelated issue then. |
@xlacroixx If your issue persists outside of Steam, then that sounds like an entirely different issue from OP even if the symptoms are similar. My Plasma+NV setup should be fairly ubiquitous enough though not to be an issue that hasn't been raised before? Aside from the NVIDIA beta driver listed, it's all stable versions (including Steam, albeit run thru Side note: using |
Stupid me, seems like this was caused by calling for a window resolution bigger than my physical display (calling for 4K on a 1440p monitor). |
Is there an existing issue for this?
Are you using any gamescope patches or a forked version of gamescope?
Current Behavior
When
gamescope
is prepended to a Steam game's launch parameters, regardless of switches used, no window ever actually appears - however, the game is still running in the background with audio appearing to play out of... nothing. It simply has to be stopped by cancelling the process from Steam.It seems to affect multiple games, but I've tried with Senko no Ronde 2 and Spelunky just for examples.
Interestingly, in KDE's Wayland session, there are windows that appear linked to gamescope, but they are invisible and nothing comes up when activated - they also don't close when requesting the windows to close, again prompting a force close from Steam's UI.
That said, Gamescope still works normally on this setup with non-Steam titles, using Proton via my own Bottles-like launcher which simply prepends
gamescope [...]
as a scaling option.Steps To Reproduce
gamescope -W (resX) -H (resY) -e -- %command%
Hardware information
Software information
Which gamescope backends have the issue you are reporting?
Logging, screenshots, or anything else
For what it's worth, Gamescope's console output is very similar in all cases, minus the Steam-specific stuff. Pasting in the output running Steam from a CLI:
The text was updated successfully, but these errors were encountered: