Gamescope breaks Steam Overlay #835
Comments
|
Can you try Steam Beta? |
I did right now and that changed nothing. I would like to mention, that forcing gamescope to start the game in fullscreen (-f) leads to a black screen with not launching the game at all. I then need to kill the game and the gamescope process. Below two screenshots showing the malformed mouse cursor: Oh and hotkeys only work by pressing super + alt/ctrl, too. |
|
I tried it with Cyberpunk 2077 and Steam Overlay isn't working in there too. Looks like it isn't related to external programs, or it isn't a game specific issue, i'm not sure. |
|
Something has changed while I was a few days away. |
|
@Milliw I'm having this issue still. Is the overlay still working for you? I can't seem to get it to work at all and I'm trying to figure out if it's just me or if there are just very few people who use it. I found #810 which seems to be the same thing. In my comment there I have some details about my env. Stuff I've tried so far has been:
Here's a successful launch of Dirt Rally 2.0. The overlay does not work in any of the games I have tried but this is one that I play often. I started the game, waited until it was running in the start screen, attempted to launch the overlay with Shift+Tab (at that point it should have already shown the popups which also didn't appear), and then force-exited the game. This is a game where the overlay is necessary to invite people to multiplayer races, so the multiplayer functionality of the game is broken due to this issue. Click to expand log text
|
|
I just discovered that the overlay, or rather a close relative of the overlay, works in big-picture mode. So if you launch steam with gamescope like so (resolution of my display just as an example): And then enter big picture mode and launch a game, the invite functions in multiplayer games launch the big picture version of the overlay which works fine and all the menus work. The only issue is that there's no way to get the overlay to appear in game without a controller. Everything else can be done with the keyboard but displaying the overlay is not possible from what I can tell, you have to be able to press the "steam" button or equivalent button on another controller type. |
Nah.... it's changing from time to time... |
|
For me steam overlay not working inside gamescope regardles of game (for a long time). Up to date EndeavourOS with KDE Wayland, RX 6600XT |
|
I'm not entirely sure what caused the overlay to stop working in gamescope, but I found a way to work around it:
|
|
That's some interesting method! |
|
Does anyone have news on this? I tried again today and my state is now, that Steam overlay works, but Hunt: Showdown says "enable steam overlay"... |
|
@Milliw what version of gamescope are you using? EDIT: And to answer your question, I haven't been able to get it to work, but also I didn't feel like installing an experimental version of mesa so I haven't tried the latest which I think is 3.12.5.r23.gb19e928 |
|
3.12.3-16 @kevenwyld Interestingly after having no success with gamescope yesterday I disabled gamescope but left overlay enabled and invite/overlay worked the whole evening with no game crashing. |
I'm testing in Arch\EndeavourOS with Gnome 44.5 (Thinkpad T450 with Intel Graphics) and I also when I remove the "-- %command%" games like Wingspan and World of Tanks Blitz that the games launch. So my working launch configuration is "gamescope --expose-wayland". So like you all, I"m trying to find out what %command% does. |
%command% should refer to the game's executable |
|
Thanks for the heads up on %command%. I think what I was really looking for is why the "gamescope --expose-wayland" will run without the %command%. Because the game (World of Tank Blitz" still launches. |
This is the only way I've been able to get the Steam Overlay in Risk of Rain Return. Thank you. (Archlinux, Swaywm) Using |
Just wanted to add I have the same issue and this workaround DOES work, but only if you launch gamescope without I also haven't been able to get this workaround working entirely via steam launch options yet. So it's just another thing to add to my custom script. I tried something like: which in theory should launch gamescope, wait for it to create the screen, and then pass it to the launching game via DISPLAY. In practice, the game never fully launches. Wish the devs would take a look at fixing the overlay so this workaround isn't needed! |
|
Running Fedora 39 KDE on Wayland. Up until December 14th the Steam overlay was working for me in gamescope on Wayland. I use the sentry copr for my kernel, and I first noticed problems with gamescope when I was on 6.6.7-202. Switching to x11, all kernel versions launch gamescope as expected, with working overlay. On another drive, I have an updated fresh install of Fedora 39 KDE with the bare minimum amount of tweaks. In all instances I'm using the Steam rpm, beta enabled. GPU is a 6700XT. One more thing that is definitely outside the scope for this issue, but might be relevant? Update: While messing around with dnf, I found I had wlroots 0.17.0 available despite it not showing up before. |
|
Could some folks here try adding This resolved the issue with steam overlay not working in gamescope for me and it may possibly fix it for you folks also. my exact launch options for gamescope are
|
|
@Eckoa well that's a bit embarrassing, could have sworn I tried that but you're right it works. Unfortunately placing that env var at the beginning like you have forces the gamescope window to run with xwayland, instead of wayland native. This is not ideal since gamescope does in fact support wayland, however it does maybe explain why things aren't working since I think wayland support might be relatively new and experimental. It's also a pretty good workaround though. |
I havent tested placing it after gamescope, I just tossed it into my launch options to see if it would work. Im not really concerned myself of xwayland or native wayland and care more about it functioning XD |
What I mean to say is that I think gamescope running in wayland native mode is the reason the overlay is not working. So placing it after won't have the same impact. |
gotcha, very well could be the case. I decided to test it after seeing someone having issues running GLmark with gamescope and they came to the conclusion the SDL wayland driver has some sort of bug as the X11 option fixed launching GLmark |
|
Another part to the SDL driver workaround may require you to pass The SDL workaround leaves the steam overlay mouse being huge but the games mouse is the proper size and passing the cursor theme fixes the game using the wrong cursor in the case of games that dont have their own. |
|
The SDL workaround doesn't seem to work for Helldivers 2; was hoping that it would but it didn't. :/ |
|
Right know I see that I can run a game in gamescope once but when I quit it I need to restart whole steam to play any other game. SDL workaround also doesn't seem to work. |
I am facing the same issue, and this is the only thing that fixed it for me. Running on version 3.14.0. |
|
That's the only way I've gotten it to work too, except I had to set the DISPLAY value to Terminal Output:Command: |
|
Hello everyone, for those still encountering this issue, I strongly advise against manipulating the DISPLAY environment variable. This variable appears to be linked to the physical device layer hierarchy itself. I have managed to resolve this issue in two Arch Linux installations with Gamescope Session Git, using the following export GAMESCOPE_WAYLAND_DISPLAY=:`1`Upon debugging through a tty session, I noticed that my By setting the |
You running the gamescope session or nested here? because pretty sure youre just running a session if youre using Gamescope Session Git . If youre running the session that has never been a problem afaik and running gamescope as your session is completely different from trying to solve the issue while running it nested within another compositor such as kwin or mutter. What myself and others have attempted to do is solve the nested issue, which when you run gamescope in a terminal will output the wayland display it is on then you just use point the game to that. I personally use the SDL workaround for it so i dont have to do that and it works for my use case. |
I'm sorry. I know this thread primarily focuses on addressing issues related to nested compositing with Gamescope. But, recently, some users, including myself, have encountered similar problems when running Gamescope in a standalone session without any additional compositor. The nature and cause of these issues are currently unclear but may be related to recent changes in Mesa or RADV libraries, which could impact both nested and standalone sessions. What I know is that custom Mesa patched libraries (such as used by Chimera), or more "outdated" versions of Gamescope, didn't result in these overlays errors. |
|
Ran into this again after moving to CachyOS and trying to set up Gamescope to work around Underrail's issues. |
When I run "Hunt: Showdown" with gamescope the Steam overlay is not working anymore.
Also mouse pointer is not shown correctly depending on launch options I tried.
Tried several options: -e, -f, -b, --dbug-hud, --adaptive-sync (latter two don't do anything)
Tried different Proton versions: GE-7.51, Experimental, 7.0.6
OS: Nobara 37, Gnome 43.2, Wayland
GPU: Nvidia RTX2060, driver v 525.85.05
Kernel: 6.2.6-201.fsync.fc37.x86_64 (Nobara standard)
Only wanted to try gamescope because of mouse escaping the game from time to time and also crashes sometimes.
Enabled proton log, too but couldn't find out what of the many entries are breaking the overlay/game.
I think, it has maybe something to do with EAC (Easy Anti-Cheat) or the way the game is started by Steam because at launch the usually displayed, small starting window is not shown but instead there is a black screen/window showing some blue, disturbed graphics in it.
The text was updated successfully, but these errors were encountered: