Announcement

Collapse
No announcement yet.

KDE Sees New Features, Bug Fixes Ahead Of Christmas

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts
    Calinou
    Senior Member

  • Calinou
    replied
    Originally posted by ms178 View Post

    I am still on X11 and can give you anecdotal evidence only there: With my 144 Hz monitor, custom compiled kernel and everything else (mesa, libdrm, llvm and kwinft) trimmed for low-latency (compiled with optimized flags), KwinFT provides a smoother experience than stock KWin which is still acceptable but stuttery and laggy in comparison. Youtube and web browsing are opening nearly instantly and are butter smooth, but I am probably more sensitive to latency than normal users. Kwin low-latency is also a noticeable improvement which I can highly recommend over stock KWin.

    By the way, the desktop experience is between day and night comparing stock Manjaro with my optimized build. Even when benchmarking Company of Heroes 2 (Proton), I get a huge improvement of 17 fps (50 vs 67 fps, a couple of weeks ago I've seen 72 fps, there were some performance regressions during the last eight weeks). Granted, I would get similar FPS on Kubuntu with the Xanmod Kernel or with a LTO'ed Kernel on openSUSE Tumbleweed with much less work, but the desktop experience would be a bit worse still and I am doing it for fun to learn a thing about compilers. I wonder why there is not a bigger push for performance from the distro vendors, especially for the desktop/gaming use case. My own experiences show me that there is still a lot of room for improvements and we haven't even tapped into LTO+PGO yet.
    Does kwin-lowlatency help if you're not using compositing? I have a 144 Hz monitor but I always have compositing disabled (to get the best gaming performance). Being on Fedora 33, I'm wondering if it's worth the trouble to use kwin-lowlatency instead of stock KWin.

    Leave a comment:

  • uid313
    Senior Member

  • uid313
    replied
    Originally posted by Vistaus View Post

    It is, but not exactly innovative or anything. AmigaOS supported that many years ago and current AmigaOS releases still do. So it's actually an old feature that is just now starting to find traction within KDE.
    Yeah, I know, I've heard so. I still think its a pretty cool thing though.

    Leave a comment:

  • timofonic
    Senior Member

  • timofonic
    replied
    Originally posted by Awesomeness View Post

    Well, you guys could apologize for ganging up on him and chasing him away. There were literally no reasons to refuse the Sway compatibility patches on KScreen.
    I agree.

    I consider KDE front must be more open to collaboration.

    Leave a comment:

  • ms178
    Senior Member

  • ms178
    replied
    Originally posted by user1 View Post

    In your experience, what is better in KwinFT compared to vanilla Kwin? I know that vanilla Kwin on x11 suffers from stuttering which is what Kwin-lowlatency fixes. I've also tried Plasma wayland session recently and it seems that Kwin-wayland doesn't have the stuttering issue.
    I am still on X11 and can give you anecdotal evidence only there: With my 144 Hz monitor, custom compiled kernel and everything else (mesa, libdrm, llvm and kwinft) trimmed for low-latency (compiled with optimized flags), KwinFT provides a smoother experience than stock KWin which is still acceptable but stuttery and laggy in comparison. Youtube and web browsing are opening nearly instantly and are butter smooth, but I am probably more sensitive to latency than normal users. Kwin low-latency is also a noticeable improvement which I can highly recommend over stock KWin.

    By the way, the desktop experience is between day and night comparing stock Manjaro with my optimized build. Even when benchmarking Company of Heroes 2 (Proton), I get a huge improvement of 17 fps (50 vs 67 fps, a couple of weeks ago I've seen 72 fps, there were some performance regressions during the last eight weeks). Granted, I would get similar FPS on Kubuntu with the Xanmod Kernel or with a LTO'ed Kernel on openSUSE Tumbleweed with much less work, but the desktop experience would be a bit worse still and I am doing it for fun to learn a thing about compilers. I wonder why there is not a bigger push for performance from the distro vendors, especially for the desktop/gaming use case. My own experiences show me that there is still a lot of room for improvements and we haven't even tapped into LTO+PGO yet.

    Leave a comment:

  • Awesomeness
    Senior Member

  • Awesomeness
    replied
    Originally posted by ngraham View Post
    That would be a question for its developer.
    Well, you guys could apologize for ganging up on him and chasing him away. There were literally no reasons to refuse the Sway compatibility patches on KScreen.

    Leave a comment:

  • Anarchy
    Senior Member

  • Anarchy
    replied
    Originally posted by ngraham View Post

    It is already in Wayland, and unfortunately it's highly doubtful that we will be able to implement it for X11 too.
    That is really unfortunate, this would have been an excellent addition to x11.

    Leave a comment:

  • ngraham
    Senior Member

  • ngraham
    replied
    Originally posted by Anarchy View Post
    Does anyone know if scaling per monitor is also for x11 or is this just a wayland improvement? There is also the font scaling, btw, is this also part of the improvement?
    It is already in Wayland, and unfortunately it's highly doubtful that we will be able to implement it for X11 too.

    Leave a comment:

  • ngraham
    Senior Member

  • ngraham
    replied
    Originally posted by Vistaus View Post

    So? Isn't that the whole point of FOSS? Not just that anyone can fork something and release their own spin, but also that anyone can fork something and merge it back, even if the codebase is out of alignment.
    Sure. but there's a difference between "fork for the purpose of developing features for the parent" and "fork for the purpose of trying to replace the parent or developing the software in a different way". In the latter cases, merging back to the parent becomes more difficult the longer the fork is worked on.

    To be clear, I'd be happy if Roman opts to contribute any of his applicable work back to KWin.

    Leave a comment:

  • Vistaus
    Senior Member

  • Vistaus
    replied
    Originally posted by ngraham View Post
    When a codebase gets forked, it inevitably drifts out of alignment with the parent codebase
    So? Isn't that the whole point of FOSS? Not just that anyone can fork something and release their own spin, but also that anyone can fork something and merge it back, even if the codebase is out of alignment.

    Leave a comment:

  • Anarchy
    Senior Member

  • Anarchy
    replied
    Does anyone know if scaling per monitor is also for x11 or is this just a wayland improvement? There is also the font scaling, btw, is this also part of the improvement?

    Leave a comment:

Working...
X