[ODE] visibility detemination?

[Erwin de Vries]

Now that i've given it a little more thought, making use of the aabb_test
function is really appropriate here. Perhaps this eliminates the need for
real plane-primitive collision, although i would keep it as an option.

Erwin

----- Original Message -----
From: "Erwin de Vries" <erwin@vo.com>
To: <ode@q12.org>
Sent: Monday, May 05, 2003 10:26
Subject: Re: [ODE] visibility detemination?


> Hi,
>
> Here is a little example on how i did it. It does not compile for you
> because it is based on my own collision system, but it is very similar to
> the ODE version, so i think you'll be able to understand it.  I never used
> this and i'm not sure it even works, but it might just same you some work.
>
> Regards,
> Erwin
>
> ----- Original Message -----
> From: "Clint Brewer" <clint@haptek.com>
> Cc: <ode@q12.org>
> Sent: Monday, May 05, 2003 08:24
> Subject: Re: [ODE] visibility detemination?
>
>
> > Hi All,
> > well after a good bit of time away, I'm finally getting a chance to work
> > on this again.
> > I just spent a good day or so planning it out and reading over the docs,
> > I think it's going to be easily do-able as we discussed before, just
> > having a special callback function for visibility determination that
> > gets called when you collide a frustum with a dSpace
> >
> > I'll create a reusable frustum geometry type so that others can use it
> > for the same purpose if they want.
> >
> >
> > gl :  not sure if you are still arround or not, I'll try out your
> > terrain collision geometry soon too.  Have you worked on it anymore?
> >
> >
> > best,
> > clint
> >
> >
> >
> >
> > skjold@cistron.nl wrote:
> >
> > >>I could be off my rocker here, but doesn't ODE do CD at two levels of
> > >>precision?  Like, dSpaceCollide looks for potential collisions, and
then
> > >>the callback function uses dCollide to get penetration
> > >>points/normals/depths, etc?
> > >>
> > >>Would the "coarse" CD of dSpaceCollide might make a good FOV test, if
a
> > >>frustum geometry class were added?
> > >>
> > >>
> > >
> > >Yes, that was the general idea being discussed: To take advantage of
the
> callback used by dSpaceCollide in determining potential visibility, but
not
> to actually call dCollide for it.
> > >_______________________________________________
> > >ODE mailing list
> > >ODE@q12.org
> > >http://q12.org/mailman/listinfo/ode
> > >
> > >
> > >
> >
> > _______________________________________________
> > ODE mailing list
> > ODE@q12.org
> > http://q12.org/mailman/listinfo/ode
> >
> >
>