<html> <head> <base href="https://bugs.freedesktop.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - DiRT Rally elements blinking constantly" href="https://bugs.freedesktop.org/show_bug.cgi?id=109212#c6">Comment # 6</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - DiRT Rally elements blinking constantly" href="https://bugs.freedesktop.org/show_bug.cgi?id=109212">bug 109212</a> from <a class="email" href="mailto:leozinho29_eu@hotmail.com" title="leozinho29_eu@hotmail.com">leozinho29_eu@hotmail.com</a> <pre>Created <a href="attachment.cgi?id=143005" name="attach_143005" title="Videos showing the difference between the good and the bad">attachment 143005</a> <a href="attachment.cgi?id=143005&action=edit" title="Videos showing the difference between the good and the bad">[details]</a> Videos showing the difference between the good and the bad I found a consistent case to bisect in DiRT Rally: at the stage Ourea Spevsi in Greece, there is one part of the replay where the effect is very visible. That part of the stage has many tress and bushes that blink constantly with the bad commit while with the good commit it's nearly perfect (notice the nearly). Even using Mesa 13.0.3 (what Feral recommends) it is similar to what the good video is. Now, with a consistent case, the only downside from the bisect seems to be the fact all builds being tested seem to be from before the memory reduction commit. Hopefully I'll be able to get the bisect result in a few hours. Another downside may be that there is no longer any Mini Cooper or Renault Alpine intact.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the QA Contact for the bug.</li> <li>You are the assignee for the bug.</li> </ul> </body> </html>