<html> <head> <base href="https://bugs.freedesktop.org/" /> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW --- - Pretty huge slowdown in mesa 9.0" href="https://bugs.freedesktop.org/show_bug.cgi?id=55998#c22">Comment # 22</a> on <a class="bz_bug_link bz_status_NEW " title="NEW --- - Pretty huge slowdown in mesa 9.0" href="https://bugs.freedesktop.org/show_bug.cgi?id=55998">bug 55998</a> from <a class="email" href="mailto:fredrik@kde.org" title="Fredrik Höglund <fredrik@kde.org>"> Fredrik Höglund</a> <pre>(In reply to <a href="show_bug.cgi?id=55998#c19">comment #19</a>) > e943e5c291c5f4c017f9f5a483f1940313333fc3 is the first bad commit > commit e943e5c291c5f4c017f9f5a483f1940313333fc3 > Author: Chad Versace <<a href="mailto:chad.versace@linux.intel.com">chad.versace@linux.intel.com</a>> > Date: Thu Aug 2 17:13:17 2012 -0700 > > intel: Advertise multisample DRI2 configs on gen >= 6 > > This turns on window system MSAA. > > So in other words, it looks like KDE is using multisampling now, whereas it > didn't before. Our implementation of that may not be optimal, and may have > bugs, but it will always be far slower than single sampling. > > My next question would be: how can one disable the use of MSAA in KWin or > Plasma? I don't see an option for that, but I would be really surprised if > there wasn't one... The algorithm that chooses the FBConfig doesn't check the values of GLX_SAMPLES and GLX_SAMPLE_BUFFERS, so I guess it ends up picking an MSAA config purely by accident. That's something we'll have to fix in KWin. But unfortunately that also means that there is no way to enable or disable the use of MSAA right now.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>