forked from ValveSoftware/steamos-compositor
-
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
Disable Layers Automatically When Needed (Optimus?) #560
Comments
This was referenced Jul 21, 2022
nrdxp
added a commit
to nrdxp/gamescope
that referenced
this issue
Jul 23, 2022
Minimally fixes ValveSoftware#560
nrdxp
added a commit
to nrdxp/gamescope
that referenced
this issue
Jul 23, 2022
Minimally fixes ValveSoftware#560
nrdxp
added a commit
to nrdxp/gamescope
that referenced
this issue
Jul 23, 2022
Minimally fixes ValveSoftware#560
nrdxp
added a commit
to nrdxp/gamescope
that referenced
this issue
Jul 23, 2022
Minimally fixes ValveSoftware#560
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I found recently that the
--disable-layers
flag was necessary for the embedded mode to work properly on my setup. I posted some details and a few debug logs in another issue #526 (comment)I was a little suprised to see KMS (libliftoff) and Vulkan interacting at all since I thought (from my non-expert view) that the former was for GL applications while the later had its own VK_KHR_DISPLAY for rendering directly to a DRM device so I tried disabling layers based on this hunch and it ended up working. I figured that instead of failing without the flag, that perhaps gamescope could intelligently detect when one or the other is needed.
Perhaps I don't understand things clearly but this would definitely be better UX than everyone with Optimus (et. al?) hardware thinking this doesn't work. #526 (comment)
The text was updated successfully, but these errors were encountered: