| Summary: | [feature-request] Please make KWin 3D desktop effects work on VirtualBox | ||
|---|---|---|---|
| Product: | [Plasma] kwin | Reporter: | Technologov <al4321> |
| Component: | general | Assignee: | KWin default assignee <kwin-bugs-null> |
| Status: | RESOLVED UPSTREAM | ||
| Severity: | wishlist | Flags: | mgraesslin:
ReviewRequest+
|
| Priority: | NOR | ||
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Platform: | openSUSE | ||
| OS: | Linux | ||
| URL: | https://git.reviewboard.kde.org/r/106821/ | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
| Attachments: |
Output of "kwin --replace" command, from openSUSE 11.4 guest.
Output of "glxinfo" command, from openSUSE 11.4 guest. |
||
|
Description
Technologov
2011-03-28 09:17:42 UTC
KWin does not "require" neither direct rendering in general nor the DRI extension (which is staill rather a matter of X11 than linux) in particular at all - it's just a good idea because it's (usually) faster (if it works... *sigh*) I don't know about the limitations of VB, but the software renderer (alongside the fallback texture generation?) used to work fine? + If VB doesn't provide accelerated GL, you could just as well use the XRender backend... + On top of that, upcoming KWin 4.7 has support for the ES profile and (imho) it would be a /very/ good idea of the VB team to support at least that. Please run kwin from konsole as "kwin --replace&" and check/post the output to see why compositing support is denied or attach a crashtrace. -Thomas, same day :-P Created attachment 58393 [details]
Output of "kwin --replace" command, from openSUSE 11.4 guest.
Created attachment 58394 [details]
Output of "glxinfo" command, from openSUSE 11.4 guest.
Kwin says it renders to "Mesa Software Rasterizer", but glxinfo claims "OpenGL 2.1 Chromium 1.9"... go figure... Chromium is the OpenGL layer of VirtualBox. ---- I know that 3D acceleration is enabled now, because Euphoria 3D screensaver renders quickly now. If I disable 3D acceleration in VirtualBox, it renders slowly. -Technologov Last time I tried KWin in VirtualBox it reported software rasterizer in indirect rendering and chromium in direct rendering. As KWin defaults to indirect rendering for unknown drivers the difference in log output is to be expected and correct. When enforcing direct rendering the screen becomes black - texture from pixmap is clearly failing. Why it works in Compiz: no idea. I assume that they implemented just enough in their driver so that Compiz works. In Virtualbox KWin automatically falls back to XRender and given that this has to be fixed by Oracle and the advantage of having Opengl compositing in virtualbox, I don't think we should do anything about it. Is it possible to use "Chromium" in indirect rendering ? Or inderect always means Software Rasterizer ? > Is it possible to use "Chromium" in indirect rendering ? Or inderect always
> means Software Rasterizer ?
Indirect means for Chromium Software Rasterizer which makes it useless
Let's hope that Oracle adds it. We cannot add the missing pieces to the drivers. It seems to work nowadays, see: https://git.reviewboard.kde.org/r/106821/ |