Announcement

Collapse
No announcement yet.

Qt 6.5 Adding Wayland Native Interface

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • #11
    Originally posted by Danny3 View Post
    Great!
    Now do something about Vulkan support!
    I wonder how lightweight and optimized KDE Plasma would be with Vulkan support?
    As now, at least on Wayland with Intel GPUs seems kinda slow.
    I'm a little skeptical Vulkan support would provide any kind of speed boost for basic desktop use. It's not like it's submitting millions of draw calls per second like a game.

    Maybe it could achieve some more consistent timing which could be helpful in spots.
    Last edited by smitty3268; 10 December 2022, 01:14 AM.

    Comment


    • #12
      Originally posted by oleid View Post

      I once wrote a cli tool which was supposed to create PDF files. It worked well, until I tried to run it on a headless machine. It turned out in order to print you needed a QApplication object, which requires a DISPLAY. Well, in the end I reworked the tool to Cairo and that worked well xD
      I know that it's probably not going to help you any more, but this kind of stuff usually works with QGuiApplication and QT_QPA_PLATFORM=offscreen.

      Comment


      • #13
        Originally posted by smitty3268 View Post

        I'm a little skeptical Vulkan support would provide any kind of speed boost for basic desktop use. It's not like it's submitting millions of draw calls per second like a game.

        Maybe it could achieve some more consistent timing which could be helpful in spots.
        Yeah I was about to say the same, the benefit Vulkan gives here is that its a much lower level API which lets you squeeze out more performance/have greater control of latency plus much saner concurrency handling for multithreaded rendering (which can theoretically be beneficial when simple divide/conquer are a solution, letting you render multiple things on different threads)

        Comment


        • #14
          Originally posted by Zeioth View Post
          QT is getting pretty good.
          Qt was already good.

          Comment


          • #15
            Originally posted by Danny3 View Post
            Great!
            Now do something about Vulkan support!
            I wonder how lightweight and optimized KDE Plasma would be with Vulkan support?
            As now, at least on Wayland with Intel GPUs seems kinda slow.
            You mean like adding QSG_RHI_BACKEND=vulkan to /etc/environment, which is already possible and working?

            Comment


            • #16
              Originally posted by smitty3268 View Post

              I'm a little skeptical Vulkan support would provide any kind of speed boost for basic desktop use. It's not like it's submitting millions of draw calls per second like a game.

              Maybe it could achieve some more consistent timing which could be helpful in spots.
              I'm using KDE with Vulkan and it's a tiny bit faster, but it's especially smoother.

              Comment


              • #17
                Originally posted by chromer View Post
                Easier path for KDE 6 !
                C U next year

                Comment


                • #18
                  Originally posted by smitty3268 View Post

                  I'm a little skeptical Vulkan support would provide any kind of speed boost for basic desktop use. It's not like it's submitting millions of draw calls per second like a game.

                  Maybe it could achieve some more consistent timing which could be helpful in spots.
                  It'd be better than OpenGL drivers in some cases. Not sure if that's what causes chromium to stop painting updates on all windows (I have no idea how to reproduce other than long run timing with plenty of tabs or several hours of youtube videos seems to do i), presumably it's an nvidia issue.

                  On VMware guests with 3D accel, I've also seen some weird rendering issues due to OpenGL there, even though VMware was offloading to Vulkan driver on the host. You had to either go down to OpenGL 2.0 or something in the guest, or use a vulkan renderer (possible for some apps like Chrome to configure), and then that worked smoothly.

                  Chrome in particular was a mess without doing either of those changes, and some kwin compositor effects would just make the screen go black, requiring compositor to be disabled to restore the display.

                  Eventually, Zink is meant to be capable of providing opengl to vulkan for the entire host, but there was some gotchas last I heard about that (might have been related to Wayland, can't recall specifics).

                  Comment


                  • #19
                    Originally posted by Vistaus View Post

                    I'm using KDE with Vulkan and it's a tiny bit faster, but it's especially smoother.
                    Interesting. I knew there were some experiments a couple years ago, but is there an up-to-date version of KWin with a vulkan backend out there somewhere that people can play with?

                    Comment


                    • #20
                      Originally posted by smitty3268 View Post

                      Interesting. I knew there were some experiments a couple years ago, but is there an up-to-date version of KWin with a vulkan backend out there somewhere that people can play with?
                      Add QSG_RHI_BACKEND=vulkan to /etc/environment and reboot.

                      Comment

                      Working...
                      X