Considering the history of KDE and how long it took to get rid of those pesky memory management and pointer related bugs, I'd rather see OpenGL (ES) continue to be used. It's a stable codepath and has seen lots and lots of testing on different hardware.
Even old CPUs like a Core2Duo @1.86Ghz can cope with running a KDE session smoothly, so I really don't know which benefits people expect from using Vulkan instead of GL in this specific case.
IMO the only things it would bring is a loss of backwards compatibility (if the GL codepath is eventually deprecated/dropped) and introducing lots of new bugs while increasing code complexity, maintenance burden and the need for development time significantly.
Announcement
Collapse
No announcement yet.
Qt 6.5 Adding Wayland Native Interface
Collapse
X
-
Originally posted by Danny3 View Post
Tried it but it doesn't seem to do anything noticeable.
I even activated the FPS effect before and after to see some number and I even saw FPS numbers in the 40-50 range from the normal 60 FPS after activating it, so I don't think it works.
Maybe it will when KDE software will be compiled with Qt 6.
- Likes 2
Leave a comment:
-
Originally posted by Vistaus View Post
You mean like adding QSG_RHI_BACKEND=vulkan to /etc/environment, which is already possible and working?
I even activated the FPS effect before and after to see some number and I even saw FPS numbers in the 40-50 range from the normal 60 FPS after activating it, so I don't think it works.
Maybe it will when KDE software will be compiled with Qt 6.
Leave a comment:
-
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?
- Likes 3
Leave a comment:
-
Originally posted by Vistaus View Post
I'm using KDE with Vulkan and it's a tiny bit faster, but it's especially smoother.
- Likes 1
Leave a comment:
-
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.
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).
- Likes 1
Leave a comment:
-
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.
- Likes 1
Leave a comment:
-
Originally posted by Danny3 View PostGreat!
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.
- Likes 1
Leave a comment:
Leave a comment: