[ODE] AutoDisable

[Cameron Bonde]

Hmm, I don't know anything really, but at the point which things rest
they have to be touching something, or at least if the last thing it
touched was within it's 'shimmy' threshhold, can't (for example) the top
object tell everything its touching to add it to a their 'reenable'
list. Then when the thing under it moves it goes through its list and
tells them to reenable themselves. Basically so it doesn't matter if
there is an actual collision happening or not, because that's been
decided before hand. So in a wall of boxes if the floor was moved down
the reenabling would cascade up the wall. I'm no doubt back in 1st grade
stuff here, but I thought I'd ask/share anyway :)

> -----Original Message-----
> From: gl [mailto:gl at ntlworld.com] 
> Sent: Monday, 1 March 2004 10:27 AM
> To: ode at q12.org
> Subject: Re: [ODE] AutoDisable
> 
> 
> 
> > It seems that all we need is the decision on angular movement 
> > threshold. Would it be ok if it just was a fixed (per-body) value?
> 
> Sure, but it would be good if you could pass the global 
> values into a call somewhere, rather than having to modify 
> the source to change them.  I have my own auto-disabling 
> code, and much depends on how aggressive you want to be, your 
> ERP/CFM values etc.
> --
> gl
> 
> _______________________________________________
> ODE mailing list
> ODE at q12.org
> http://q12.org/mailman/listinfo/ode
>