On 12/4/06, <b class="gmail_sendername">Hans-Christoph Steiner</b> &lt;<a href="mailto:hans@eds.org">hans@eds.org</a>&gt; wrote:<div><span class="gmail_quote"></span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div style=""><div><span class="e" id="q_10f4f9d7b0d492de_1"><br><div><br></div></span></div><div>Yup, Gem loads and so does [gemwin].&nbsp; An ATI from 1998 supports some NVidia extensions that a current ATI does not support, crazy...
</div></div></blockquote><div><br>I don't think that is the case.&nbsp; That ATI part does not support the OpenGL functionality in question at all whether through the NV or ARB extension.&nbsp; No properly functioning ATI driver would have that extension in it.
<br></div><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><div style=""><div>I am thinking for the Pd-0.39.2-extended release, Gem should be compiled with --disable-NV, but it can stay as is on the nightly builds if that's useful to y'all.
</div></div></blockquote><div><br>I wouldn't do anything until it is clear that the autobuild machine is building a binary with calls to the Nvidia extension.&nbsp; I do not think it is.<br></div><br></div><br>