3 ms·
That's great! How is WebRender on Wayland + Vulkan progressing by the way? I'm still postponing switch to Wayland, until major KWin bugs (like flickering one)
by shmerl 8y ago
That's great! How is WebRender on Wayland + Vulkan progressing by the way?
I'm still postponing switch to Wayland, until major KWin bugs (like flickering one) are fixed.
- nwah1 8y agoI'm running the nightly on KWin and wayland right now, and typing this from there. Alas, setting about:config gfx.webrender.all to true results in the window being blank, if using it in native wayland mode. Apparently there's some upstream improvements coming to kwayland that will help. WebRender itself is very stable. So much so that it is on by default for beta users on Windows with Nvidia. Recent weeks have also saw much better memory usage.
- shmerl 8y agoBut it's not using Vulkan yet. KWin itslef still has this bug which is very irritating: https://bugs.kde.org/show_bug.cgi?id=387313 https://bugs.kde.org/show_bug.cgi?id=387313
- kvark 8y agoThe Vulkan/D3D12/Metal port is done on the side, and we don't want to disrupt the rollout of the WR-powered Firefox onto wider userbase at this time.
- shmerl 8y agoSo it's planned to be focused on once WebRender is out and enabled everywhere? I see some work here: https://github.com/szeged/webrender/issues/198 https://github.com/szeged/webrender/issues/198
- kvark 8y agoYes, that's the idea, although it's not officially approved by the product management yet. And that link is correct.