[ODE] AutoDisable: Alternatives

[Jani Laakso]

Aras Pranckevicius wrote:

>>To be honest I'd personally be happy enough with global thresholds
>>for now... while local thresholds would be better, we're still
>>talking about magic number tuning really and I don't realistically
>>expect users to bother to tune per-body thresholds.
> 
> 
> So - a pair of global params or a pair of per-body params?
> (of course, with functions to set/get each of them)

Summary, here are the alternatives:

1. global parameters (all bodies)

2. global parameters per each type (sphere type, box type..)

3. local parameters per each body

4. add your own solution here


The parameters would consists of three values:
-angVel, linVel and stepCount?


I'd go for most flexible solution (3). Unless there is a good reason not 
to do it this way.


Is there an real performance (speed / memory) issue against using per 
body specified parameters? This would be more flexible than global 
parameters.

I'd assume user would want to use global parameters for most of the 
bodies, but there can be some bodies that need different auto disable 
parameters.

Also different geoms, e.g. sphere vs. box, can require different auto 
disable values, don't you agree?


-- 
Jani Laakso / IT Mill Ltd | Tel. +358 40 5898086 | http://www.itmill.com