<html>
<head>
<base href="https://bugs.freedesktop.org/" />
</head>
<body>
<p>
<div>
<b><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#c10">Comment # 10</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 <span class="vcard"><a class="email" href="mailto:mattst88@gmail.com" title="Matt Turner <mattst88@gmail.com>"> <span class="fn">Matt Turner</span></a>
</span></b>
<pre>(In reply to Ian Romanick from <a href="show_bug.cgi?id=91617#c5">comment #5</a>)
<span class="quote">> (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.</span >
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.</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the QA Contact for the bug.</li>
</ul>
</body>
</html>