Profiling Havok

Profiling Havok

We are seeing havok take some large times per frame that we can't explain.

So assuming that we are using havok in a bad way, what is the best way to track down what is causeing the performance bottlenek.

We are seeign 2ms step time ont he physics for a about 200 static fixed rigid bodys and 150 moving ones.

3 posts / 0 new
Last post
For more complete information about compiler optimizations, see our Optimization Notice.

Quoting - rbabiak

We are seeing havok take some large times per frame that we can't explain.

So assuming that we are using havok in a bad way, what is the best way to track down what is causeing the performance bottlenek.

We are seeign 2ms step time ont he physics for a about 200 static fixed rigid bodys and 150 moving ones.

Hi rbabiak,

The best way to start is to capture a Visual Debugger movie with the Statistics Viewer enabled. That will bring up a tree of timing information, similar to when you turn on the timers in the demo framework. Once you've done that, you can attach it here so we can see where the time is going (and also how your scene is set up).

VDB movies shrink a lot when you zip them, btw.

If you're nervous about posting the movie publicly, we can work something out so that you can send it directly to one of us. But I'd rather have it public if possible so that other people can learn too.

-Chris

Hi,

Just wondering if you had any more info here.

Another thought if you don't want to attach a full VDB movie - you can take a look at the DetailedTimers demo, which should show how to save out the Havok timers for a few frames to a file. That still lets us see which Havok functions are taking up the time, although it doesn't give as much info about your shape usage and rigid body distribution. But on the plus side, it also doesn't let everybody else see your super-secret project :)

-Chris

Leave a Comment

Please sign in to add a comment. Not a member? Join today