This also happens in the steam-compositor, not only on Gamescope. Is there a way to test the client with an older version of the runtime so I can pin down if it is a runtime issue?
This issue is now in the mainline version of Steam, and also affects the SteamOS compositor. It is also worse than just flickering: many games will not become focused at all.
While debugging the issue in steamos-compositor-plus I found that the compositor thought there was always a game with ID 413090 running. This "game" is "Steam Controller Configs - Big Picture" according to steamdb. The compositor can only focus a single app window at a time, so the two apps fight for focus and one will win somewhat randomly or the compositor will constantly switch between the two.
Not sure if this is a bug in the Steam client or the consequence of some intentional new feature. For reference, I worked around it with this change:
https://github.com/ChimeraOS/steamos-compositor-plus/commit/cdfc4431b9f47215c439504af3be223eadb4308a
steamos-compositor-plus 1.8.4 in the AUR includes this change.
Hello @alkazar, can you also add a focus note to #8055 if appropriate?
I can confirm the workaround works with current stable and beta client using SteamOS compositor plus.
Gamescope still presents the issue.
There is a fix in the Steam client that is scheduled to release to Beta this week.
Current version beta (1631912732) still flickers (less frequent like instead of each frame, each half-second). The workaround by @alkazar made the games playable but seems to introduce performance issues. I noticed games don't flicker but instead frames need more time to render or use more GPU time.
I'm happy to report that current beta version (1632409172) does not flicker in game :) kudos!
That's awesome!
On Fri, Sep 24, 2021, 6:02 PM Joaquín Ignacio Aramendía <
@.***> wrote:
I'm happy to report that current beta version (1632409172) does not
flicker in game :) kudos!—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/ValveSoftware/steam-for-linux/issues/7966#issuecomment-926986284,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAAB7Y72LHQOTKNX6EX3J7DUDUNSZANCNFSM5BNKZWFA
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
Thanks for confirming.
I've not been testing for a while on the non-beta client. But today I can confirm the issue is gone in (at least) version 1634158817. So I'm closing this one.
Your system information
Please describe your issue in as much detail as possible:
Running Steam BPM under Gamescope as a single-user session under systemd with these scripts games started by the client flicker alternatively a game frame and a blue (wait, three bars) screen. Only happens under current beta, stable client version works without issues.
$ /usr/bin/gamescope -e -f -- steam -tenfoot -steamos -fulldesktopres)Game starts flickering a blue "wait" (three bars) screen from Steam client and a game frame alternatively.