great
Measuring Input Latency on Linux: X11 vs. Wayland, VRR, and DXVK
151–160 of 297 posts
Re: Measuring Input Latency on Linux: X11 vs. Wayland, VRR, and DXVK
#152Well written article with a lot of interesting info. I do wish there was a comparison to Windows as well though, as a frame of reference.
Re: Measuring Input Latency on Linux: X11 vs. Wayland, VRR, and DXVK
#153Earlier quoted context omitted.
Some things do indeed improve, but some other things require a massive effort that no hobbyist or small company can make happen. This is most obvious in places where a lot of coordination is required, for example in supporting proper color correction throughout all applications, or decent support for advanced printer functions. There are many incremental changes, but we often get stuck in local minima for years. Stil…
Because if it's open source you can't make money from it or have multiple tiers.
If it's open source you can make money by selling managed services to companies. They don't want to deal with it really.
Re: Measuring Input Latency on Linux: X11 vs. Wayland, VRR, and DXVK
#154X11 is a protocol. Xorg is an end of life'd project run by the Wayland team. Xlibre is an actively developed and maintained X11 protocol display server. Xfree86 is dead, long live Xorg. Xorg is dead, long live Xlibre!
Xenocara does it better than XLibre.
Re: Measuring Input Latency on Linux: X11 vs. Wayland, VRR, and DXVK
#155It looks like consoles and PCs have settled on somewhat different gaming configurations. Consoles usually try to target a fixed output frame rate, while the resolution is often dynamic. On PCs, by contrast, the resolution stays static, while the frame rate and frame-time pacing are dynamic. How does this fit into the latency discussion? Especially in competitive gaming, I often see people targeting frame rates way be…
[dead]
Re: Measuring Input Latency on Linux: X11 vs. Wayland, VRR, and DXVK
#156Earlier quoted context omitted.
The context here is the article's author is a twitchy FPS player, those extra 3ms are something that community agonizes over. I appreciated how much effort was put into controlling the variables in this test. There's a whole lot of witchcraft associated with these kinds of efforts and he sat down and did the measurements and got real numbers. My hat is off to OP.
ping is going to dominate over 3ms in pretty much every situation. And the non-xwayland numbers are all within a single ms of each other. --- Not to undermine the measurements of the author (agree with you, it's a cool effort), but my read is that this was basically proof that it doesn't matter.
It doesn't matter. Whether you have a ping of 40 or a ping of 300, 3ms is 3ms and will mean you win a little less often.
The saying we have in bike racing marginal gains is "leave no stone unturned, but turn over the big ones first"
So sure, first make sure your internet connection is solid. Then make sure your hardware and game settings are optimizing FPS to a reasonable point of diminishing returns.
Then make sure you don't use XWayland
Re: Measuring Input Latency on Linux: X11 vs. Wayland, VRR, and DXVK
#157Something interesting is the author right away wants to isolate and reduce placebo. But surely, latency is all about "placebo" and "vibes" and "feel" is it not? The ultimate test is how it feels to use on a personal level.
Of course, where gathering this sort of data _is_ useful is diagnosing and fixing real latency so it obviously has merit. I just think it's ok to lean on taste and experience for most things UI/UX, including latency.
Another point, by couching the comparison in a less technical form (for example, rating a configuration/setup out of 5 stars or some similar approach), it protects from being "too methodological" during testing and data-gathering. One possible issue with the author's methods is if there are degenerative cases that are common in the day-to-day experience of a given configuration, they are unlikely to be present during the precise test that they have setup.
Re: Measuring Input Latency on Linux: X11 vs. Wayland, VRR, and DXVK
#158Earlier quoted context omitted.
Because if it's open source you can't make money from it or have multiple tiers.
If it's open source you can make money by selling managed services to companies. They don't want to deal with it really.
How is Red Hat's revenue compared to Microsoft's?
Re: Measuring Input Latency on Linux: X11 vs. Wayland, VRR, and DXVK
#159Earlier quoted context omitted.
The context here is the article's author is a twitchy FPS player, those extra 3ms are something that community agonizes over. I appreciated how much effort was put into controlling the variables in this test. There's a whole lot of witchcraft associated with these kinds of efforts and he sat down and did the measurements and got real numbers. My hat is off to OP.
ping is going to dominate over 3ms in pretty much every situation. And the non-xwayland numbers are all within a single ms of each other. --- Not to undermine the measurements of the author (agree with you, it's a cool effort), but my read is that this was basically proof that it doesn't matter.
You can genuinely feel just a few milliseconds of input latency with a mouse, it disconnects looking around with your physical actions. It's the same way you can feel the difference between low and high refresh rate monitors, even though you can't really count the frames themselves
Re: Measuring Input Latency on Linux: X11 vs. Wayland, VRR, and DXVK
#160This website uses IP address blocking to censor itself, and deserves to be publicly shamed for it. Here's an archive link: https://archive.is/hrYZ6
Hello, this is my website and I do not know what you mean by this. If you give me technical details (like the subnet your operating out of), I can take a look at it. My webserver is using crowdsec ( https://www.crowdsec.net ) to ban malicious IPs and I would guess that you are somehow unintentionally affected by this. You can also test your IP by entering it into the crowdsec website to see if it is affected.
There you go then. Thank you for confirming my determination of IP blocking. The archive link above may work for the users you censor.
Paying $1900/month for an IP address blocklist for a website? Yikes.