[ODE] new ODE collision

[Russ Smith]

> - Remember to add dGeomMoved() calls inside of all Set functions of a
> geom. Also SetRadius, etc.

yup, i'm on it.

> - I think the destructor of a geom needs to tell the body it might be
> attached to that it wants to remove itself. Otherwise the body will
> use this geom in its linked list after it has been destroyed, which
> crashes.

quite right - i'll do this too.

> - When adding the ray class we should think about what the
> 'penetration depth' should be. Do you have any thoughts on this?

i'm not sure that dRay will ever be attached to a body, in which case
penetration depth does not have much use for the dynamics. perhaps you
can think of a non-dynamics use/definition for the penetration depth?

> - Why do you memcopy inside the dxSpace::computeAABB() function?

no good reason. it may actually be marginally faster because the
g->recomputeAABB() call will cause a reload of the class aabb pointer,
but not the stack aabb buffer. it's an optimization, but i doubt anyone
would notice the extra cycles.

> - Should we add support for a user defined, or infinite AABB on demand
> for spaces? This is really useful for the quadtree space containing
> huge (10.000 for example) amounts of geoms. If i would remove a single
> geom it would need to do a lot of work.

i don't understand this .. ?

russ.

-- 
Russell Smith
http://www.q12.org