Add the ability to render a XAML tree to a direct3d texture (offscreen rendering)

[eladmaimoni]

Currently WPF offers the ability to render a xaml tree to a bitmap via RenderTargetBitmap.
Yet this API forces the client to do a copy of the render target to system memory (and back).
It would be much better if it would be possible to gain access the Direct3D9 render target.

There could be various applications to this feature. 3D game overlays, Heads up displays etc.

Here are several discussions on this issue:
https://stackoverflow.com/questions/10376016/rendering-from-wpfs-internals-to-a-directx-application
https://stackoverflow.com/questions/18881683/how-to-display-wpf-overlay-on-top-of-directx?noredirect=1&lq=1
https://stackoverflow.com/questions/52918039/is-it-technically-possible-to-render-a-wpf-xaml-element-to-a-direct3d-texture

[lindexi]

#97 Bring win2d to WPF

And you may use D3DImage.

[lindexi]

#85 Extensible rendering pipeline

[eladmaimoni]

@lindexi

And you may use D3DImage.

How can D3DImage help in this case? it only allows rendering DirectX content to an exisiting WPF UI, not the other way around.

[lindexi]

But it can add in xaml

[jtorjo]

Would this allow for then grabbing the direct3d texture into a bitmap (basically, avoiding the costly RenderTargetBitmap on a XAML tree)?

If so, that would be INSANELY USEFUL!
How soon could we expect this? My app would benefit immensely from this. Probably a 10x improvement in speed or so.

[lostmsu]

As a user of WPF, I'd be happy, if RenderTargetBitmap would allow expose its own DXGI surface, or allow me to supply my own.

[jtorjo]

@lostmsu I've given up on this entirely. I've switched to UWP almost a year ago (which comes with its own huge bag of gotchas, but that's an entirely different story).