Often when you read articles explaining how to use a D3DImage in your WPF application you use code which directly handle the CompositorTarget.Rendering event by updating the 3D world... This can lead to performance problems.

For example in my application, WPF refresh the display with a FPS of 160 : the handler which recreate the 3D image is then call 160 times a second. No need to refresh this often.

The solution I used is to create a Timer which will do it at the FPS I want. Let's say 30FPS for example :

public void createTheRenderingWithCorrectFPS(int whichFPS){
   DispatcherTimer _timer = new DispatcherTimer();
   _timer.Interval = new TimeSpan(1000 /whichFPS);
   _timer.Tick += new EventHandler(_timer_Tick);
void _timer_Tick(object sender, EventArgs e)
   //Refresh the 3D scene

This enables your application to be really more reactive especially that you need to be on the main thread to update the 3D scene...

Do you know a better way ?

kick it on DotNetKicks.com Shout it