[ODE] Collision Shapes - was : FPS Player physics

Michael Molkenthin molle at michael-molkenthin.de
Tue Aug 1 01:33:22 MST 2006

thank you for the valuable recommendations, Jon.

Okay, i am going to change my moving trimeshes to collision proxy 

How are doing the people getting the parameters for their proxy objects? 
Do they hardwiring them into their code? Or do they have special 
exporter plugins in their modeling tools?

so long,

On Mon, 31 Jul 2006, Jon Watte (ODE) wrote:
> When a trimesh is involved, ODE calls out to OPCODE. When trimeshes are not 
> involved, ODE uses its own collision primitives.
> The trimesh <-> trimesh case ("moving trimeshes") is not as well behaved as 
> most other cases, even with the numerous hacks you can employ, and is usually 
> often a lot slower, so people usually use collision proxy objects (capsules, 
> boxes, etc) for the moving actors and/or their limbs.
> Using static trimeshes (for terrain/buildings/etc), and proxy objects for 
> moving actors, is the well-tested, well-behaved, well-performing "standard 
> case" when using ODE.
> Cheers,
>         / h+
> Michael Molkenthin wrote:
>> i thought, ode is making transparently usage of OPCODE for all 
>> trimesh/trimesh collisions. Are there any cases ODE is doing collision 
>> without OPCODE? Perhaps i have not understanded your post.
>> Is somebody here converting its trimeshes into approximating 
>> Boxes/Cones/tubes dedicated for collision to simplify trimesh/trimesh 
>> situations to box/trimesh or trimesh/cube?
>> regards,
>> Michael

More information about the ODE mailing list