Hi Nick,

Are you using the same mesh for both rendering and physics simulation? This is done in our demos but usually in games there are separate assets for rendering and for physics. This is definitely the recommended approach as concave geometry collision detection is very slow in physics simulation and can often be simplified to convex geometry. The same goes for geometry with lots of triangles: more triangles means more time spent simulating physics when it could be simplified to simple primitives or low-poly meshes.

If you keep your render and physics assets separate, you won't need to worry about textures and Havok at all.

Daniel

Nick,

Render meshes should be imported into OGRE using some format designed for render meshes. OGRE has its own mesh format for this. Havok can handle animation and physics, and the Havok Content Tools will export animations and physics meshes for you, but it's important that you don't physically simulate your render meshes.

Player characters are usually physically simulated by a simple model made with a couple of capsules for each arm, a couple for each leg, and a few boxes or spheres for the torso for "high quality" and often a simple capsule surrounding your render mesh is enough for acceptable physical interaction.

You shouldn't be passing anything from hkx files to the renderer. Use the hkx file data to create your Havok world, and then you use the Havok-animated/Havok-physically-simulated object transforms to set the transforms of your render-meshes.

Have a look at Havok Physics->Physics Articles->Physics Primer in the docs and hopefully it'll make a little more sense to you as to how to implement what you're trying to do.

Daniel