From: jaminW55 <jaminW55@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [ISSUE] Package request: gamescope
Date: Wed, 31 Jan 2024 01:12:26 +0100 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-48451@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1931 bytes --]
New issue by jaminW55 on void-packages repository
https://github.com/void-linux/void-packages/issues/48451
Description:
### Package name
gamescope
### Package homepage
https://github.com/ValveSoftware/gamescope
### Description
In an embedded session usecase, gamescope does the same thing as steamcompmgr, but with less extra copies and latency:
It's getting game frames through Wayland by way of Xwayland, so there's no copy within X itself before it gets the frame.
It can use DRM/KMS to directly flip game frames to the screen, even when stretching or when notifications are up, removing another copy.
When it does need to composite with the GPU, it does so with async Vulkan compute, meaning you get to see your frame quick even if the game already has the GPU busy with the next frame.
It also runs on top of a regular desktop, the 'nested' usecase steamcompmgr didn't support.
Because the game is running in its own personal Xwayland sandbox desktop, it can't interfere with your desktop and your desktop can't interfere with it.
You can spoof a virtual screen with a desired resolution and refresh rate as the only thing the game sees, and control/resize the output as needed. This can be useful in exotic display configurations like ultrawide or multi-monitor setups that involve rotation.
It runs on Mesa + AMD or Intel, and could be made to run on other Mesa/DRM drivers with minimal work. AMD requires Mesa 20.3+, Intel requires Mesa 21.2+. For NVIDIA's proprietary driver, version 515.43.04+ is required (make sure the nvidia-drm.modeset=1 kernel parameter is set).
If running RadeonSI clients with older cards (GFX8 and below), currently have to set R600_DEBUG=nodcc, or corruption will be observed until the stack picks up DRM modifiers support.
### Does the requested package meet the package requirements?
System, Compiled
### Is the requested package released?
Yes
next reply other threads:[~2024-01-31 0:12 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-31 0:12 jaminW55 [this message]
2024-01-31 0:15 ` jaminW55
2024-01-31 0:15 ` jaminW55
2024-01-31 0:16 ` jaminW55
2024-01-31 2:27 ` chrysos349
2024-01-31 3:09 ` jaminW55
2024-01-31 3:09 ` [ISSUE] [CLOSED] " jaminW55
-- strict thread matches above, loose matches on Subject: below --
2022-04-26 5:25 [ISSUE] " 0-st
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-48451@inbox.vuxu.org \
--to=jaminw55@users.noreply.github.com \
--cc=ml@inbox.vuxu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).