<html>
<head>
<base href="https://bugs.freedesktop.org/" />
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW --- - r300g does not eliminate unread varyings"
href="https://bugs.freedesktop.org/show_bug.cgi?id=65416#c1">Comment # 1</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW --- - r300g does not eliminate unread varyings"
href="https://bugs.freedesktop.org/show_bug.cgi?id=65416">bug 65416</a>
from <span class="vcard"><a class="email" href="mailto:stefandoesinger@gmx.at" title="Stefan Dösinger <stefandoesinger@gmx.at>"> <span class="fn">Stefan Dösinger</span></a>
</span></b>
<pre>Fwiw, I don't know if r600g is affected. The HW has enough varyings to run the
unoptimized shaders, and the applications affected by this performance wise are
CPU limited on my r600g system.
Wine has some checks to prevent writing texture coordinates in the vertex
shader when there is no input to generate them. Unfortunately 3DMark 2000 and
Unreal Tournament 2004 use a strange vertex processing setup that breaks those
checks(D3DTSS_TEXCOORDINDEX of all texture stages is 0, thus they're reading
the first texture coordinate input, which does exist).</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the assignee for the bug.</li>
</ul>
</body>
</html>