Re: [osg-users] Crash in osg 3.4.0 on Virtual Machine when OSG_GL3_AVAILABLE enabled

2016-03-09 Thread Christian Buchner
Hi Robert, thanks for the quick response, > > My point is that enabling GL3 and then using a driver that doesn't support > gl buffers causes a null pointer access, to me this is a bug. If it is > valid to use buffer objects when gl3 is enabled then bufferobject needs to > do something other than

Re: [osg-users] Crash in osg 3.4.0 on Virtual Machine when OSG_GL3_AVAILABLE enabled

2016-03-09 Thread Barney Wrightson
Hi Robert, thanks for the quick response, My point is that enabling GL3 and then using a driver that doesn't support gl buffers causes a null pointer access, to me this is a bug. If it is valid to use buffer objects when gl3 is enabled then bufferobject needs to do something other than what is

Re: [osg-users] Crash in osg 3.4.0 on Virtual Machine when OSG_GL3_AVAILABLE enabled

2016-03-09 Thread Robert Osfield
HI Barney, The extension check is correct as buffer objects are part of the spec for GL3, the driver doesn't need to define the ARB extension in this case. For your own work I would recommend not selecting GL3, just build the OSG with defaults and let it check the functionality at runtime. If