protonscr

Most of Steam Overlay Cannot Be Interacted With on Scaled Display on Wayland

steamclosed overlayDistro Family: Arch
ValveSoftware/steam-for-linux#11126 · opened 2024-07-23 by sonic2kk · updated 2024-10-16 · 5 comments · github
Ssonic2kk 2024-07-23 github

Your system information

  • Steam client version (build number or date): 1721420033
  • Distribution (e.g. Ubuntu): Arch Linux with KDE Plasma Wayland 6.1.3
  • Opted into Steam client beta?: Yes
  • Have you checked for system updates?: Yes
  • Steam Logs: steam-logs.tar.gz (maybe it'll have some information about what display size the Steam Overlay can see?)
  • GPU: AMD Radeon 7900XTX

Please describe your issue in as much detail as possible:

When opening the Steam Overlay, only a small portion of it can be interacted with. Some windows overlayed on top, such as the Friends List, can be interacted with just fine. But all of the buttons except for the "Exit Game" button cannot be interacted with.

As a result of this issue, it is not possible to interact with any of the bottom portion of the Steam Overlay (to open the Web Browser, Achievements, etc) or to interact with the Overlay "X" button in the top-right.

I assume this is a result of using a scaled display on Wayland. I am using a 3840x2160 display scaled to 150% from the KDE Plasma display scaling settings, although I also have multiple monitors and none of my other displays are using scaling (and using a combination of scaled and unscaled displays has caused Wayland headaches in the past on various Wayland sessions).

There are similar issues with the new Game Recording UI (#11025), but it now extends to much of the Steam Overlay. I cannot test to confirm but I imagine the interactive region is a small square of the available overlay that the "Exit Game" button happens to be inside of, so I don't think this is a case of only one button being interactable.

Steps for reproducing this issue:

  1. Use a scaled display on KDE Plasma Wayland 6.1.3
  2. Activate the Steam Overlay in a game
  3. Much of the overlay cannot be interacted with, but some parts can (such as the Friends List)
TTTimo 2024-07-29 github

What do you have selected for Legacy applications (X11)? Does switching between the two settings and restarting affect reproduction? Which game are you testing this with?

Ssonic2kk 2024-07-29 github

I have "Apply scaling themselves", which means the Steam Client and so games are not blurry on my scaled displays. I will check later if changing this setting helps, but this would unfortunately not be a viable workaround as I would be unable to play games at native 4k with my 150% scaled display (fwiw, this X11 scaling setting is the default on KDE Plasma these days, although it wasn't at first when I enabled it iirc).

This affects any game I have tested, but the ones I recall recently are:

  • Cookie Clicker (Proton)
  • To the Moon (Native)
  • Sonic Adventure (Proton)
Ssonic2kk 2024-08-04 github

Sorry for the delay. This issue is not resolved when using the "Scaled by the system" option, so there is no workaround for this issue. Most of the Steam Overlay cannot be interacted with regardless of whether "Apply scaling themselves" or "Scaled by the system" is used.

Ssonic2kk 2024-09-28 github

This has actually regressed slightly since I posted this, and now the Friends List dialog and most dialogs cannot be interacted with on the Steam Overlay. The Game Information dialog can be to some extent.

The "Exit Game" button still works, but much of the rest of the Steam Overlay still cannot be interacted with. I have not found any workaround for this yet.

Ssonic2kk 2024-10-16 github

Woohoo! This has been fixed at least as of the current Steam Beta:

Steam Beta Branch: Steam Beta Update
Steam Version: 1729015347
Steam Client Build Date: Tue, Oct 15 18:45 UTC -08:00
Steam Web Build Date: Mon, Oct 14 22:56 UTC -08:00
Steam API Version: SteamClient021

I cannot pinpoint the exact time when this was fixed, which is why I am reporting this as fixed "at least" in the current Beta. It may have been fixed in a previous Beta.

Closing as this issue is now resolved!

Nothing extracted yet.