136
Measuring input latency on Linux: X11 vs Wayland, VRR, and DXVK - Marco Nett (marco-nett.de)
submitted 2 weeks ago by to c/linux_gaming@lemmy.world
22 comments fedilink hide all child comments
you are viewing a single comment's thread
view the rest of the comments
[–] 8 points 2 weeks ago (3 children)

Without dxvk-low-latency, XWayland adds 3.13 ms of latency to the measurement.

Can 3ms actually be noticed? Like if you randomly select one mode and did a "blind" test to see if you can tell the difference which mode is on? This honestly sounds impossible to me.

  • permalink
  • fedilink
  • source
  • hideshow 6 child comments
    •
  • [–] 10 points 2 weeks ago

    If you're familiar with the setup and play something where latency matters (competitive FPS and rhythm games cone top mind) I guess it might be enough to their you off your game.
    But on an unknown system, where you have no comparison, I'm not so sure.

  • permalink
  • fedilink
  • source
  • parent
  • [–] 2 points 2 weeks ago (1 child)

    3ms by itself prolly not. But it adds up, if you add input lag, monitor lagetc.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [–] 7 points 2 weeks ago

    The 3ms is the full end-to-end latency. From the click to the monitor updating with the result.

    3ms isn't noticeable, even the worst performer (xwayland) only hit 8ms which wouldn't be noticed outside of very specific games.

    Fighting games' frames are around 17ms and moves that require hitting a single frame are nearly impossible to perform consistently.

  • permalink
  • fedilink
  • source
  • parent
  • [–] 2 points 2 weeks ago (1 child)

    I guess 3ms would not be noticeable to most people.

    It would be interesting to see how this behaves at lower refresh rates. Loosing the same 1 or 2 frames at 60/144 Hz should be noticeable.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •