You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm not sure if it's Mesa, Steam, or gamescope that is the culprit, but something changed in the last two months or so that causes the Intel OneXPlayer 1S to not render gamescope if xwayland-count 2 is used. If I use xwayland-count 1 I'm able to use gamescope-session, but the overlays are broken.
This is seemingly a hard requirement for Intel devices in general, but if I don't set -w 1280 -h 800 I get the same black screen on other devices as well.
In both instances you'll hear the Steam deck boot sound with no picture. This would appear to be a regression of some sort because this was never an issue before.
ruineka
changed the title
[ANV/Intel] --wayland-count 2 causes black screen for Steam's gamepadui
[ANV/Intel] Some intel devices won't render if --xwayland-count 2 is used
Mar 9, 2023
I'm not sure if it's Mesa, Steam, or gamescope that is the culprit, but something changed in the last two months or so that causes the Intel OneXPlayer 1S to not render gamescope if
xwayland-count 2
is used. If I usexwayland-count 1
I'm able to use gamescope-session, but the overlays are broken.This is seemingly a hard requirement for Intel devices in general, but if I don't set
-w 1280 -h 800
I get the same black screen on other devices as well.In both instances you'll hear the Steam deck boot sound with no picture. This would appear to be a regression of some sort because this was never an issue before.
Here is the link to the session we use https://github.com/ChimeraOS/gamescope-session
I see that the g_nNestedHeight is calculated but never set in the mode. Is this intentional?
https://github.com/Plagman/gamescope/blob/a3dc37f2621a4e561434068cab4a97677406d5af/src/steamcompmgr.cpp#L6404
edit:
I downgraded to gamescope-3.11.32-1 and it has the same black screen issue, so it's not necessarily a regression with gamescope itself.
The text was updated successfully, but these errors were encountered: