![]() So on X11 the default will stay GLX, while on Wayland the only option is EGL. We decided that it doesn’t make sense to expose a config option which in most cases will result in the users systems being broken. Way too often we saw bug reports about rendering being broken and it was caused by using EGL. Unfortunately EGL is still not a good enough option on X11. Removal of GLX/EGL selectionĪ change which also got backported to a 5.7 bugfix release is the removal of the selection of GLX or EGL in the compositor settings. And as a result we were already able to improve various parts of our rendering stack which will benefit all users – independently of whether llvmpipe is used or not. Last but not least using llvmpipe also exposes performance problems which we normally don’t see with a fast GPU. This might also be a handy new features for users who don’t want any animations at all, but still want the compositor enabled. For this we introduced a way to disable all animations in KWin and a lot of effects are already adjusted. So we are now working on disabling the effects if we are on software emulation. We don’t want blur effect on software emulation and neither wobbly windows. The solution to this problem is to deactivate what we know to be expensive – all these effects which are not available on XRender because we know it to be too expensive. So nothing gained by forcing to XRender.īut still it’s possible that using llvmpipe compositing will result in high CPU usage if KWin has to use it. For XRender it’s possible that the xorg modesetting driver is used in combination with glamor. Last but not least there is the question whether XRender or QPainter compositing is a better solution than llvmpipe. Similar the embedded systems also provide working drivers nowadays, if we think of raspberry pi or odroid – they all can do OpenGL and we don’t have the risk of them going on llvmpipe which would result in a very bad experience. For example we didn’t want virtual machines to render through llvmpipe, but today also KVM can do accelerated OpenGL through virgl driver. Related to that many of the reasons to not use llvmpipe by default are going away. If the system is usable enough for Plasma, it will also be sufficient for KWin’s compositing. Thus most of the system is going through that driver. Due to QtQuick KWin will render parts of its user interface through llvmpipe anyway and also Plasma will render completely through llvmpipe. In this release we re-evaluated the situation and came to the conclusion that it doesn’t make sense to continue blocking llvmpipe driver. We thought that with XRender based compositing one gets better results than with software emulation. So far KWin fall back to XRender based compositing when the OpenGL driver uses software emulation. With Plasma 5.8 we finally allow OpenGL compositing through the llvmpipe driver. Which means the debug console can now be freely resized and moved around. This is intended to be useful when for whatever reason glxinfo is not working and one needs to know exactly which extensions are available.Īs you can see in the screenshot: KWin also learned to add decorations around “internal” windows on Wayland. It shows the information gathered from the OpenGL library (version, renderer, etc.) and all the available extensions. This shows information comparable to what we know from glxinfo/es2_info. The new KWin debug console gained a new tab for OpenGL information. Manual installation of updated lighthouse firmware.Įnabling Direct Mode - Fails, I assume until I can use a pre breakoutbox at least according to the wiki.In Plasma 5.8 we will see a few changes in the OpenGL compositor which are worth a blog post. ![]() But the dashboard continues to notify that the lighthouses still have a firmware update pending.įull uninstall - Reinstall (pulling USB drivers, uninstalling steam vr, etc)ĭifferent Steam VR versions (beta, regular release) Selecting the "Make compositor fullscreen" has no effect, moving my mouse to the other screen and left clicking has no effect.Īdditionally it indicates that the lighthouses have a firmware update, and running the firmware update tool indicates success. No windows appear to be present to eclipse the compositor. The compositor is showing full red, this displays in the mirror window, and it is being displayed by the HMD. I'm getting green lights across the board, but an error message that the compositor is not fullscreen. I'm running into an error with the (non-pre) original dev kit.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |