Best solution for physics integration?

Hi,

I've been reading these forums for a while, and made generally good progress with ODN - well done, the wrapper is very complete. I'm wondering though, what have you guys done for physics integration in your projects?

Currently, I'm using ODE.NET (just a wrapper for ode v0.5), and I've managed to (with some effort) read the vertex data from Mesh objects into an array of vertices. So I could use this to construct TriMeshes in Ode, and go from there, but I feel like I might be reinventing the wheel here. There are a lot of projects out there that have already integrated some physics engine and Ogre, but are any of them rapped well enough to be usable yet? What about the Gansta wrapper? Is there still ongoing development on it?

Thanks

tirpluK

Honestly, I'd like to know the answer to this too. It seems like physics are a whole other complex beastly animal that I'll have to learn.

walaber's OgreNewt wrapper for the Newton Game Dynamics engine is stellar.

walaber's OgreNewt wrapper for the Newton Game Dynamics engine is stellar.

So if you use GangstaDotNet (a wrapper) to implement Gangsta Wrapper to use OgreNewt, you'd have a wrapper of a wrapper of a wrapper around a physics engine...

Huh...

GangstaDotNet
- Wraps Gangsta Wrapper
-- Which wraps OgreNewt
--- Which wraps Newton

Wow, that's a lot of wrapping!

Best? that's so argumentative, it all depends on you needs/comfort with the API.

the GangstaWrapper is not under development now no but I like it. just because you can choose different PE to use.

also Gangsta has the ability to take a mesh and setup a trimesh automatically.

walaber's OgreNewt wrapper for the Newton Game Dynamics engine is stellar.

So if you use GangstaDotNet (a wrapper) to implement Gangsta Wrapper to use OgreNewt, you'd have a wrapper of a wrapper of a wrapper around a physics engine...

Huh...

GangstaDotNet
- Wraps Gangsta Wrapper
-- Which wraps OgreNewt
--- Which wraps Newton

Wow, that's a lot of wrapping!

hehe just wrap ogreNewt , there aren't many functions and it works very easily with ogre. The only 'weird' thing to consider is it uses callbacks for most things (including adding forces etc).