[ODE] Sliding over a trimesh

[Simon Barratt]

Colin Bonstead already posted some code which implements a system
similar to the one discussed in GPG4 as well as modifications to one of
the colliders to support the 'inactive edge' data.

http://q12.org/pipermail/ode/2004-June/013183.html  was the email with
the cvs patch http://open.cyanworlds.com/ode_tri_pre.patch 

Hope that helps.

--
Simon Barratt, Lead Developer, Pineapple Interactive Ltd
e: barog at pineapple-interactive.com
w: www.pineapple-interactive.com
t: +44 (0)1274 480185

-----Original Message-----
From: ode-bounces at q12.org [mailto:ode-bounces at q12.org] On Behalf Of Adam
D. Moss
Sent: 16 September 2004 09:36
To: ode
Subject: Re: [ODE] Sliding over a trimesh

Will Thimbleby wrote:
> Confused ramblings.....
> Also. I was thinking about the trimesh collision code, and I was 
> wondering if it might be a good idea to be able to give trimeshes a 
> handedness (cw/ccw).  This way the penetration depth is always known.

This is already the case... winding-order is very important.

> Perhaps, would it be possible / 'a good idea' to be able to turn edge 
> collisions off for specific(convex and duplicated) edges. If these 
> both were done would it be equivalent to a convex hull

I think that'd be very nice.  At the moment, though, IIRC ODE (OPCODE)
trimeshes are pretty much a triangle-soup with no connectivity
information for making this automatic -- but I don't see a technical
reason why each triangle couldn't have three flags for explicitly
turning off per-edge collisions (or, that is to say, the direction of
push would always be the triangle's normal in the event of a 'disabled'
edge collision).

--Adam
_______________________________________________
ODE mailing list
ODE at q12.org
http://q12.org/mailman/listinfo/ode