[ODE] Colliider space/geom issues

[John Miles]

That's fine, too; the instructions Benoit gave for integrating them with ODE
0.039 are still valid for the current version.

I believe the objection to full ODE citizenship in the past has been their
lack of support for collisions with trimeshes.  I don't think that's a very
pressing concern, because the usual applications for trimeshes seem to be
terrain and static geometry that doesn't need to collide with height maps
anyway.

I have not tested the dCone primitive, but the heightmap terrain geoms have
worked great for a long time.

(I just updated the files in the zipfile with a few cosmetic cleanup tweaks;
you might want to re-download it before you do the update.)

-- jm

> -----Original Message-----
> From: Bram Stolk [mailto:bram at sara.nl]
> Sent: Saturday, February 25, 2006 4:41 AM
> To: John Miles
> Cc: Ode at Q12.Org
> Subject: Re: [ODE] Colliider space/geom issues
>
>
> John Miles wrote:
> > Cool -- I noticed it when diffing against an older version, and
> wasn't sure
> > what was up.
> >
> > Here are versions of the dTerrainY, dTerrainZ, and dCone source
> files that
> > work with the new geom-offset functionality.  They appear to
> work fine with
> > the test_boxstackb program:
> >
> > http://www.speakeasy.net/~jmiles1/terrcone.zip
> >
> > Can someone with CVS access please move these into the
> > contrib/TerrainAndCone directory of the unstable branch, so
> they'll continue
> > to be usable with the rest of the library?  Thanks!
>
> Well, as you have tested these, maybe they should go in the
> source tree, instead of in contrib.
> I'll try to do this this weekend.
> Probably with a --with-cone configure flag or something.
>
>    bram
>
>