KDE is more attentive to gaming use cases than Gnome.

View this comment - View article - View full comments

Secrecy of console companies is such a total dinosaur of an idea.

It would be nice for Godot to compete with the likes of Unreal Engine.

View this comment - View article - View full comments

KDE supports it better, yeah. Except some scenarios where cursor breaks it, which I think is being addressed at Wayland protocol level before compositors will fix it. But Gnome just doesn't seem to focus on gaming use cases in general, so it takes them forever to add any adaptive sync support.

View this comment - View article - View full comments

Quoting: tohurinput lag from vsync has squat to do with refresh rate honesly

It has a lot to do with that I'd say. If refresh rate is low (60 Hz) and compositor waits for vertial sync, you'll notice lag. Tearing means compositor doesn't wait and draws even if it will result in jagged image, so you'll see updates before the full refresh cycle even happens, which in practice means lower latency (lag). That kind of scenario benefits from enabling tearing.

Scenario when your refresh rate is 144 Hz and more reduces the period of blanks low enough that you don't notice anything even if compositor waits for it. But more importantly, you need to have adaptive sync (VRR) in order to avoid unnecessary waits. That's an improvement of the old style vsync.

There was a thread about it here: https://www.gamingonlinux.com/forum/topic/5185/

Here is a useful diagram:



I think using Vulkan mailbox present mode above the monitor refresh rate is similar to what AMD means by "enhanced sync".

View this comment - View article - View full comments

Quoting: tohurbruh you clearly haven't compared GNOME vs KDE in this regard.. the Input lag in shooters and the such is bad enough it is noticeable lol. plenty of recent bug reports/ feature request out there to prove it is an issue now

I think Gnome's input lag has nothing to do with refresh rate, they just didn't optimize their own compositor for lower latency unlike KWin developers did. I.e. besides refresh rate delaying drawing, input lag can be caused by simply compositor doing any stuff before it's ready to draw. If you have too much of that - you'll have lag.

So yeah, Gnome might have such issue, but adding tearing won't help it if they don't optimize what they aren't doing efficiently, that's my point.

View this comment - View article - View full comments

Quoting: tohurThe reason you turn Vsync off is input lag.. granted you don't notice it in most games but fast paced games you need Vsync off because in competitive games even moderate lag will get you killed. GNOME doesn't allow for you to turn it off in wayland and trust me in wayland you want Vsync off because with it on the lag is terrible.. for my preferred games GNOME is bad bad LMAO.. in KDE wayland there is a setting to allow screen tearing aka turnk off vsync for full screen apps aka games. the overall gaming experience is better on KDE

I said it before, but whole turn vsync off for input lag idea is like couple decades or more old and is in practice outdated.

It originates from the time when everyone had 60 Hz displays. Those who worry about input lag today don't use such displays, so with adaptive sync and 144 Hz display (or even more) having tearing above monitor refresh rate range is of little value, because you won't notice much of a difference.

If you have 60 Hz monitor still - then yeah. So it's useful that KDE supports such scenario, but less useful than how it sounds.

View this comment - View article - View full comments

About restarting the desktop shell, in KDE at least, It's Alt + F2 and then:

killall plasmashell; plasmashell

Not needed often, but doesn't feel complicated.

View this comment - View article - View full comments

Quoting: slaapliedjeScreen sharing is possible in Xorg. Isn't that one of the things that is broken in Wayland?

Works fine in OBS for video capturing, so it's not broken. It needs mechanisms like portals or the like since it's a security related feature.

There is also this wip:

https://planet.kde.org/arjen-hiemstra-2023-08-08-remote-desktop-using-the-rdp-protocol-for-plasma-wayland/ [External Link]

View this comment - View article - View full comments

If anyone still asks "why Wayland instead of X", revisit this video:

https://www.youtube.com/watch?v=GWQh_DmDLKQ [External Link]

View this comment - View article - View full comments

Quoting: EikeIs the option Wayland only?

It probably is Wayland only, but I haven't tested it.

View this comment - View article - View full comments