[ODE] AutoDisable issue?

[Mohsin Hasan]

Why would a collision test be done if the object is disabled? Maybe I'm
missing something here. I guess I'll just debug the ODE code and see what's
happening. I am using Hashspace BTW.

Mohsin


Mohsin Hasan wrote:
> When the simulation starts all the bodies get autodisabled and the stack
is
> perfectly resting. I am getting an average FPS of 245 FPS. I drop a sphere
> from top and all the stacks collapse with cubes all over the ground.
> Simulation speed varies by dropping to 50 FPS to 230 FPS to again 50 FPS
and
> finally when all the bodies get disabled I get a stable 145 FPS... 100
less
> than the original disabled bodies FPS I was getting. Why is that?

There's more going on than simulation.  The extra time is probably
being taken up by colliding the rather different distribution of
geoms, even though they're disabled (I don't think that ODE culls
away collisions between pairs of disabled bodies until fairly late,
but I could be wrong).  The penalty for that will vary depending
on the type of Space used.

But then, you could always profile and stop guessing.

--Adam
-- 
Adam D. Moss   . ,,^^   adam at gimp.org   http://www.foxbox.org/   co:3