<div>GEM doesn't support geometry shaders at this point. It could turn out that they won't work well with the Pd/GEM environment, but there are other aspects of GL that don't work either. GL was clearly not designed to do what GEM does, so there is a lot of work to be done for each new feature added to GL. There is a lot of compromise needed to fit the latest and greatest into a framework over a decade old.
</div>
<div> </div>
<div> </div>
<div><span class="gmail_quote">On 8/16/07, <b class="gmail_sendername">Wesley Smith</b> <<a href="mailto:wesley.hoke@gmail.com">wesley.hoke@gmail.com</a>> wrote:</span>
<blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">I'm not sure if GEM has support for geometry shaders yet, but how do<br>you imagine handling the program parameters like
<br>GL_GEOMETRY_VERTICES_OUT_EXT, GL_GEOMETRY_INPUT_TYPE_EXT, and<br>GL_GEOMETRY_OUTPUT_TYPE_EXT without some kind of extra information<br>since these things aren't inherent to the shader code yet most<br>geometry shaders are written for particular input and output types?
<br><br>wes<br></blockquote></div><br>