<html> <head> <base href="https://bugs.freedesktop.org/" /> </head> <body> <div> <a class="bz_bug_link bz_status_REOPENED " title="REOPENED - Unigine Heaven 4.0 silhuette run" href="https://bugs.freedesktop.org/show_bug.cgi?id=92233#c10">Comment # 10</a> on <a class="bz_bug_link bz_status_REOPENED " title="REOPENED - Unigine Heaven 4.0 silhuette run" href="https://bugs.freedesktop.org/show_bug.cgi?id=92233">bug 92233</a> from <a class="email" href="mailto:kenneth@whitecape.org" title="Kenneth Graunke <kenneth@whitecape.org>"> Kenneth Graunke</a> <pre>(In reply to Ilia Mirkin from <a href="show_bug.cgi?id=92233#c9">comment #9</a>) > It causes a major performance regression on e.g. nouveau. I assume this is > because they do n+1 passes where they would have done n. Thanks, that is constructive feedback. I actually started blacklisting GL_ARB_blend_func_extended for Unigine demos in 2012, because of this very bug. Marek removed this in June 2015 when he dropped support for (the much more broken) Heaven 3.0, re-enabling it. During that three year period, no one had ever mentioned to me that disabling it dropped performance, or expressed any opinion that disabling it was a problem. My patch was simply returning us to the longstanding status quo. I even checked with the AMD developers before proceeding with the patch. Regressing Nouveau is obviously not acceptable. To that end, I've come up with a new drirc workaround that will make Unigine's broken dual color blending work on i965 so we can re-enable it. I hope to send the patches out later tonight, once I've tested them for regressions.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the QA Contact for the bug.</li> </ul> </body> </html>