this post was submitted on 27 Jan 2025
24 points (92.9% liked)

Linux

8605 readers
151 users here now

Welcome to c/linux!

Welcome to our thriving Linux community! Whether you're a seasoned Linux enthusiast or just starting your journey, we're excited to have you here. Explore, learn, and collaborate with like-minded individuals who share a passion for open-source software and the endless possibilities it offers. Together, let's dive into the world of Linux and embrace the power of freedom, customization, and innovation. Enjoy your stay and feel free to join the vibrant discussions that await you!

Rules:

  1. Stay on topic: Posts and discussions should be related to Linux, open source software, and related technologies.

  2. Be respectful: Treat fellow community members with respect and courtesy.

  3. Quality over quantity: Share informative and thought-provoking content.

  4. No spam or self-promotion: Avoid excessive self-promotion or spamming.

  5. No NSFW adult content

  6. Follow general lemmy guidelines.

founded 2 years ago
MODERATORS
MigratingtoLemmy
24
X11 vs Wayland cursor latency (mort.coffee)
submitted 2 days ago by Feathercrown to c/linux
6 comments fedilink hide all child comments
 

I don't think he should have included the starting frame-- if the cursor were theoretically instant, his method records it with a 1 frame delay, and this +1 frame error happens on every test. Correcting this actually makes Wayland more laggy proportionally, although it makes both less laggy absolutely.

you are viewing a single comment's thread
view the rest of the comments
[โ€“] [email protected] 8 points 2 days ago* (last edited 2 days ago) (1 children)

What I've noticed with Wayland in Plasma is that it's very much tied to my monitors refresh rate.

At 240Hz, with adaptive sync turned off or to Automatic, I get a very responsive cursor.

At 75Hz, or if I force adaptive sync to be on at all times (instead of off or Automatic), then I get a noticeable mouse latency

[โ€“] [email protected] 1 points 2 days ago* (last edited 2 days ago)

Plasma

I don't perceive this with Sway (1.10-2) using a mouse being polled at 1000 Hz.

When I turn on my monitor's FPS display and my mouse is not moving, the monitor reports that the frame rate drops down to the lowest rate available (48 Hz), then when the mouse is moving, jumps up to the highest rate.

investigates

Hmm. Apparently there's someone complaining about that behavior occurring in games during mouse movement, and saying that Sway's behavior is a bug.

https://github.com/swaywm/sway/issues/6832#issuecomment-1079941291

I start a game (for example Overwatch, or Witcher 3 - both are running through wine). Normally the game would run at a framerate higher than 165fps
I cap the framerate (for example with Overwatchs ingame limiter, MangoHud, or Gamescope), to something lower, for example to 100fps
FreeSync is working, which I can see because my monitor displays the current refresh rate
As soon as I move the mouse, the refresh rate jumps up to 165

The effect does not occur in Plasma Wayland (with Kwin)

I guess the concern is that one doesn't want that to happen in a typical fullscreen game that can't render at the monitor's full frame rate, but do want to with, say, the desktop environment to keep the pointer responsive.

Honestly, while I use adaptive sync, I only really care about it for fullscreen movie playback, where I want the monitor to be able to run at the movie's framerate. I actually hadn't even thought about the fact that it affects games. Hmm.