This site relies heavily on Javascript. You should enable it if you want the full experience. Learn more.

How to transfer from DX11 to EX9?

DX11 Renderer shows donut, EX9 render shows white square.

blausand, Saturday, Nov 21st 2015 Digg | Tweet | Delicious 4 comments

microdee 22/11/2015 - 03:42

MRT is tricky when you share it, proper temptarget is more stable for sharing however as i can remember there's a DX11ToDX9 module coming with dx11.
also why do you need the result in dx9? what's missing in dx11? (except some old stuff like AsVideo)

actually i know a scenario when you need to have frame synchronous contour detection with freeframe from a kinect2, I've created a x64 vvvv instance for kinect shared with dx11 and received the thing in dx9 in an other x86 vvvv for the freeframe contour, it was hacky as hell but the alternative with OpenCV was actually slower.

microdee 22/11/2015 - 03:59

also need to point out couple of things: on dx9 formats are not called the same the dx11 R16G16B16A16_Float is A16R16G16B16F in dx9, shared handle is != texture pointer, you need to use the former. To make texture sharing work the sharable texture should end up in a renderer output otherwise it is not considered used hence it's not created. On dx9 SharedTexture node usage should be set to rendertarget.

blausand 26/11/2015 - 22:27

Thanks, microdee.
I need to share via DX11 since DX9 fails to let the texture travel between adapters.
The rest of my setup is DX9, hence the desire to cast down.

In DX9, that was really easy using Writer (EX9.Geometry XFile) and Xfile (EX9.Geometry Load). Currently the objects are mapped using a pimped Pointeditor (3D Persistent Sandwich) and flushed into .x files.

I'm thinking of porting the whole project to DX11; right now i'm gonna learn about saving mapped DX11 geometry to disk. But i can't find corresponding geometry writing node.

microdee 27/11/2015 - 13:15

the reason you can't find it is that .x is gone. in dx11 you have to save your geometry with readback and your own method. because in dx11 geometry is only a large buffer of bytes on the gpu and bunch of metadata which tells assemblers and shaders how to deal with them but you can customize that metadata without any constraints. this allows you to do way more stuffs than the dx9 meshes, like a quad based system instead of triangles. or triangles with adjacency information.

How to transfer from DX11 to EX9?

Shoutbox