Sign in to follow this  

WPF and SlimDX (DirectX 11) interop

This topic is 2122 days old which is more than the 365 day threshold we allow for new replies. Please post a new topic.

If you intended to correct an error in the post then please contact us.

Recommended Posts

Hello, posted this on StackOverflow ([url=""]http://stackoverflow...ectx-11-interop[/url]) but figured that this might be a better forum to post my question. Here it is:

[color=#000000][hr][/color][color=#000000]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 (20 FPS) when rendering simple scenes (e.g. GameOfLife in the SlimDX samples) at high resolution (2560x1440).[/color] [color=#000000][font=Arial,]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.[/font][/color]

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

[color=#000000][font=Arial,]A lot of time is spent flushing the device after drawing:[/font][/color]
[CODE]_device.ImmediateContext.Flush(); // <- 20,6% of the time when rendering the frame[/CODE]

[color=#000000][font=Arial,]Anyone know the problem and how to optimize this? Can you expect to get descent performance when integrating WPF and SlimDX?[/font][/color]
[color=#000000][font=Arial,]I've used the same rendering code and initialization as in the SlimDX WPF interop sample (for DirectX 10), just modified it so it uses DirectX 11 instead. Seeing as it spends much time waiting for the D3DImage to get unlocked, it seems to me that WPF is keeping it locked alot for some reason (I'm not updating any WPF controls). Any Ideas?[/font][/color]


Share this post

Link to post
Share on other sites
Sign in to follow this