I'll work up a base example and see if it occurs there or just within my
own code...
On Thu, 2008-03-20 at 14:36 +0000, Robert Osfield wrote:
> Hi Jeremy,
>
> This "might" be an osgUtil bug, we'd need to recreate it on one of the
> core examples and go from there.
>
> Robert.
>
> On Thu, Mar 20, 2008 at 2:27 PM, Jeremy Moles <[EMAIL PROTECTED]> wrote:
> > While working through some strange picking problems in osgWidget (and,
> > by the way, SVN osgWidget is _TOTALLY_ busted, so please don't even
> > bother with it :)), I noticed that at some XY coordinates
> > osgViewer::computeIntersections is returning an Intersection object for
> > the same Drawable twice. I'm not quite sure what causes this, but I used
> > the followed code (psuedo) to verify it:
> >
> >
> >
> > for(x = 0; x < screenWidth; x++) {
> > for(y = 0; y < screenHeight; y++) {
> > v.computeIntr(x, y, i, MY_MASK)
> > }
> > }
> >
> >
> >
> > ...with only a single Drawable (Widget) on the screen at the time, which
> > simulates a person moving their cursor over every pixel. There's no
> > pattern that I can see to the times this occurs, and it isn't something
> > I've been able to fix by changing the threading model or
> > enabling/disabling vsync.
> >
> > I can certainly add code to guarantee that my own internal PickResults
> > object doesn't add the same Drawable more than once, but I wanted to
> > throw this question out there before going down that path. Is it
> > perfectly acceptable for computeIntersections to return the same
> > Drawable twice?
> >
> > _______________________________________________
> > osg-users mailing list
> > [email protected]
> > http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org
> >
>
_______________________________________________
osg-users mailing list
[email protected]
http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org
