Hi Robert, That would cover our primary use cases. We've already done the same in all of our application code.
Catching the failure instead of crashing is very much preferred, even if it leads to a bad display. I'm on board with this solution and can help test my end. - Dan > -----Original Message----- > From: osg-users [mailto:osg-users-boun...@lists.openscenegraph.org] On > Behalf Of Robert Osfield > Sent: Wednesday, June 13, 2018 3:28 PM > To: OpenSceneGraph Users > Subject: Re: [osg-users] VBO Bug with 3.6.1 and Normal Arrays > > I am moving towards the idea that we may only be able to catch on the > fly bad usage and disable the arrays that don't have a VBO assigned > when trying to render with VAO, and emit a warning. this will be > better than having an application crash. > > I'm going to re-factor the existing places in the OSG where the later > Array::setBinding() is being used so that doesn't cause problems, this > will at least make the above problem case less likely. This won't fix > application code that needs to be amended though. > > Robert. > _______________________________________________ > osg-users mailing list > osg-users@lists.openscenegraph.org > http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org _______________________________________________ osg-users mailing list osg-users@lists.openscenegraph.org http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org
