This is an optimization if your geometry doesn't change. A display list loads all of the vertex, color, texcoord and normal data onto the card and then just tells the card to render it right from VRAM. The model object uses display lists for speed. If you need 10,000 cubes it would be faster to make a model of the cube and load it that way.
<br><br>Cyrille's trick is to set up a render chain and render that once into the display list. After that only the gemhead feeding GEMglCallList is rendered every frame. <br><br>On 2/28/07, <b class="gmail_sendername">
Frank Barknecht</b> <<a href="mailto:fbar@footils.org">fbar@footils.org</a>> 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;">
Hallo,<br>cyrille henry hat gesagt: // cyrille henry wrote:<br><br>> don't forget you can optimized your patch with GEMglGenList / GEMglNewList etc in order to create a display list so that you patch could resume in :
<br>><br>> repeat 1000<br>> [<br>> GEMglCallList<br><br>I've never hear of this optimization, do you have an example for it?<br><br>Ciao<br>--<br> Frank Barknecht _ ______footils.org_ __goto10.org__
<br><br>_______________________________________________<br><a href="mailto:PD-list@iem.at">PD-list@iem.at</a> mailing list<br>UNSUBSCRIBE and account-management -> <a href="http://lists.puredata.info/listinfo/pd-list">
http://lists.puredata.info/listinfo/pd-list</a><br></blockquote></div><br>