<html> <head> <base href="https://bugs.freedesktop.org/" /> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - [BDW] Incorrect rendering in CS:GO" href="https://bugs.freedesktop.org/show_bug.cgi?id=91617#c11">Comment # 11</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - [BDW] Incorrect rendering in CS:GO" href="https://bugs.freedesktop.org/show_bug.cgi?id=91617">bug 91617</a> from <a class="email" href="mailto:matthieu.bouron@gmail.com" title="Matthieu Bouron <matthieu.bouron@gmail.com>"> Matthieu Bouron</a> <pre>(In reply to Matt Turner from <a href="show_bug.cgi?id=91617#c10">comment #10</a>) > (In reply to Ian Romanick from <a href="show_bug.cgi?id=91617#c5">comment #5</a>) > > (In reply to Matthieu Bouron from <a href="show_bug.cgi?id=91617#c4">comment #4</a>) > > > > Matthieu: Can you try running with the environment variable > > > > "INTEL_DEBUG=vec4vs". I'm not 100% sure how to do that in Steam, but Dylan > > > > or Google may be able to help. This will remove one difference between the > > > > IVB and BDW systems. > > > > > > Exporting the variable (with export) before launching steam seems to do the > > > trick, however the issue is still there. Would the vec4vs output be useful > > > to you ? > > > > Thanks for trying. If that doesn't workaround the problem, output from that > > configuration won't help. I knew it was a bit of a long shot. > > I think Matthieu's reply has confused the issue. I think he meant that > INTEL_DEBUG=vec4vs indeed works around the issue, but that the underlying > issue still exists, not that using INTEL_DEBUG=vec4vs did not do anything > differently. Sorry, my initial reply was not very clear. INTEL_DEBUG=vec4vs did *not* work around the issue.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the QA Contact for the bug.</li> </ul> </body> </html>