Home/ Questions/Q 7748431
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-06-01T10:47:02+00:00

Hello I’ve managed to integrate SlimDX and DirectX 11 graphics in a WPF application

  • 0

Hello I’ve managed to integrate SlimDX and DirectX 11 graphics in a WPF application by using D3DImage and shared textures. However, but I’m getting some really poor performance when rendering simple scenes (e.g. GameOfLife in the SlimDX samples) at high resolution (2560×1440).

I’ve tried doing some performance profiling of my render method and it looks like most of the time is spent on locking the D3DImage when invalidating the backbuffer. 

_d3dImage.Lock(); // <- this call takes 78,5 % of the time when rendering the frame
_d3dImage.AddDirtyRect(new Int32Rect(0, 0, _d3dImage.PixelWidth, _d3dImage.PixelHeight));
_d3dImage.Unlock();

A lot of time is spent flusing the device after drawing:

_device.ImmediateContext.Flush(); // <- 20,6% of the time when rendering the frame

Anyone know the problem and how to optimize this? Can you expect to get descent performance when integrating WPF and SlimDX?

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    Since you’re seeing performance issues on locking and flushing calls (which are points where the GPU needs to sync with the CPU), I’d guess that your program is severely GPU bound, and the CPU has to keep stalling waiting for it to catch up. That’s also born out by the performance increase when disabling the compute shader.

    I’m not sure what to tell you at that point, except that if that guess is right, it would appear that your card can’t handle the load.

    • 0