Hi Jeremy, There isn't anything special that osg::Geometry does with VBO, in fact the handling of primitive data could certainly do with some improvement w.r.t sharing a single VBO between separate primitives.
The code in Drawable is all just extension support, there isn't any actual implementation, and its beyond the scope of the Drawable base class. What it will give you is runtime check for VBO support and ability to handle multiple graphics contexts. Robert. On 2/5/07, Jeremy L. Moles <[EMAIL PROTECTED]> wrote:
I have a situation where I'd like to use VBO's in my custom drawable's drawImplemention method. I have experience using VBO's in a "normal" sense by making calls to OpenGL directly, but I'm _certain_ OSG provides a more sensible, safe way to do this. I've investigated the BufferObject header some, but this doesn't appear to be the place to do it (unless we're supposed to use BufferObject::Extensions directly). The Drawable parent class itself appears to have some internal support for enabling VBO's, but no apparent way to initially populate or bind the VBO's data using BindBuffer/BufferData. Is there something very obvious that I'm missing? Or should I go ahead and implement my Drawable such that it maintains these buffers itself? Better yet, is there some documentation on this issue, or perhaps is this something that might go into Martz's book? :) _______________________________________________ osg-users mailing list [email protected] http://openscenegraph.net/mailman/listinfo/osg-users http://www.openscenegraph.org/
_______________________________________________ osg-users mailing list [email protected] http://openscenegraph.net/mailman/listinfo/osg-users http://www.openscenegraph.org/
