Linux Gaming

15834 readers

47 users here now

Gaming on the GNU/Linux operating system.

Recommended news sources:

Related chat:

Related Communities:

Please be nice to other members. Anyone not being nice will be banned. Keep it fun, respectful and just be awesome to each other.

founded 4 years ago

MODERATORS

[email protected]

Wayland vs X11 in Counter Strike 2 (lemmy.world)

submitted 1 day ago* (last edited 1 day ago) by [email protected] to c/[email protected]

7 comments fedilink hide all child comments

Hello,

Recently I was fed up with bad performance in CS2 on Fedora 41 (KDE/Wayland/kernel 6.11.7-300) and started googling around. With my RX6600 I was able to hit 60fps on 1080p/low, but it would often go as low as 40. Trying to change te resolution would cause some strange mouse issues where the game wouldn't let me look to the right or down at all. After reading some posts and getting opposing info, I decided to dnf install plasma-workspaces-x11 and test things out. The X11 session doubled the FPS like it was nothing. A constant 120fps with the possibility to go even higher. Is there something that I could try and fix in Wayland to achieve the same level of performance? As far as I understood, KDE might axe X11 support in the upcomign releases and I wouldn't want to be left behind.

you are viewing a single comment's thread
view the rest of the comments

[–] [email protected] 4 points 1 day ago (1 children)

Use gamescope to run the game under Wayland. Gamescope creates an XWayland window (for which you can specify things like resolution, upscaling, and refresh rate) to run the game in, so the game can pretend it's under X11, and gamescope interacts with Wayland.

[–] [email protected] 9 points 1 day ago (1 children)

Gamescope will add input lag which is something you don't want to have in a game like CS2

[–] [email protected] 1 points 1 day ago* (last edited 1 day ago) (1 children)

Thanks, TIL

How is SteamOS on the Deck dealing with this? I thought they also used gamescope

[–] [email protected] 4 points 1 day ago

Steam Deck runs an embedded session of Gamescope which uses DRM (no not copy protection) to display games.

Running Gamescope as a launch command will run it in a nested session, where it's output is being sent to your display manager, ex. Kwin. That's where the lag can happen, and usually does especially in GPU bound scenarios