robertosfield wrote:
> Hi Fred,
> 
> You interpretation of what Geometry::setUseVertexBufferObjects(true)
> is correct, so what you are see looks to be a bug.  Which version of
> the OSG are your using?
> 
> A couple of weeks ago I was looking into VBO setup issues relating to
> the new serializers and tracked down the issues I was seeing to
> src/osg/Geometry.cpp, so I then tidied up the loopholes in the set up
> of the VBO's.  The problems I saw was that is some usage models the
> VBO's were all setup correctly, but others it wasn't, so I closed
> these loopholes, these fixes are now checked into svn/trunk.
> 
> There might still be some combinations of usage that I didn't spot, if
> svn/trunk has them then just point me in the right direction.
> 
> Robert.
> 


I am working right off the trunk as I will most likely need to test 
recent/experimental features in the future.

I was using a version from early October, IIRC. I have just updated and things 
work as expected now.

One minor remark though.

In my GL tracer, I can see the following warning:

wglGetCurrentDC()
wglGetExtensionsStringsARB(<hex value>)
glGetString(...)
glGetString(...)
[...]
glGetString(...)
glGetQueryiv(GL_CURRENT_TIME_NV, GL_QUERY_COUNTER_BITS, <hex value>)
OpenGL error GL_INVALID_ENUM detected

I'm using a Radeon HD5000 graphics card, the call above is unsupported.

Thanks,
Fred

------------------
Read this topic online here:
http://forum.openscenegraph.org/viewtopic.php?p=33996#33996





_______________________________________________
osg-users mailing list
[email protected]
http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org

Reply via email to