jazztickets@lemmy.world to Linux Gaming@lemmy.worldEnglish · 12 hours agoMeasuring input latency on Linux: X11 vs Wayland, VRR, and DXVK - Marco Nettmarco-nett.deexternal-linkmessage-square21fedilinkarrow-up1106cross-posted to: linux@programming.dev
arrow-up1106external-linkMeasuring input latency on Linux: X11 vs Wayland, VRR, and DXVK - Marco Nettmarco-nett.dejazztickets@lemmy.world to Linux Gaming@lemmy.worldEnglish · 12 hours agomessage-square21fedilinkcross-posted to: linux@programming.dev
minus-squarePrunebutt@slrpnk.netlinkfedilinkEnglisharrow-up3·8 hours ago3ms by itself prolly not. But it adds up, if you add input lag, monitor lagetc.
minus-squareFauxLiving@lemmy.worldlinkfedilinkEnglisharrow-up4·6 hours agoThe 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.
3ms by itself prolly not. But it adds up, if you add input lag, monitor lagetc.
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.