Hi Sebastian, On 16 January 2014 08:12, Sebastian Messerschmidt < [email protected]> wrote:
> Hi Ethan, > > Thanks for bearing with me Robert, I do realize that there has been much >> discussion over this topic (I have spent hours trying to understand it all >> but OSG is the only exposure to OpenGL that I've ever had so trying to >> understand it all is tricky for me). >> >> You mention using the osg_deprecated to tide me over, but I'm wondering >> what is the more appropriate long-term solution. To be clear, I don't need >> to support any existing geometry that contains BIND_PER_PRIMITIVE (i.e. I >> don't need to use fixDeprecatedData(). What I do need to do is to be able >> to create new osgGeometry objects with osg3.2 and future versions of osg >> that allow me to have the end-effect of coloring each primitive >> individually. Now, if I am understanding correctly, what I will have to do >> when creating new geometry is to only put a single primitive in each >> primitiveset and use BIND_PER_PRIMITIVE_SET. My understanding is that >> BIND_PER_PRIMITIVE_SET is supported in OpenGL and that this will not be >> deprecated any time soon. Do I have this more or less correct? >> > Bind per primitive is supported, and I guess that it won't be deprecated > any time soon. > It would seem that you have got your information mixed up. BIND_PER_PRIMITIVE had been deprecated for many years, modern OpenGL does not support it in any form so you have to emulate it. In OSG-3.2 official support for BIND_PER_PRIMITIVE was removed and a fallback provided to convert old data across to not use BIND_PER_PRIMITIVE. In OSG-3.2 a deprecated_osg::Geometry class provides the old API support for those that a need a quick workround for code that uses old deprecated features. Robert.
_______________________________________________ osg-users mailing list [email protected] http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org
