On 3/22/2013 4:56 AM, Robert Osfield wrote:
Hi Judson,
On 21 March 2013 20:26, Judson Weissert <[email protected]> wrote:
There is an interesting distinction between needing to dirty a display list
(e.g., Drawable::dirtyDisplayList()) versus having to dirty a primitive when
using VBO (e.g., Array::dirty()). When a VBO request falls back to a display
list implementation, it is possible that a call to dirtyDisplayList() in
client code could be missing (because the primitive array was dirtied
instead of the display list for instance). Not that this is a major issue,
but it is something to think about when fallback is a possibility.
There is only so much we can do as a fallback, both from a
practicality and efficiency standpoint. As a general practice I'd
recommend calling dirtyDisplayList() when you have modified the
geometry, or disabling use of display lists.
Robert.
I concur.
Also, I learned why the viewer was opening in full screen when running
in VirtualBox with 3D Acceleration enabled. I foolishly did not check
the return value of osg::GraphicsContext::createGraphicsContext() to
ensure it was valid before assigning it to my camera. Therefore, when
osg::Viewer::realize() was called later, it detected it was not fully
initialized, so it went on to create its own fullscreen window.
Apparently, a pixel format could not be created that matched my traits.
Specifically, when I specified 4 samples (associated with
WGL_SAMPLES_ARB), choosing a pixel format failed, but it succeeds with a
value of zero (which also explains how the fullscreen window was able to
function).
Thanks again,
Judson
_______________________________________________
osg-users mailing list
[email protected]
http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org
