<html>
<head>
<base href="https://bugs.freedesktop.org/">
</head>
<body><span class="vcard"><a class="email" href="mailto:t_arceri@yahoo.com.au" title="Timothy Arceri <t_arceri@yahoo.com.au>"> <span class="fn">Timothy Arceri</span></a>
</span> changed
<a class="bz_bug_link
bz_status_NEW "
title="NEW - Special block from Minecraft mod rendered out of place"
href="https://bugs.freedesktop.org/show_bug.cgi?id=100960">bug 100960</a>
<br>
<table border="1" cellspacing="0" cellpadding="8">
<tr>
<th>What</th>
<th>Removed</th>
<th>Added</th>
</tr>
<tr>
<td style="text-align:right;">Status</td>
<td>NEEDINFO
</td>
<td>NEW
</td>
</tr></table>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW - Special block from Minecraft mod rendered out of place"
href="https://bugs.freedesktop.org/show_bug.cgi?id=100960#c5">Comment # 5</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW - Special block from Minecraft mod rendered out of place"
href="https://bugs.freedesktop.org/show_bug.cgi?id=100960">bug 100960</a>
from <span class="vcard"><a class="email" href="mailto:t_arceri@yahoo.com.au" title="Timothy Arceri <t_arceri@yahoo.com.au>"> <span class="fn">Timothy Arceri</span></a>
</span></b>
<pre>I can confirm this renders correctly on Nvidia's Linux driver.
The rendering of the block can be seen in Frame 815 via three calls to
glCallList().
glCallList(55503), glCallList(55504) and glCallList(55505)
These call lists are compiled in Frame 814.
Editing the y param to the glTranslatef() call that exists before glCallList()
is called allows us to move the block to a more correct location.
There are a bunch of gl{Push,Pop}Matrix() calls before this but as far as I can
tell Mesa's implementation of these functions looks fine.
I couldn't find any reason for the block to be rendered in the wrong position
on Mesa drivers but thought I'd record this information in case anyone else
wants to take a look.</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the assignee for the bug.</li>
<li>You are the QA Contact for the bug.</li>
</ul>
</body>
</html>