Earlier quoted context omitted.
It is absolutely not the DE/WM devs driving this, it's the wayland folks saying that xorg would no longer be maintained. They literally just dumped an Ikea box of protocols on the table without even bothering to provide a decent sample implementation and said 'good luck!'
the Wayland folks are the X11 folks though
Measuring Input Latency on Linux: X11 vs. Wayland, VRR, and DXVK
231–240 of 297 posts
Re: Measuring Input Latency on Linux: X11 vs. Wayland, VRR, and DXVK
#232Re: Measuring Input Latency on Linux: X11 vs. Wayland, VRR, and DXVK
#233Re: Measuring Input Latency on Linux: X11 vs. Wayland, VRR, and DXVK
#234> A lot of people still use X11 over Wayland because Wayland is said to have much worse input lag Wayland is fine. People should use AMD and KDE Plasma. I'd avoid Nvidia to begin with.
AMD's Mesa drivers are better, but if you already have an Nvidia card then you can still use it just fine with Wayland. The biggest hit is Vulkan performance (~20% less than Windows iirc) but for desktop and casual gaming use, Nvidia's proprietary drivers are perfectly fine.
Re: Measuring Input Latency on Linux: X11 vs. Wayland, VRR, and DXVK
#235Awesome article. I switched my daily driver / gaming rig to Fedora a few months back. Everything seems snappier compared to Windows, but not sure if it’s in my head, and I’ve been very curious about gaming input latency. This helps answer some questions. I recently switched to hyprland and I’m very interested how that fits in these results. hyprland uses Wayland so I hope the author might revisit now that hyprland is…
Re: Measuring Input Latency on Linux: X11 vs. Wayland, VRR, and DXVK
#236He seems confused at the end why people think wayland is so slow, but don't you think it's because of his xwayland result? People were probably running x11 games on wayland and noticed that significant lag. Just a wild guess. Very nice article, wish people did actual measurements like this more often, of all sorts of things.
No. Wayland is slow on its own. You can test it without Xwayland.
Re: Measuring Input Latency on Linux: X11 vs. Wayland, VRR, and DXVK
#237Earlier quoted context omitted.
There is a wayland equivalent. It's called waypipe. In my experiences it often works better than x11 forwarding.
Unfortunately, there's no wayland server for windows, so you can't use waypipe there without pulling in a linux vm or similar.
But it does not matter that they now have some kind of a solution for a use case for which they denied that it even exists for a long time. I will avoid Wayland because I do not like the direction and the interests that drive it.
Re: Measuring Input Latency on Linux: X11 vs. Wayland, VRR, and DXVK
#238Earlier quoted context omitted.
>give Bazzite a whirl I never really understood Bazzite's immutable fs thing. Can one install standard dev stuff (i.e. compilers, ides, etc) easily under bazzite? This use case is the main reason why I lean towards maybe using cachyos
Yes of course, but you need to do it via the package manager. You can't "sudo make install". If you build your own software and want to install it system wide, you need to flatpack/brew it or run it in a docker container. (obviously you can modify the filesystem if you really really really want to). Bazzite is gaming oriented version of Fedora CoreOs. There are many different versions. I am running bluefin. I've trie…
Why not, this kind of management seems ideal, A/B safe testing for boot.
Lots of containers to go around these days, people are familiar with them and how they work, seems like an obvious sane choice.
Re: Measuring Input Latency on Linux: X11 vs. Wayland, VRR, and DXVK
#239Re: Measuring Input Latency on Linux: X11 vs. Wayland, VRR, and DXVK
#240> Yes, but nowhere near enough to explain why Wayland is generally perceived as much worse than X11.
Personally speaking: Wayland has massive stutters when the system is under load, most notably on the mouse pointer. X11 doesn't.