[ODE] .NET wrapper - Materials

[David Walker]

I'd missed the discussion on materials but I've just had a quick look at the
archives and it sounds like a good idea but there are few things I'm not
sure about. If I read it correctly, you would assign a material to each geom
and then when the collision is detected use the properties of the materials
to assign the correct values to the surface properties. This could
potentially lead to a lot of surface combinations. Not really a problem I
suppose, since you already have the same number of combinations at the
moment and at least the materials would give some way to structure it. hmm.
sorry don't really know where I was going with that just kinda thinking out
loud.

The other thing that occurred to me is that I think the collision callback
is useful for a few other things. a) ignoring collisions and b) performing
other operations when a collision occurs (increasing score for example) and
c) just general flexibility, so I think that any materials mechanism should
be optional and implemented alongside the callback.

David.

----- Original Message -----
From: "Nate W" <coding@natew.com>
To: <ode@q12.org>
Sent: Monday, January 27, 2003 11:02 PM
Subject: Re: [ODE] .NET wrapper


> On Sun, 26 Jan 2003, Jeff Weber wrote:
>
> > Yes, David's wrapper has the call-backs all hooked up. I hadn't gotten
to
> > that in my wrapper, but i'm sure it'll be easier now that i have a
> > reference.
>
> I feel partial to the 'material' concept that Anselm brought up on this
> list a while back.  Is anyone still working in that direction?  It should
> do away with whatever overhead is involved in the transition from
> unmanaged code to managed and back again, which sounds valuable for
> something that's going to happen many times per world-step.
>
> --
>
> Nate Waddoups
> Redmond WA USA
> http://www.natew.com
>
>
> _______________________________________________
> ODE mailing list
> ODE@q12.org
> http://q12.org/mailman/listinfo/ode